When this happens, one of the processes invoked by the installer (usually REGSVR32.EXE) peaks at 100% CPU and stays there indefinitely. Killing the process usually leaves the install or removal in a broken state until you complete it at another time.
At first I thought this was a problem with the system in general, but no other software installations seemed to suffer from the same issues. Some online searching turned up a possible
The two services in question turned out to be the Microsoft Distributed Transaction Controller and the Windows Installer service, Both were enabled but not running. Once I started both of them and re-ran the deinstaller, the .NET Framework was removed cleanly. I was also able to reinstall them without trouble.
Note: The Windows Installer service should be version 3.1 or better; if it isn't installed (check Add/Remove Programs), you can download version 3.1 or higher.
Further note: Some third-party applications can also cause this to happen. In his aforemention blog, Aaron Stebner mentions Tenebril GhostSurf 2006, an Internet anonymity product. However, that program doesn't seem to require the .NET Framework to run. Furthermore, there may be other products that cause issues like this as well.
About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter, which is devoted to hints, tips, tricks, news and goodies for Windows NT, Windows 2000 and Windows XP users and administrators. He has more than 10 years of Windows experience under his belt, and contributes regularly to SearchWinComputing.com and SearchSQLServer.com.
More information on this topic:
- Tip: Windows Installer Cleanup utility jettisons hard-to-lose apps
- Topics: Server management
- RSS: Sign up for our RSS feed to receive expert advice every day.
This was first published in September 2006