Vista - .NET Runtime Optimization Service has encountered a problem

I just installed PowerShell 2.0 on Windows XP. When I run it, I get a
popup that says ".NET Runtime Optimization Service has encountered a
problem and needs to close". Other than the popup, I don't see any
evidence of a problem.

Any idea what is causing this?
Should I go back to 1.0?

Thanks,

Al

What .NET version is installed?

I'm using .NET Framework 3.5 Service Pack 1 on XP SP3 with no problems like that.

- Larry


Al Fansome wrote:

I am running the same versions of both .NET and XP.

I now don't think that this happens when I run PowerShell. The .NET
Runtime Optimization Service is a service; it was probably running until
I installed PowerShell 2, at which point it started failing. I tried
uninstalling .NET and then reinstalling it, but the problem continues.
Eventually the service no longer restarts, so I don't see the popup any
more.

From what I've read I might be able to get by without it, but it would
be nice to know why it started failing, and why reinstalling .NET and
PowerShell doesn't fix the problem.

Larry__Weiss wrote:

http://social.msdn.microsoft.com/For...e-e4376a6f7075
mentions a removal tool that helps remedy this.

- Larry


Al Fansome wrote:

I am using the procedure described here, and I seem to be making
progress:
http://blogs.msdn.com/powershell/arc...-download.aspx

This service, known as "ngen", precompiles .NET intermediate code in the
background. Apparently a bunch of non-existent assemblies got queued to
this service; they appear to be leftovers from when I installed PS 1 and
then uninstalled it. When the service tries to compile them, it crashes
because they got uninstalled.

"ngen uninstall" will remove these from the queue, one at a time. So,
you have to go to C:\windows\microsoft.net\framework\v2.0.50727, and
look at the last entry in ngen_service.log: "(cat
ngen_service.log)[-10..-1]". Then use ngen uninstall to remove this last
entry, e.g.

v2.0.50727> .\ngen uninstall
"System.Management.Automation.resources,Version=1.0.0.0,Culture=%PowerShell_Culture%,Public
KeyToken=31bf3856ad364e35,ProcessorArchitecture=msil"

Then start the service again. When it fails again, do the above again;
rinse and repeat. I think it finally is ok now; I believe I had to do
this for about five or six assemblies.

Larry__Weiss wrote: