Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

.NET Framework Setup Verification Tool User's Guide

.NET Framework Setup Verification Tool User's Guide

Rate This

.NET Framework Setup Verification Tool User's Guide


This .NET Framework setup verification tool is designed to automatically perform a set of steps to verify the installation state of one or more versions of the .NET Framework on a computer.  It will verify the presence of files, directories, registry keys and values for the .NET Framework.  It will also verify that simple applications that use the .NET Framework can be run correctly.

If the verification tool finds any issues, there is a .NET Framework Repair Tool that can be found at the following locations:

Additional support can be obtained by visiting the .NET Framework setup forum at http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/threads.

Download location

The .NET Framework setup verification tool is available for download at the following locations:

The .zip file that contains the tool also contains a file named history.txt that lists when the most recent version of the tool was published and what changes have been made to the tool over time.

Supported products

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
  • .NET Framework 4.5.1
  • .NET Framework 4.5.2
  • .NET Framework 4.6

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:"setupverifier2.exe /a"

Silent mode

The .NET Framework setup verification tool does not support running in silent mode.

Exit codes

The verification tool can returns the following exit codes:

  • 0 - verification completed successfully for the specified product
  • 1 - the required file setupverifier.ini was not found in the same path as setupverifier.exe
  • 2 - a product name was passed in that cannot be verified because it does not support installing on the OS that the tool is running on
  • 3 - a product name was passed in that does not exist in setupverifier.ini
  • 100 - verification failed for the specified product
  • 1602 - verification was canceled

Log files

This verification tool creates 2 log files by default that can be used to determine what actions the tool is taking and what errors it encounters while verifying a product.  The 2 log files are listed below, and they are created in the %temp% directory by default.  Note that you can find the %temp% directory by clicking on the Windows start menu, choosing Run, typing %temp% and clicking OK to open the directory in Windows Explorer.

  • %temp%\setupverifier_main_*.txt - this log contains information about all actions taken during a verification tool session; it will include information about each resource that the tool attempts to verify for a chosen product and whether or not that resource was found on the system; this log tends to be fairly long, so errors will be logged with the prefix ****ERROR**** to make it easy to search and find them
  • %temp%\setupverifier_errors_*.txt - this log only contains information about any errors found during verification of a chosen product
  • %temp%\setupverifier_netfx20testapp_*.txt - this log contains error information for the .NET Framework test application that is run by the verification tool.  This log will only be created if there is an error while running the test application.

A new pair of log files will be created each time the verification tool is launched.  The date and time the tool is launched will be appended to the end of the log file names by default in place of the * in the names listed above.  If you want to control the exact names used for the log files, you can use the following command line parameters:

  • /l <filename> - specifies a name to replace the default value of setupverifier_main_*.txt for the main activity log for the verification tool
  • /e <filename> - specifies a name to replace the default value of setupverifier_errors_*.txt for the error log for the verification tool

For example, the following command line will allow you to specify non-default names for both log files:

netfx_setupverifier.exe /q:a /c:"setupverifier2.exe /l %temp%\my_main_log.txt /e %temp%\my_error_log.txt"


