When you are experiencing issues with applications that depend on Microsoft's Net Framework, you have a few options at hand to troubleshoot those issues. If you are running Windows 7 or earlier, you could try the .Net Framework Cleanup Tool for a drastic approach that is removing all installed versions of the software from the system. You could alternatively try Microsoft's own .Net Framework Repair Tool which works for all versions of Windows.
If you want to dig deeper, the Microsoft .Net Framework Setup Verification Tool can come in handy, and it is this tool that just got updated to support the new Microsoft .Net Framework 4.5 and Windows 8. As the name suggests, you can use it to verify .Net Framework installations on Windows.
The .NET Framework setup verification tool supports verifying the following products:
- .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
- .NET Framework 4.5
By default, the .NET Framework setup verification tool will only list versions of the .NET Framework that it detects are installed on the computer that it is being run on. As a result, the tool will not list all of the above versions of the .NET Framework. This product filtering can be overridden by running the .NET Framework setup verification tool with the following command line switch:
netfx_setupverifier.exe /q:a /c:"setupverifier.exe /a"
When you first start the program after installation you are presented with a menu that is displaying all .Net Framework versions that are recognized on the system.
All you need to do is select the product that you want to verify and click on the verify now button afterwards to start the process. The program checks all selected Framework files then, a process that should not take longer than a few seconds, and reports back to you whether the product verified successfully or not.
You can click on the view log button in case it did not verify, to check which files or Registry keys and values that belong to the framework did not verify. Your best bet then may be to uninstall the Framework that failed the verification to reinstall it afterwards on the system. If that fails, you still have the Cleanup Tool and the Repair Tool available that you could use to resolve the situation.
You can download the latest version of the Microsoft .Net Framework Verification Tool from Aaron Stebner's website where it is available for all supported operating systems (including Windows 8).
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.