Skybuck said:
Hiding .NET Framework 3.5.1 seems to have helped.
All other updates seems to have been installed, even some patches for
the .NET Framework 3.5.1 were installed which is kinda weird but ok.
So far so good:
http://www.skybuck.org/Windows7/Aut...me/Attempt2HidingDotNetFrameworkHasHelped.png
Bye,
Skybuck.
Windows 7, comes with .NET 3.5.1.
And that makes repairing it a problem.
When you turn off a feature in Windows, it doesn't necessarily remove it.
There is a picture here, of being able to turn it off, but that's not
going to help your problem as far as I know.
http://social.technet.microsoft.com...t/thread/3755d82c-cd2b-458e-918e-16c9f4f5d1db
*******
Aaron Stebner offers a tool for .NET cleanup. It basically uninstalls
any hand-installed versions of .NET. I do not think it will remove
3.5.1 for you, neither will it contribute to an effort to "freshen
up the files".
http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx
The other tool that is useful, is Aaron's "netfx_verifier_new".
It runs a test, for each .NET version, to see whether things are
working properly or not. You can use this, at the current time,
to determine whether the versions of .NET that are installed,
are working right. I've used the Verifier on my machines
here, when I experience .NET problems, and I want to be sure
everything is still working.
http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
HTH,
Paul
