Welcome to MSDN Blogs Sign in | Join | Help

XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

Good things come to those who wait.  Please download these bits and let us know if you have any problems with them.

https://connect.microsoft.com/windowsmanagement/Downloads

 Just to be clear, this download contains the latest version of both PowerShell and WINRM.

SNOOPY DANCE!

Jeffrey Snover [MSFT]
Distinguished Engineer
Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

 

Published Thursday, September 10, 2009 9:32 PM by PowerShellTeam

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

Thanks, guys!  I'm installing them now.  Well, downloading XP SP3 first :-).

Thursday, September 10, 2009 6:27 PM by Mike Wilson

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

Been fighting with this all night but I can not get it to install on my XP image that had been running PS 2 CTP3.... the PSCustomSetupUtil is driving me nuts with the constant prompts to send report.

Thursday, September 10, 2009 10:24 PM by JKavanagh

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

Been waiting for this since CTP1.  Version 2 is finally almost here!  Good work to all on the Powershell Team.

Thursday, September 10, 2009 10:33 PM by Shane Powser

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

As someone whose been working up an app that uses PowerShell heavily for scripting, using CTP3, it'll be very helpful if a list of changes between CTP3 and the RC could be given.

Friday, September 11, 2009 12:04 AM by Cheetah

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

Jeffrey and Team:  Great job on this release!  Were I presently employed, you'd once again be saving me hours each day in mgmt. tasks.

Also want to take a moment and thank you all for bringing your bits and dependencies bits together for release!  I was one of the more vocal users regarding the issues faced in the past when a new PS build was available, and the dependency bits weren't available to work with the new features in PS.

Thank you PS Team and keep up the great work!

Friday, September 11, 2009 5:02 AM by Eric Walker

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

@JKavanagh If you set your Internet Explorer trust setting for Local Intranet to High it'll magically install.  

Friday, September 11, 2009 5:33 AM by Damien Ryan

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

The install did not go well, unfortunately due to me forgetting to RTFM...  I installed en-US_Core_XP_x86_KB968930.exe and then realized that I didn't have PS 2.0.  I uninstalled WMF and PS 1.0 and installed PS 2.0.  Now my .NET Optimization Service is crashing regularly and my system has delays all over the place.  I can't even tell if I have PS 2.0 installed now as I see C:\Windows\System32\WindowsPowerShell\v1.0, but no v2.0 folder.

Friday, September 11, 2009 9:34 AM by Derek Price

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

I had seen the not about IE Security settings, that does not seem to fix the issue.  I did install this on a few Win2003 Servers x86 without a hitch.  

Friday, September 11, 2009 1:25 PM by JKavanagh

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

I faced same issue which Derek is facing, now my .NET Optimization Service is crashing regularly

Tuesday, September 15, 2009 2:50 AM by Ashish

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

I ran into the same issue experienced by Derek and Ashish. Removal of RC leaves some bogus entry in the NGEN service queue, which causes service to blow up trying to execute it. Reinstallation of RC doesn't help.

Could the PowerShell team provide an instruction on how to properly remove RC from XP/Win2K3, so .NET optimization service wouldn't crash?

There is related bug on Connect marked as fixed, but to explanantions how to work around the issue using the current version of the binaries.

Tuesday, September 15, 2009 10:58 PM by Seva

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

Can anyone in PowerShell land help us poor folks out with this crash .NET Optimization Service issue?

Monday, September 21, 2009 1:15 PM by Derek Price

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

@Derek

Here is a solution from our customer.

------------

Problem Description:

If you're experiencing the crashing of the dotnet optimization service as described in the other feedback sections here, the fix is to remove Dotnet 2.0 (SP1) and reinstall it. A reboot is not required between uninstall and reinstall.

Wednesday, September 23, 2009 2:45 PM by PowerShellTeam

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

@PowerShellTeam

Thanks for the suggestion, but it doesn't really work in general case.

I already have framework 3.5SP1 installed and a bunch of applications that use .NET 2.0 and up.

Attempt to uninstall .NET 2.0 SP2 results in an error message saying that there are apps dependencies and .NER 2.0 SP2 cannot be uninstalled.

Wednesday, September 23, 2009 5:09 PM by Seva

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

Unfortunately I don't have .NET FX 2.0 SP1.  I have SP2 and it won't let me uninstall it and gives me this link: go.microsoft.com/fwlink/?LinkId=91126.  Does this mean that I would have to start uninstalling 3.5 SP1, then 3.0 SP2, then finally 2.0 SP2?

What now?

Wednesday, September 23, 2009 8:15 PM by Derek Price

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

Like Derek, I tried uninstalling .NET 2.0 SP2, but with all the apps installed on top of it, .NET 3.0 and .NET 3.5 that would be easier to reinstall everything rather than attempt to track all the dependencies and uninstall them one by one.

Are there any other suggestions? Is there a way to view/edit/flush .NET Optimization service queue? There must be, as .NET 2.0 uninstall is effectively flushes or deletes the queue.

Sunday, September 27, 2009 6:09 PM by Seva

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

OK, someone made a suggestion on the Connect to use ngen uninstall.

There is a workaround that worked for me:

>>>>>>>>>>

Basically, you need to remove bogus "compile assembly" entry using "ngen uninstall" command. On my system I had to run ngen uninstall multiple times for various PowerShell assemblies.

To get the idea what assembly to remove, check NGEN service log file %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ngen_service.log.

The last entry is what crashed the service. E.g.

09/27/2009 18:31:33 [6452]: Error compiling Microsoft.PowerShell.Security.resources,Version=1.0.0.0,Culture=%PowerShell_Culture%,PublicKeyToken=31bf3856ad364e35,ProcessorArchitecture=msil: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

Command line to run then will be (in %SystemRoot%\Microsoft.NET\Framework\v2.0.50727 folder)

ngen uninstall Microsoft.PowerShell.Security.resources,Version=1.0.0.0,Culture=%PowerShell_Culture%,PublicKeyToken=31bf3856ad364e35,ProcessorArchitecture=msil

After you executed ngen uninstall, you might need to start the .NET Runtime Optimization service.

If it crashes, you'd have to check the log again and get the name of the next assembly to uninstall.

Using a log monitoring utility like tail (or get-content -wait) in a separate window might make it easier.

<<<<<<<<<<<<<

Sunday, September 27, 2009 6:59 PM by Seva

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

Using NGEN Uninstall fixes the crash of the .Net Runtime Optimization Service.

However, the downloaded package will still not install.  It continue to loop the PSCustomSetupUtil error and put the .Net Runtime Optimization Service back in the broken state.  Something is still wrong with the install package.

I have un-installed all previous version of Power Shell.

Like the others, I am running a lot of software on top of .Net 3.5 SP+, so an answer of "uninstall" all your stuff is UNACCEPTABLE!

I do not have 2 days to fix my computer and re-install everything.

I would get fired if I wrote an instalation package that didn't report the actual problem so I could fix it.

Tuesday, September 29, 2009 10:38 AM by Al

# re: XP and W2K3 Release Candidate Versions of PowerShell are Now Available for Download

I was able to follow the uninstall NGEN services directions that Seva provided and all seems to be working now.  I do agree with Al that this manual process really should have been handled by the Microsoft PowerShell team instead of finding the answer in a blog post comment.

Wednesday, October 07, 2009 12:49 PM by Derek Price

Leave a Comment

(required) 
required 
(required) 

  
Enter Code Here: Required
 
Page view tracker