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 Lacynth - The logs you sent show a similar problem to the ones I've looked at previously.  There is a component of .NET Framework 4 setup that is failing to install correctly on your computer.  The failing component is the one that updates mscoree.dll to a 4.0 version, and that failure causes the .NET Framework 4 to fail to work after installation.

    The logs you sent show the following error:

    Launching CreateProcess with command line = wusa.exe "C:\Users\Lacynth\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\Windows6.1-KB958488-v6001-x64.msu" /quiet /norestart

    Exe (C:\Users\Lacynth\AppData\Local\Temp\Microsoft .NET Framework 4 Setup_4.0.30319\Windows6.1-KB958488-v6001-x64.msu) failed with 0x80240017 - (null).

    MSU packages are OS update packages, and from what I can tell, it doesn't look like your computer has had any successful OS update installations since back in May (the most recent entries in your cbs.log file are from May).  Are you able to install anything from Windows Update on your computer currently?  Also, if you run optionalfeatures.exe, does it correctly show you a list of Windows features on your computer and allow you to uninstall + re-install Windows features?

  • No, optionalfeatures.exe shows nothing. But, the stuff from Windows Update SAYS it installed... Um, how would I go about fixing this? And what could have happened to cause it?

  • Hi Lacynth - If there is nothing listed in your Windows Features control panel (optionalfeatures.exe), then this usually means that there is something wrong with your OS component store, and that can also cause OS updates (like the .NET Framework 4. KB958488 update) to fail to install.  I usually suggest trying the System Update Readiness Tool and the steps listed at blogs.msdn.com/.../9303167.aspx to see if that will help solve this problem.  Hopefully it will work for you as well.

    I'm not sure how a computer gets into this type of broken state though.  I've only ever seen computers after they were already in the broken state, and I wasn't able to reverse engineer how they got broken in the first place.

  • Did all that, and the SUR Tool came back without any errors... Being hopeful, I uninstalled and reinstalled .NET Full 4, running the clean-up tool in between, and ran the verifier. Still broken. Same error. I'm really not sure what do here.

  • Hi Lacynth - If CheckSUR didn't report any problems, then I'm not sure what else to suggest.  I think you may need to repair Windows to solve this type of problem.  Before doing that, you may want to try to contact Microsoft technical support to see if they have any more targeted workarounds that they can offer you for this type of problem.  You can find contact information for the support team at http://support.microsoft.com, and you should be able to get free support for this type of installation issue.

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

    ****ERROR**** Verification failed for product .NET Framework 4 Client

    Unfortunately, the only fix so far on the net about this error code is to basically format/reinstall windows. In most cases a simple repair/restore wasn't good enough either. So while there is a way to resolve the problem, its not really a fix since it requires reinstalling windows itself. This is ridiculous and I'm seeing a lot of people with this issue as I search for solutions but no official word on the bug as a known issue. If anyone else has a fix that doesn't require reinstalling windows please post if you stop by here.

  • Hi .Net 4.0 fails - The error from the test application most often means that the CLR cannot start on the computer, and no .NET Framework 4 applications will run in that scenario.  The cases I've seen of this error so far have been caused by a part of the .NET Framework 4 failing to install behind the scenes.  You can tell if you're hitting the scenario that I've seen so far by checking the version number of mscoree.dll.  A successful install will have version 4.0.* of that DLL, whereas a bad install will have version 2.0.* of that DLL.

    The cases I've seen so far have been unable to install updates from Windows Update and/or unable to install/uninstall features in the Windows Features control panel because the OS component store was in a broken state.  The .NET Framework 4 installs an OS update to modify mscoree.dll, and so if the OS component store is broken, that part of the .NET Framework 4 setup will fail.

    I typically suggest trying the steps + tool listed at blogs.msdn.com/.../9303167.aspx in this type of scenario, but unfortunately that doesn't work in all cases, so it might be necessary to repair/re-install Windows to solve this type of problem.  I'd suggest contacting Microsoft technical support to see if they have any other options for you to try before resorting to re-installing Windows though.  You can find contact information for them at http://support.microsoft.com.

  • Hi Mike Stubner,

    No need to use your tool I tried for interest. Unfortunately. After using your tool "PC-WELT-Tool FixDotNetFramework" on the following article:


    I got just problems:

    -Driver Sweeper not loading anymore

    -Tuneup 2011 demands to reinstall

    To turn XP one day back was possible but didn't help.

    Before using your tool: 0 (zero) updates

    After using your tool:

    Windows update replies: The following couldn't be installed!

    Microsoft .NET Framework 3.5 SP1- und .NET Framework 2.0 SP2-Sicherheitsupdate für Windows 2000, Windows Server 2003 und Windows XP x86 (KB979909)

    Microsoft .NET Framework 3.5 SP1-Update für Windows Server 2003 und Windows XP x86  (KB982168)

    Sicherheitsupdate für Microsoft .NET Framework 2.0 SP2 und 3.5 SP1 unter Windows Server 2003 und Windows XP x86 (KB2418241)

    Sicherheitsupdate für .NET Framework 2.0 SP2 und 3.5 SP1 unter Windows Server 2003 und Windows XP x86 (KB983583)

    Update für .NET Framework 3.5 Service Pack 1 für .NET Framework Assistant 1.0 x86 (KB963707)

    Microsoft .NET Framework 3.5 SP1- und .NET Framework 2.0 SP2-Update für Windows Server 2003 und Windows XP x86 (KB982524)

    Sicherheitsupdate für Microsoft .NET Framework 3.5 SP1 unter Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008 x86 (KB2416473)

    Reinstall of Tuneup was successful not for Driver Sweeper.

    Tried to download again your tool from site mentionned: not possible, replies "The setup files are corrupted. Pls obtain a new copy of the program"

    - A yellow flag with a ! inside is waiting on the lower right to install the 7 updates. Will not succeed.

    Is there a deinstallation/rollback of your program or other way to fix instead of reinstallatin on whole XP?

  • Hi Ron - I'm sorry for the hassles that this issue is causing for you.  It looks like the tool on that site is a version of my cleanup tool, not the verification tool described in this blog post.  You can find the cleanup tool user's guide at blogs.msdn.com/.../8904493.aspx.

    You shouldn't need to reinstall Windows XP to solve this type of issue.  I'd suggest using the steps listed at blogs.msdn.com/.../8108332.aspx to fully remove the .NET Framework from your computer, then re-install the .NET Framework 3.5 SP1, then check for the latest updates on Windows Update.

  • ¿ayuda¡¡¡ con el net framework ¡¡¡¡?

    no puedo iniciar el programa para hack pet society me sale error¡¡ dice : para ejecutar esta aplicacion debo instalar la versiones net framework: v4.0.30319 pongase en contacto con el editor de la aplicacion para obtener instrucciones sobre como tener la version adecuada de net framework.

    y yo tengo el net framework 4.0 es el mas nuevo verd??? o que devo0 hacer para poder abrir este programa xfax ayudeme

  • Mike Stubner, have you had any experience with using this tool to manage multiple servers?  I manage 150 web servers and I would like to run a report to provide status of .Net for verification purposes.  Is there a version that supports the remote management of various servers and returns the status of each framework?   In advance, thank you

  • Hi Ronny - I didn't specifically design this tool to manage multiple servers.  If you have a way to remotely execute processes on each machine, you could run the verification tool in silent mode (using command line switches described above in this blog post) and then gather the log files for analysis or something like that.

  • I have a new HP Laptop Computer with Windows 7 on it.   I have been trying for over 3 months, and through about 35 hours on the phone with TurboTax trying to install my 2010 tax preparation software, but it keeps stopping the installation because it is unable to verify that the .NET Framework 3.5 SP1 is installed on this machine.   We have used the verification tool and the cleanup tool.   We have attempted to re-install the .NET Framework.   Nothing is working.   Can you please tell me how to make TurboTax 2010 work with Windows 7.  (P.S.  have also tried to use .NET Framework 4, but TurboTax does not like it either and keeps running into the problem when trying to verify .NET Framework 3.5 SP1, which is what the program was designed to coordinate with.   HELP PLEASE!!!!!!!    Ladena Bough 417-276-5010

  • Hi Ladena Bough - I'm sorry for the hassles that this issue is causing for you.  The log file from the verification tool that you provided shows that the following 2 files are missing from your computer:

    [02/02/11,10:12:26] ****ERROR**** File C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config is not installed on the system

    [02/02/11,10:12:27] ****ERROR**** File C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config is not installed on the system

    There are files in those folders that are named machine.config.default.  I'd suggest making copies of machine.config.default in each of those locations, then renaming the copies to machine.config in order to replace each of those missing files.

    Hopefully this will be enough to cause TurboTax setup to correctly detect the .NET Framework and allow you to install.

  • In setupverifier_errors log, someone know what this error mean?


    [02/10/11,14:17:35] Beginning of new SetupVerifier error logging session


    [02/10/11,14:17:35] Build created on January 17, 2011

    [02/10/11,14:17:35] Detected operating system: Windows Server 2003 (x64)

    [02/10/11,14:17:35] ****ERROR**** GetModuleHandle failed for 'shell32.dll' with error code 1114 - Une routine d'initialisation d'une bibliothèque de liens dynamiques (DLL) a échoué.

    Sorry for the french part, it's on a french Windows server 2003 sp2.

Page 4 of 26 (376 items) «23456»
Leave a Comment
  • Please add 6 and 5 and type the answer here:
  • Post