Sometimes Microsoft products are crankier than my two children combined, and that’s saying a lot. This particular issue has been a thorn in my side for several months, and I finally found a workaround that fixes the problem. And now without further ado, I present the .NET Framework Fix.
If you happen to run into an XP machine having trouble installing a .NET Framework Windows Update, it will most likely need the .NET Framework Fix. It’s an annoying time consuming process of uninstalling and reinstalling various Windows updates.
Symptoms: A Windows Update/Automatic Updates error similar to this (Error code: 0x80070643):
Cause: According to Microsoft: “This issue may occur if the MSI software update registration has become corrupted, or if the .NET installation on the computer has become corrupted.” However, I personally believe it is the way that Microsoft stacks updates with the .NET framework, similar to older versions of Adobe Reader or Java. It never completely cleans out/uninstalls the last version before trying to put in the next version in thereby creating issues.
- Download the dotnetfx_cleanup_tool.zip:
- When you are prompted, click Open, and then click Extract Now.
- In the files that you extracted, double-click cleanup_tool.exe.
If you are prompted for an administrator password or for confirmation, provide the password, and then click Continue.
- In the Do you want to run the .NET Framework Setup Cleanup Utility? message, click Yes.
- Click Yes to accept the license agreement.
- In the Product to cleanup window, click the list, select .NET Framework – All Versions, and then click Cleanup Now.
- After the .NET Framework is removed, restart the computer.
- Download and install the following components:
.NET Framework 1.1
Microsoft .NET Framework Version 1.1 Redistributable Package
.NET Framework 1.1 Service Pack 1 (SP1)
Microsoft .NET Framework 1.1 Service Pack 1
.NET Framework 3.5 SP1 (this will also install the .NET Framework 2.0 SP2 and the .NET Framework 3.0 SP2)
8. Restart the computer.
9. Visit Windows Update again, and then check for and install updates.
I have tested this on several computers at the station that refused to install the .NET updates and it works like a charm. Big THANK YOU to Aaron Stebner for sharing this information!