The troubleshooting of .Net Framework issues should begin with an assessment of the installed versions of the Framework on the operating system. The tool for that is the .Net Framework Setup Verification Utility. It supports all versions of the .Net Framework, here is the full list valid as of today:

• .NET Framework 1.0
• .NET Framework 1.1
• .NET Framework 1.1 SP1
• .NET Framework 2.0
• .NET Framework 2.0 SP1
• .NET Framework 2.0 SP2
• .NET Framework 3.0
• .NET Framework 3.0 SP1
• .NET Framework 3.0 SP2
• .NET Framework 3.5
• .NET Framework 3.5 SP1
• .NET Framework 4 Client
• .NET Framework 4 Full

It is important to always run the latest version of the installed .Net Framework on the system. This means that you should run .Net Framework 3.0 SP2 and not .Net Framework 3.0. The setup verification tool scans the computer for installed .Net Framework versions and displays them in a listing. Even better is that it can be used to verify the integrity of those installations.

To verify a .Net Framework installation pick the product from the pulldown menu and select Verify Now. The application scans the system and will display the status of the analysis in the end. The message Product verification succeeded indicates that that scanned .Net Framework version is installed correctly on the system. Two log files are automatically generated, the important log for troubleshooting the framework is the error log. Both log files are stored in the system cache.

The verification needs to be run for every installed .Net Framework version. There are two possibilities now. The first is that all verifications have completed successfully. That’s great as it means that the .Net Framework is working properly and that a corrupt installation is not the cause of the issues experienced on the PC. Users who do not have the latest .Net Framework version installed may consider installing it to see if it resolves the issues they are experiencing.

Users with corrupt or damaged framework installations need to fix those issues before they can run programs that depend on the framework in Windows. There are two possibilities for this. They may want to try and uninstall the damaged frameworks from the “uninstall a program” control panel applet.

This may or may not work depending on the individual situation. The best alternative for this scenario is to remove the full .Net Framework from the system, with full meaning all product versions. It is then possible to reinstall the desired .Microsoft .NET Framework after the old installation has been removed completely from the computer system.

The tool of choice for this procedure is the .NET Framework Cleanup Tool which supports the following product versions.

• .NET Framework – All Versions
• .NET Framework – All Versions (Tablet PC and Media Center)
• .NET Framework – All Versions (Windows Server 2003)
• .NET Framework – All Versions (Windows Vista and Windows Server 2008)
• .NET Framework 1.0
• .NET Framework 1.1
• .NET Framework 2.0
• .NET Framework 3.0
• .NET Framework 3.5
• .NET Framework 4

Please note that the cleanup tool will only offer to remove framework versions that are not part of the operating system. This means for instance that Windows 7 users will only see an option to remove the .NET Framework 4.0 if it is installed and not the versions 2.0, 3.0 or 3.5.

Have another tip on troubleshooting .Net Framework issues? Post it in the comments.

The newest iteration of the framework improves on the current ones. It introduces several new features as well as performance improvements that both developers and end users will benefit from.

Some of the more important changes are:

• Performance improvement including better multicore support, background garbage collection, and profiler attach on server.
• Easier debugging including dump debugging, Watson minidumps, mixed mode debugging for 64 bit and code contracts.
• Added support for Windows 7 multi-touch, ribbon controls, and taskbar extensibility features.
• Improvements in performance and scalability.
• Visual improvements in text clarity, layout pixel snapping, localization, and interoperability.

A full list of changes is available on this Microsoft page.

Microsoft .NET Framework 4 Download

Microsoft is giving more weight to the web installer in their announcements. They are often not mentioning that a standalone installer is available as well. Here are the links to both the offline and online installer of the .net Framework 4.

• Microsoft .NET Framework 4 (Web Installer)
• Microsoft .NET Framework 4 (Standalone Installer)

The standalone installer has a size of 48 Megabytes and contains all the files needed to install the new framework which means it does not have to load additional components from the Internet; Ideal for installing the Microsoft .NET Framework 4 on offline computer systems with no direct Internet connection.

The web installer weights in at less than 1 Megabyte but requires an Internet connection to download the remaining components during installation.

Both links point to the English version of the .net Framework 4.

Microsoft .NET Framework 4 requires at least Windows XP SP3, Windows Vista SP1 and will run on both 32-bit and 64-bit editions of those operating systems.

Applications that require the Microsoft .net Framework 4.0 will – as usual – trigger a download of the component if it is not already installed on the user’s PC.

Many programs that are developed for the Windows operating system make use of the framework that needs to be installed before software that uses it can be installed or run. Verifying that the .net Framework has been installed correctly is an important task especially for business environments but also for users who experience error messages or other problems with the net. Framework.

The Microsoft .Net Framework Setup Verification Utility can verify the installed .net Frameworks. It will only display those frameworks that it detects to be installed on the computer system it is executed on.

This limitation to the installed versions can be overridden with a command line parameter.

netfx_setupverifier.exe /q:a /c:"setupverifier.exe /a"

The program can also be run in silent mode which will process the command without showing the graphical user interface.

netfx_setupverifier.exe /q:a /c:"setupverifier.exe /p "

The program will start the verification of the selected .net Framework after selecting one of the available options in the pulldown menu and a click on the Verify Now button. The result will be echoed in the graphical user interface. More interesting for most users is the log file that is created by the program. This log file contains detailed information about the verification steps. It will for instance display all the files that are installed with the selected net Framework and their status.

This log file can be used to analyse problems which usually come down to missing files or Registry entries.

The Microsoft .Net Framework Setup Verification Utility can be downloaded from the developer’s website over at MSDN. The website contains additional information and command line parameters.

All In One Runtime offers an efficient (critics would probably call it unnecessary or overkill) solution to the problem. The program checks the installed runtimes of the Windows operating system and will automatically display and install the runtimes that are not installed on the PC system.

The supported runtimes are:

• Microsoft .net Frameworks
• .net language packs
• System runtimes
• Visual C++ runtimes
• Microsoft Visual J#
• Adobe Flash Player
• Microsoft Silverlight
• Shockwave Player
• Java Runtime Environment
• DirectX

The program will display the runtimes that it intends to install. A 30 second countdown will be displayed allowing the user to pause and cancel the installation or remove runtimes from the installation. All In One Runtime is a portable software program for Microsoft Windows operating systems. Supported are 32-bit and 64-bit editions of Windows XP, Windows Vista and Windows 7. The download is available on a German website. The developer’s website is also only available in German.

Update: The program now offers options to install only the selected runtimes on the system. That’s better than just blindly installing all missing ones. The program has recently been updated to include runtime updates. The latest version will for instance install the latest version of Adobe Flash Player if missing on the system. It is still recommended to check for program updates after the installation to make sure that all runtimes are up to date (especially those with web browser plugins).

The Microsoft .net Framework comes in various versions that build up on each other. The current versions that are mostly used by software developers are the Microsoft .net Framework 2.0, 3.0 and 3.5 with their respective Service Packs.

A user with .net Framework 3.5 installed will also have the versions 3.0 and 2.0 on his computer whereas someone with the Microsoft .net Framework 3.0 will only have version 2.0 installed as well.

The concept is not that hard to grasp but it is still confusing as to why so many different .net Framework versions are installed on the computer. That’s where the .net Version Detector (via Raymond) comes into play.

The portable software scans the computer system for installed .net Framework components and displays the results in a list. It will also list the root directory of the Microsoft .net Framework on the computer system and provide download links to versions that have not been installed yet.

This software makes the detection easier. Experienced users could also look in the System Control Panel and see which versions of the .net Framework are installed there which will give the same information except for the root directory and the download links.