- Windows Vista
- Windows 7
- Windows Server 2008, 2008 R2
So we had a server with a corrupted .net installation, Windows Update kept on trying to install a .net 3.5 QFE and failed it, which showed up on the SUS server error logs. Investigation revealed that it would not install the update.
After running the .net cleaner utility, Windows Update still insisted that the machine needed the QFE – despite the fact that .net 4, 3.5, 3.0, 2.0 and 1.x were not installed.
The next obvious step was to put .net back on the machine, starting with 3.0 in the Windows Server Manager ‘Features’ list. It would not reinstall the feature however terminating with
There were two problems here
- A .net Framework update was stuck in the Windows Update Catalogue and could not be cleared (even by purging SoftwareDistribution)
- The .net Framework 3.0 feature could not be reinstalled onto the operating system via Windows Server Manager
In this instance the following solved the problem:
- Browse to:
- Check to see if there is a machine.config file present within the folder
- If there is not, make a copy of machine.config.default in the same folder and rename it to machine.config
Note that you may need to look through other folders under C:\Windows\Microsoft.NET\Framework for this .config file as the ‘v2.0.50727’ part changes with the service release.
Once this was done, .net 3.0 could be reinstalled from Windows Server Manager. Once that was done .net 3.5 SP1 could be reinstalled (along with .net 2.0 SP2 and .net 3.0 updates). This allowed the stuck update to actually install and cleared the original error from WSUS.
After that .net 4.0 went back on and everything on the server was back to normal again.
…the toe bone connected to the foot bone, and the foot bone connected to the ankle bone, and the ankle…