BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

InfoQ Dev Summit Boston

Discover transformative insights to level up your software development decisions. Register now with early bird tickets.
InfoQ Dev Summit Munich

Get practical advice from senior developers to navigate your current dev challenges. Register now with early bird tickets.
QCon San Francisco

Level up your software skills by uncovering the emerging trends you should focus on. Register now.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News A Easier Way to Repair the .NET Framework

.NET

A Easier Way to Repair the .NET Framework

This item in japanese

Lire ce contenu en français

Bookmarks

May 12, 2016 1 min read

InfoQ Article Contest

Share your knowledge Win a ticket to a QCon event
or an InfoQ Dev SummitFind out more

Having a set of the .NET Frameworks that works correctly is important for all Windows users and developers are no exception.  Through the course of development, it is easy to accidentally overwrite needed files.  In an effort to minimize troubleshooting, Microsoft provides the .NET Framework Repair Tool.  This tool provides the ability to scan a Windows system for errors with any of the .NET Framework packages that are supposed to be installed.

The program may be executed via the command line or through a graphical wizard.  Command line switches are available which allow the tool to be run unattended and to enable proper .NET packages to be located on a network share (versus requiring Internet access).  There is also an option to disable the default behavior of sending a diagnostic log file to Microsoft after the tool has been executed.

The typical operation of the utility takes the following steps:

  1. Scan the machine for the known errors with .NET Framework installations and if found, provide a list to the user for ereview
  2. Take any of the following corrective measures:
    1. Ensuring Windows Installer service is properly operational
    2. Reset discretionary access control lists on system folders
    3. Verify and correct update registration
  3. If the actions in step 2 have not been successful in correcting the issue, provide user with an option to perform a full repair of the installed .NET Frameworks.
  4. Optionally send a CAB file containing system logs for transmission to Microsoft.

In a trial run on this author's machine, the program's operation took approximately 20 minutes.  When completed, a cab file was left in %TEMP% directory which contained all of the log files from my user directory's AppData.  The cab also included registry dump files for HKCR and HKLM (HKEY_LOCAL_MACHINE).

Full details on the program’s operation are available in a blog post by The .NET Fundamentals Team and in its corresponding KB article.  The latest version, V1.3, includes support for all .NET Frameworks through 4.6.1.  It supports operation on Windows operating systems through Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1.

Rate this Article

Adoption
Style

This content is in the .NET topic

Related Topics:
BT