Quote:Framework 3.0 installation
Sorry that was vaugue.
Recently suffered HD failure. Framework 1.0, 1.1, 2.0, 3.0, 3.5, 4.0 all affected.
I have mananged to uninstall Framework 1.0, 1.1, 2.0 using microsoft tech articles along with patience.
Framework 3.0, 3.5 apparently are corrupted in my registry. I have tried MS technet and several "fixit" solutions but XP will not let me uninstall 3.0, nor will it let me change it. Primary problem is is referencing the framework 3.0 .msi file which used to be on my f: drive prior to the crash.
I have downloaded the Framework 3.0 installation program and tried to run it and re-install the program with not success (corrupted registry).
The other problem is that the MS Updated has a back log of about 11 updates it continually want to try for 3.0, 3.5 and 4.0 all which fail because of the corruption.
So, I am looking for the solution to manually uninstall Framework 3.? and / or how to remove it from the registry so it can be installed.
Thanks for that suggestion.
I pursed the Microsoft Tech Net a bit more and found this link -
This page speaks a great deal about missing or corrupted MSI files, and about half way down the page offers a "Framework Cleanup Tool" -
.NET Framework 1.0, 1.1, 2.0, 3.0, 3.5
To repair the .NET Framework 1.0, 1.1, 2.0, 3.0, 3.5, use the .NET Framework Cleanup Tool to uninstall multiple versions of the .NET Framework, and then reinstall the components.
To do this, follow these steps:
1.Visit the following blog post:
.NET Framework Cleanup Tool User's Guide
2.Download dotnetfx_cleanup_tool.zip from the following site:
The clean up tool basically lets you pick which version of .NET you wish and it clears all entries in the registry per your selection.
I removed 3.0, 3.5 and 4.0 using the tool, then reinstalled Framework 2.0. I decided to let "Microsoft Update" decide what happened next. It then chose to download and install the Framework 2.0 - 3.5 Update which is the orginal 11 updates I could not do before. They were successfull.
I have not reinstalled .Net 4.0 + yet and choose to wait for the time being, or if Windows runs across something in which it decides that version is necessary. We'll see what happens.