| T O P I C R E V I E W |
| 1029usr078198 |
Posted - January 24 2008 : 17:18:20
I found this blog article that helps.
http://blogs.msdn.com/astebner/archive/2005/04/16/408856.aspx
GEEKS ONLY!
Hope it helps,
David |
| 4 L A T E S T R E P L I E S (Newest First) |
| 1029usr078198 |
Posted - April 22 2008 : 19:00:48
Good catch Ryran! I've updated my post.
Thanks.
David |
| ryran |
Posted - April 22 2008 : 16:24:32
Thanks a lot for this!
Heads-up: something happened with the formatting for the Framework 2.0 link and it's just pointing to this page.
Proper link for easy access: http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&DisplayLang=en |
| 1029usr078198 |
Posted - April 14 2008 : 15:18:44
Also from Aaron Stebner's Blog:
The .NET Framework cleanup tool.
Download it here. Now, the tool supports .NET 4 as well.
You might try using the control panel to uninstall or run a repair; but I just go straight to the cleanup tool now. When the Framework is corrupted, I usually get an error to the effect that the original installation source is unavailable, even though it's right there on the desktop.
Here's the walkthrough:
In addition to the cleanup tool, download the following files:
Put the downloads in a place where they can be accessed later, e.g. Network share, CD, flash drive, etc.
Use the cleanup tool to remove the specific version of .NET Framework that's corrupted, the corrupted version and all previous versions, or all versions on the system.
Reinstall the .NET Framework versions you removed in the order listed in the download list above.
Update: In this Microsoft Answers article I found that if you remove .NET Framework 3.5(SP1), then you can skip reinstalling .NET Framework 3.0 SP2 and 2.0 SP2 because these are included as part of 3.5, but you should also reinstall in this order:
- .NET 3.5 (which includes 3.0 and 2.0)
- .NET 1.1
[*].NET 1.1 SP1
Note: I have attempted to create a complete list of updates, but recommend that after installing your downloads, and before moving to the next version of the Framework, check Windows Update for new updates to that version. Sometimes it happens that if you install a higher version before all the previous version's updates are installed, future Framework updates will fail. So, when Framework 1.0 is installed, check Windows Update before installing Framework 1.1, etc.
The whole process will take between 1.5 and 2 hours unless you already have the downloads handy. |
| 1029usr078198 |
Posted - February 22 2008 : 09:49:12
In case that article disappears, here's the text of it from Aaron Stebner's blog:
How to manually cleanup a failed .NET Framework 2.0 install
In response to the blog article I posted last week where I provided a link to a .NET Framework manual cleanup tool, [Editor's Note: Go get that tool, NOW!] I got some questions about whether or not a comparable version is available for cleaning up the .NET Framework 2.0. I am currently working on a couple of small work items in the code for the tool to enable it to work with 2.0, but in the meantime I wanted to post some manual steps. I know there have been a lot of uninstall/reinstall issues because we have released an alpha, a beta and numerous Community Tech Preview (CTP) versions and not all of them will uninstall completely cleanly in order to allow a future beta version of 2.0 to install correctly.
The following steps will help resolve .NET Framework 2.0 installation failures/hangs in most cases. Before proceeding please note these important caveats:
These steps will only work for the .NET Framework 2.0 installed by dotnetfx.exe (the MSI-based setup). There is a version of .NET Framework 2.0 that is installed as part of the OS if you are running any pre-release builds of Windows codename Longhorn. You should not use these steps on Longhorn.
These steps will damage the .NET Framework 1.0 or 1.1 if you have either of these versions installed on your computer. This is because you are instructed to rename the file mscoree.dll that is shared by all versions of the .NET Framework. If you have 1.0 or 1.1 installed, you will need to immediately install a later build of .NET Framework 2.0 to update mscoree.dll or perform a repair of the .NET Framework 1.0 or 1.1. To repair .NET Framework 1.0 or 1.1, go to the Add or Remove Programs control panel, click on the link for support information, and then click on the Readme link.
If you are running Windows Server 2003, Windows XP Media Center Edition or Windows XP Tablet PC Edition, there is a version of the .NET Framework that ships as part of the OS. In those situations, you cannot repair by using the instructions in Add or Remove Programs under the readme link. In those scenarios it is strongly recommended that you immediately install .NET Framework 2.0 to provide an updated version of mscoree.dll. If that is not an option, you must repair your OS to fix the issue.
Steps to clean up a machine to fix a failed .NET Framework 2.0 installation:
Using Add or Remove Programs, locate any versions of the .NET Framework 1.2 or 2.0 and choose Remove to uninstall them
Using regedit, navigate to HKLM\Software\Microsoft\.NETFramework and delete any keys and values that have 1.2 or 2.0 in it, including keys/values that are in subkeys underneath .NETFramework.
Using regedit, navigate to the sub-hive HKLM\Software\Microsoft\.NETFramework\Policy and delete any key or value that has 1.2 or 2.0 in it.
Using regedit, navigate to HKLM\Software\Microsoft\ASP.NET and delete any key or value that has 1.2 or 2.0 in it, including keys/values that are in subkeys underneath ASP.NET.
Right-click on My Computer and choose Manage. Expand Computer Management (Local), then Local Users and Groups, then click on the Users folder. In the right-hand pane, right-click on the ASPNET user account and choose Delete to remove it.
Go to %windir%\assembly and delete anything with *1.2* or *2.0* in the folder name. Delete the GAC_32 and GAC_MSIL folders as well.
You can not view the contents of %windir%\assembly in Windows Explorer when the .NET Framework is installed. In order to view the contents, you will need to set the following registry value and reopen Windows Explorer
Key name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion
Value name: DisableCacheViewer
Data type: REG_DWORD
Value data: 1
Note: You should remove the DisableCacheViewer value after you complete this step because this is only used for debugging purposes.
Go to %windir%\Microsoft.NET\Framework and delete any folders named v1.2.* or v2.0.* along with all of the files and subfolders they contain. You may get errors when trying to delete some of the files because they are in use. In most cases, rebooting the machine and trying again will work. If not, you can rename the files to be <filename>.old and then delete them after a future reboot.
Rename %windir%\system32\mscoree.dll to mscoree.dll.old.
After doing all of this, try to install the previously failing version of the .NET Framework 2.0.
If you have any trouble getting these steps to work correctly please let me know. Also stay tuned for a future post once I get the cleanup tool updated to work with .NET Framework 2.0 and post it for download.
After the removal procedure, reinstall the .NET framework versions plus all current updates in order. So, .NET framework 1.1, then all updates to that, then .NET framework 2.0, then all its updates.
Hope it helps,
David |
|
|
