April 19th, 2016

Introducing the Microsoft .NET Framework Repair Tool Version 1.3

This post was written by Rakesh Ranjan Singh, Senior Software Engineer on the .NET Setup team.

We are happy to announce the latest version of the .NET Framework Repair Tool that supports all versions of the .NET Framework from 3.5 SP1 to 4.6.1. This version of the tool adds support for .NET Framework 4.5.2, 4.6 and 4.6.1.

The .NET Setup team has made some significant investments over the last couple of years in improving the deployment experience for the .NET Framework setup and its updates. Occasionally, some customers will run into issues with deploying the .NET Framework or its updates that cannot be fixed from within the setup itself. For such cases, the .NET Framework Repair Tool can help with detecting and fixing some of the common causes of install failures.

How to Obtain the Latest Version of the Microsoft .NET Framework Repair Tool

The .NET Framework Repair Tool is available for download from the Microsoft Download Center.

For more information about the fixes and options in this revision of the tool, see the Knowledge Base Article KB2698555.

Using the Tool

The .NET Framework Repair Tool can be run in two ways:

  • With a wizard that will guide you through the various steps for scanning and fixing issues.
  • In Quiet/Passive Mode using command line switches. You will most likely use this option if you want to automate the process of running the tool for applying fixes, collecting logs, repairing specific versions, etc.

A common usage for quite/passive mode is:

This will run the tool in quiet mode, apply fixes/repairs for supported .NET Framework versions (excluding in box versions), collect logs in %temp% folder and send usage data to Microsoft.

You can find more details on tool usage and features can be found at Microsoft .NET Repair Tool blog post.

Providing Feedback

If you discover setup issues not currently addressed by this tool or have any other suggestions feel free to send us a note at netfxsetup@microsoft.com.

0 comments

Discussion are closed.