Article ID: 2698555
Microsoft has released version 2 of the Microsoft .NET Framework repair tool. This tool addresses frequently observed issues that may cause failures for installations of the .NET Framework. Version 1 supported the .NET Framework 4 and its updates. Version 2 extends support to the .NET Framework 3.5 SP1. (This includes the .NET Framework 3.0 SP2 and the .NET Framework 2.0 SP2.) Version 2 also adds offline support for computers that have limited or no Internet connectivity.
Version 2 of the .NET Framework repair tool is available for download from the following Microsoft Download Center website:
Microsoft .NET Framework Repair Tool
OverviewThe .NET Framework repair tool detects frequently occurring issues with the .NET Framework setup or updates. The tool tries to resolve those issues by applying known fixes or by repairing the installed version of the .NET Framework. The tool can also be used to repair corrupted installations of supported .NET Framework versions. This includes .NET Framework 4 language packs. The tool is wizard-based and is easy to use.
The .NET Framework repair tool follows a four-step process:
The tool may make one or more changes to the installed version of the .NET Framework. For example, it may correct the state of Windows Installer on the computer, reset the discretionary access control lists (DACLs) on certain folders, or resolve issues that are related to an invalid or corrupted update registration.
The .NET Framework repair tool provides an option to repair the versions of the .NET Framework that are installed on the computer (step 3 of the process) and requires the redistributable files of those versions to be available at the time of repair. By default, the tool downloads these packages from the Internet during repair. If your computer has limited or no Internet connectivity, you should use offline mode for repair. To do this, specify the /addsource option together with the path of the folder that contains the redistributable files, as in the following example:
NetfxRepairTool.exe /addsource \\SHARE_PC\SHARE_FOLDERIf the repair tool does not find the required redistributable in the specified folder, it will try to download the file from the Internet. The repair tool cannot do this if the required file cannot be downloaded. The following table lists the .NET Framework redistributable files.
Collapse this tableExpand this table
Data collectionThe .NET Framework repair tool collects information about tool usage in addition to collecting diagnostic installation data. The usage information is used to improve the quality of the .NET Framework repair tool, and the installation data is used to improve .NET Framework setup. This information is not used for marketing or sold to a third party. For more information, read the Microsoft .NET Framework Repair Tool Privacy Statement . You can download this statement from the following Microsoft Download Center web site:
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
Download the Microsoft .NET Framework Repair Tool Privacy Statement
Collapse this imageExpand this image
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
(http://support.microsoft.com/kb/119591/ )How to obtain Microsoft support files from online services
Note The data collection feature creates a compressed .cab file of the .NET Framework installation logs. After the tool processes the logs, a .cab file whose name starts with FixDotNet appears on the desktop. When you select Finish in the wizard, the tool sends the .cab file that contains the logs to Microsoft.
The .cab file stays on your desktop regardless of whether you decide to send the data to Microsoft.
Collapse this imageExpand this image
Applies to:The .NET Framework repair tool can be used to correct setup problems for the following configurations: