Error when starting PS V2 CP

I've installed PS V2 (CP) on Windows XP Sp2. When running the shell I
always get these errors (in red):

Windows PowerShell
Copyright (C) 2006 Microsoft Corporation. All rights reserved.

Error loading the extended type data file:
Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0
\types.ps1x
ml(259) : Error in type "System.DirectoryServices.DirectoryEntry":
Exception: Ca
nnot convert "Microsoft.PowerShell.AdapterCodeMethods" to
"System.Type".
Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0
\types.ps1x
ml(266) : Error in type "System.DirectoryServices.DirectoryEntry":
Exception: Ca
nnot convert "Microsoft.PowerShell.AdapterCodeMethods" to
"System.Type".
Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0
\types.ps1x
ml(277) : Error in type "System.IO.DirectoryInfo": Exception: Getter
method shou
ld be public, non void, static, and have one parameter of type
PSObject.
Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0
\types.ps1x
ml(308) : Error in type "System.IO.FileInfo": Exception: Getter method
should be
public, non void, static, and have one parameter of type PSObject.

....and then the prompt appears. Is that expected and can I simply
ignore it?


Thorsten

Thorsten Kampe 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

* Marco Shaw [MVP] (Thu, 10 Jan 2008 17:01:00 -0400) Done

Thorsten

Interestingly I have not seen these on XP, Windows 2003 or Windows 2008
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Thorsten Kampe" wrote:

RichS wrote: At least 3 more people reported this. Check the comments here:
http://blogs.msdn.com/powershell/arc...his-space.aspx

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

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

Blog:
http://marcoshaw.blogspot.com

Interesting -

Can those types actually be accessed even though an error is being reported.
Be also interested to know patching levels of .NET


--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Marco Shaw [MVP]" wrote:

RichS wrote: I have one who has contacted me directly. He did have v1 on the system
previously.

I'll dig up something to test the types.

Is this a true test of the .NET version information?

PS C:\WINDOWS\Microsoft.NET\Framework> dir v*
Directory:
Microsoft.PowerShell.Core\FileSystem::C:\WINDOWS\Microsoft.NET\Framework
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 1/4/2008 12:18 AM v1.0.3705
d---- 1/4/2008 12:18 AM v1.1.4322
d---- 12/4/2007 9:59 PM v2.0.50727
d---- 4/30/2007 4:28 PM v3.0
d---- 8/9/2007 1:29 AM v3.5

I updated v.2 recently. That version above seems different, although I
can't remember for sure. The directory/version info must have changed
on reboot (if that's possible). I don't remember being asked to reboot
when I loaded a newer downloaded version.

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

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

Blog:
http://marcoshaw.blogspot.com

I match those version numbers. I'm not sure the folder name updates when the
particular version is patched
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Marco Shaw [MVP]" wrote:

"Thorsten Kampe" <thorsten@xxxxxx> wrote in message
news:MPG.21f07aae3702ca01989935@xxxxxx
Running what? Just opening it the first time with no customization?

FWIW when I did that I got a series of security prompts which I eventually
disabled. Unfortunately I can't recall exactly what they said but it looked
as if I was getting one prompt per default script loaded.

Also, it may matter whether you have also installed (or tried to use)
the V2 Graphical shell. FWIW I had to install .NET 3.5 for that
and downloaded a beta version to do it. It was a bit of an adventure
getting that installed. I now understand some of the frustration
that some users complain about when installing .NET updates
but think I now am also in a better position to make suggestions
about making them work without resorting to some of the sledgehammer
repair suggestions that many people end up resorting to. ; )


Good luck

Robert Aldwinckle
---

The v2 graphical editor requires .NET 3.0 likely because it utilises
some of the 3.0 extensions like WPF.

I found the 3.0 (and 3.5) install to be very easy personally, but agree
that some may have problems finding the installers.

Marco