Vista - Powershell 2 startup Errors

Here's what I get now when I launch a new PS:
------------------------------------------------------------------------------------------------


Error loading the extended type data file:
Microsoft.PowerShell.Core,
D:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(259) : Error in type
"System.Director
yServices.DirectoryEntry": Exception: Cannot convert
"Microsoft.PowerShell.AdapterCodeMethods" to "System.Type".
Microsoft.PowerShell.Core,
D:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(266) : Error in type
"System.Director
yServices.DirectoryEntry": Exception: Cannot convert
"Microsoft.PowerShell.AdapterCodeMethods" to "System.Type".
Microsoft.PowerShell.Core,
D:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(277) : Error in type
"System.IO.Direc
toryInfo": Exception: Getter method should be public, non void, static, and
have one parameter of type PSObject.
Microsoft.PowerShell.Core,
D:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(308) : Error in type
"System.IO.FileI
nfo": Exception: Getter method should be public, non void, static, and have
one parameter of type PSObject.

File D:\Documents and Settings\Admin.PDC1\My
Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cann
ot be loaded. The file D:\Documents and Settings\Admin.PDC1\My
Documents\WindowsPowerShell\Microsoft.PowerShel
l_profile.ps1 is not digitally signed. The script will not execute on the
system. Please see "get-help about_signing" f
or more details..
At line:1 char:2
+ . <<<< 'D:\Documents and Settings\Admin.PDC1\My
Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps
1'




---Any Advice? Thanks

Looks like Keith's blog post will help you:
http://keithhill.spaces.live.com/blo...A97!6040.entry

--
Kiron

Well for the last problem it looks like you need to execute
"Set-ExecutionPolicy RemoteSigned" (or Unrestricted). Try opening up a
session after doing that.

--
Keith

"Ian_1" <fakeaddy@xxxxxx> wrote in message
news:E308EF57-D5D4-498D-93BF-58B14C5B54F2@xxxxxx

Did you ever find the solution to this problem. I installed Powershell 2.0
today and ran into the same problem. I didn't see anything in Keith Hill's
Blog that discussed this.
Thank you,
Fred J
swim.instructor@xxxxxx

"Ian_1" wrote:

Keith,
Thank you for your response. I tried it but no cigar. For some crazy reason
I am still executing what appears to be $host.version 1 0 0 0.
However, I did locate this in the event log.
Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7036
Date: 1/5/2008
Time: 5:53:38 PM
User: N/A
Computer: MICRON
Description:
The .NET Runtime Optimization Service v2.0.50727_X86 service entered the
running state.
Event Type: Error
Event Source: SideBySide
Event Category: None
Event ID: 32
Date: 1/5/2008
Time: 6:01:53 PM
User: N/A
Computer: MICRON
Description:
Dependent Assembly Microsoft.VC80.MFCLOC could not be found and Last Error
was The referenced assembly is not installed on your system.

Although the installation completed sucessfully perhaps this is the problem.
I have installed .Net Framework 2 and 3 and Service Pack 1 for 2 and 3.

Any thoughts? Thank you,
Fred Jacobowitz

"Fred Jacobowitz" <FredJacobowitz@xxxxxx> wrote in
message news:7DB548A7-D556-4A94-8196-BCFEDB10AF49@xxxxxxI can't imagine that PowerShell depends on MFC. However check if you have
the 8.0 CRT DLL - MSVCR80.dll. Again I can't imagine that you wouldn't
since PowerShell should install it. The DLL should be located in this dir:

%windir%\winsxs\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd

That is, if you are running 32 bit windows.

--
Keith

Keith,
Thank you for your response. I do have the 8.0 CRT DLL - MSVCR80.dll.
located in
%windir%\winsxs\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd.

I am running 32 bit windows XP service pack 2. In the interim I re-installed
Powershell V1.0 because you can't be without a working version!!!!

Thank you for all your suggestions. I will keep on plugging away.
Fred Jacobowitz

Ian_1 wrote:A few others have reported seeing similar problems.

If you're not in a hurry to fix, and are willing to work with someone to
try to find a solution, email me: marco DOT shaw AT gmail DOT com

Hopefully we can find the issue for everyone's benefit.

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

Fred Jacobowitz wrote:A few others have reported seeing similar problems.

If you're not in a hurry to fix, and are willing to work with someone to
try to find a solution, email me: marco DOT shaw AT gmail DOT com

Hopefully we can find the issue for everyone's benefit.

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

Do you have any PSsnapins isntalled prior to trying to install V.2

I recieved something simialr to this, and uninstalled the snapins. I
think the community extensions snapin builds a custom personal setup for
powershell that is not compatible with V.2

You might delete the "powershell_profile.ps1" file from "My
documents\WindowsPowershell\Microsoft" and see if the errors go away.

I am not positive about this, just a suggestion

Dennis



"Marco Shaw [MVP]" <marco.shaw@_NO_SPAM_gmail.com> wrote in message
news:u1XMgw8UIHA.4696@xxxxxx