Attachment: netfx_setupverifier_new.zip
  • Hi Brian THOMAS - I don't know how to explain why the test application is returning an access denied error like this.  The test application is a very small, simple .NET Framework application that is designed to tell whether or not basic .NET Framework functionality is working on a computer.  If it fails to run, it usually means that there is something fundamentally wrong with the .NET Framework on the computer.

    Do you see any problems running other types of .NET Framework applications on this computer?  For example, you can try running MMC because the version of MMC in Windows 7 uses the .NET Framework.

  • Aaron:  Ignore my last comment because evidently everything was extracted and the verification tool report success.  Why then doesn't my Turbo Tax product load?????

  • Hi Barbara - If the verification tool is reporting success but TurboTax still won't launch, then I think you'll need to contact TurboTax technical support for more in-depth troubleshooting assistance.

  • Hi Aaron: I've been trying to install .Net Framework 4.0 Full on a PC running Windows XP 32 bit. I downloaded the freestanding installers for both the 64 - 86 Full and the smaller 86 Full, using IE. With either install, the results are installation of (i) .Net 4.0 Extended and (ii) .Net 4.0 Client Profile. The problem is that a software program I just purchased specifically requires the presence of Full rather than Client Profile. The developer stated that he was having this problem with some other clients as well and feels that it is a problem with the .Net Installer. This is somewhat of a dilemma, because his program has to see "Full" in order to open. Do you have any suggestions for loading the Full version rather than the Client Profile?

  • Hi Genome58 - The installer for the .NET Framework 4 Full will install the client profile and the extended package.  Based on what you describe, it sounds like you have the .NET Framework 4 Full correctly installed.  If the application you are trying to use doesn't recognize that Full is installed on your computer, then that sounds like a bug in the application.  Do you know exactly what they're checking for when they try to figure out whether or not you have Full installed?

  • Hi Aaron,

    I was referred to your blog when TurboTax 2012 would not install due to .NET errors.  I am running Windows 8 Pro 64-bit so I downloaded and ran your .NET Framework Setup Verification for .NET Framework 4.5. The product verification fails, but I do not know what to make of the log.  The log indicates that 2.0, 3.0, 3.5, 4 and 4.5 are all installed.  However, at the bottom of the log I have the following errors:

    ****ERROR**** Process 'Netfx40TestApplication.exe' exited with return code -532462766

    ****ERROR**** Verification failed for product .NET Framework 4.5

    I do not know how to interpret this and any help would be appreciated.  Thank you.

  • Hi ShaneG - I don't recognize that error code for the Netfx40TestApplication.exe process.  That application is a very simple application that is designed to tell whether or not basic .NET functionality is working on the computer.  If that fails, it usually means that something is fundamentally wrong with .NET.  Could you please try to do the following to see if the test application will give a more useful error message on your computer to help with troubleshooting?

    1.  Run the .NET Framework verification tool

    2.  Leave it on screen and go to the folder %temp%\IXP000.tmp

    3.  Run %temp%\IXP000.tmp\Netfx40TestApplication.exe /u

    Hopefully this will give a more useful error message and we can figure out next steps to correct this issue from there.

  • Hi all,

    I downloaded the 3.5 update, clicked the checkbox in 'Turn on and off features', then went through the verification tool and everything checked out, but the site that needs to utilize the updated .Net Framwork 3.5 still says I need to upgrade. Thoughts?

  • Hi Mitch - This issue could be a compatibility problem with the site.  You might want to search to see if the site you're trying to use has any known compatibility issues with newer versions of Windows.

  • Aaron,

    I've scripted some client checks around the silent mode of this utility, is there a particular reason this functionality was removed?

  • Hi Clint - There were application compatibility issues that led me to remove silent mode from this tool.  You can find more details about this change in the post at blogs.msdn.com/.../10349253.aspx.

  • Hi Aaron, pretty much every machine in my small office has .net security windows update errors (all windows xp sp3) Some of the machine have software that requires various service packs. Just looking through your verifier on my machine and in .NET 2.0 I have this warning;

    ***WARNING*** File C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Security.dll is not installed on the system

    A while back I had searched and found many microsoft articles about repairing/re-installing different versions of .NET. Can you recommend your favorite how-to guide for completely cleaning a Windows XP SP3 system of .NET and re-installing them in the right order so that all windows updates work correctly? Why are these .NET packages so difficult to keep in good working order??!!

  • Hi Justin - The steps I recommend most often to remove and re-install the .NET Framework to fix .NET Framework security update installation errors are the ones listed at blogs.msdn.com/.../8108332.aspx.  Can you please take a look and see if those steps help in your scenario?

  • Hi Aaron,

    How are you? could you help me to fixed this problem about .net framework 4.o

    i download it  but i received a message like this:

    Blocking Issues:

    You must install the 32-bit Windows Imaging Component (WIC) before you run Setup. Please visit the <A HREF="go.microsoft.com/fwlink Download Center</A> to install WIC, and then rerun Setup.

  • Hi Yas - The .NET Framework 4 requires the WIC component, but it doesn't install it automatically if it is missing like previous versions of the .NET Framework did.  You'll need to download and install it yourself to resolve this error.  You can download a version of WIC that is compatible with the .NET Framework 4 at www.microsoft.com/.../details.aspx.

Page 16 of 25 (372 items) «1415161718»
Leave a Comment
  • Please add 1 and 2 and type the answer here:
  • Post