My boss had some problems on his PC after installing some tools onto it and upon further diagnosis it appeared to be that the .Net Framework had been corrupted. We did all the usual things of looking in "Add/Remove Programs" etc, adding service packs etc all to no avail. I then came across this blog entry and a fix started to come to light
How to repair the .NET Framework 2.0 and 3.0 on Windows Vista
Since the Windows Vista public launch in January 2007, I have been receiving questions about how to repair the .NET Framework 2.0 and 3.0 to try to resolve various bugs. As I previously described here, the 2.0 and 3.0 versions are installed as OS components on Windows Vista and do not appear in the Programs and Features (formerly known as Add/Remove Programs) control panel.
Many of the customers I have heard from have tried to use the .NET Framework cleanup tool, but it does not list the .NET Framework 2.0 as a valid removal option when it is run on Windows Vista. This is by design - the cleanup tool does not offer the option to remove any version of the .NET Framework that is an OS component on the OS it is being run on.
Aaron Stebner's WebLog : How to repair the .NET Framework 2.0 and 3.0 on Windows Vista
The important things seem to be:
- Don't use the clean up tool
- Try the command "sfc /scannow" from an elevated command prompt
- Repair the (V2) framework with the command "%windir%\Microsoft.NET\Framework\v2.0.50727\ngen.exe update" again from an elevated command prompt
The 1st item stops corruption, then 2nd checks the OS's binary (core internal files) are correct and matching their signatures and the final one re-creates all the "native" files from the IL code.
Fri, Feb 1 2008 7:32 AM