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

Introduction

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

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 David - That error means that the verification tool is failing to load shell32.dll on your computer.  It uses that DLL for looking up some common Windows folder paths, and if it fails to find that DLL, it should fall back to looking up those folder locations from the registry.  Do you see verification errors later in the process on this computer, or is this the only error you see?  If this is the only error, I believe it can be safely ignored because it shouldn't affect the ability to verify the .NET Framework install state.  That shell32.dll file should be a part of Windows Server 2003 though, so if it is failing to load, there may be something else wrong with your OS though.  You may need to run sfc /scannow to restore a copy of that file to your computer.

  • Hi Aaron, thank you for your help. It's the only error I have.

    I would like to use sfc /scannow, but it's asking me the SP2 cd for windows 2003, and SP2 was installed by WSUS. Windows 2003 SP2 x64 French is not available to download on Microsoft website (only in Japanese and English). I spoke to a Microsoft representative and he said that I need to open a service call for that!

  • Hi David - That's unfortunate.  Do you have another machine with that OS that you could cherry pick that file from in the meantime?

    Also, please note that the .NET Framework verification will fallback to using the registry in that scenario, so this missing file shouldn't block you from being able to verify the .NET Framework.  However, shell32.dll is a pretty fundamental part of the OS, so if it is missing, it would be good in a general sense to get that fixed on this machine.

  • Hi Aaron,

    shell32.dll is there.

    I would like to repair .NET framework 1.1 part of the OS, but I prefer to try a "sfc /scannow" before trying the procedure. I don't know if the repair procedure of the framework will ask me for the sp2 cd. It's on a production server, so I want to be sure.

    Thank you

  • Hi David - If the .NET Framework verification tool didn't report any errors besides that shell32.dll issue, then I don't know if there is any need to repair it.

    SFC will repair all files that are a part of the OS, including the .NET Framework.  If files are missing, it will ask for your original OS disc.

    If you'd like to, you can try the steps listed at blogs.msdn.com/.../431385.aspx to repair the .NET Framework 1.1 that comes with the OS on Windows Server 2003.

  • I attempted to install Turbo Tax 2010 on my desktop which has Vista.  The first error I got had me do the following:

    turbotax.intuit.com/.../SLN12263.html

    After that, it continually tells me the .NET Framework 3.5 Service Pack 1 verification failed.  I have tried to repair though the control panel, I have done the sfc /scannow, I have used your cleanup tool and tried to reinstall all .NET Framework versions and updates.  Nothing seems to work.  I have had different errors, including: setup.exe has stopped working and .NET Framework 3.0 is managed through "Turn Windows features on/off" (which will not configure either), corrupt files, etc.  I can also not open the 2009 Turbo Tax which worked fine in March 2010.  Any suggestions before I throw my computer out the window?  If I knew how I would send you the log files :)

    Thank you!

  • hi

    i getting following result. can anyone explain what is that?

    Section [Registry - .NET Framework 2.0 (32-bit)] - stop parsing entries

    [02/17/11,17:05:03] Not running action 'Registry - .NET Framework 2.0 (64-bit)' for product '.NET Framework 2.0' because the OS condition does not match

    [02/17/11,17:05:03] Not running action 'Registry - .NET Framework 2.0 (Wow6432Node)' for product '.NET Framework 2.0' because the OS condition does not match

    [02/17/11,17:05:03] Processing custom action 'Custom Action - .NET Framework 2.0 test application'

    [02/17/11,17:05:03] ExecutablePath = 'Netfx20TestApplication.exe'

    [02/17/11,17:05:03] FriendlyName = '.NET Framework 2.0 test application'

    [02/17/11,17:05:03] TimeoutSeconds = '300'

    [02/17/11,17:05:03] WaitOnExit = 'true'

    [02/17/11,17:05:03] Silent = 'true'

    [02/17/11,17:05:03] Launching process 'Netfx20TestApplication.exe' now

    [02/17/11,17:05:03] Process successfully launched. Waiting 300 seconds for it to complete.

    [02/17/11,17:05:03] ****ERROR**** Process 'Netfx20TestApplication.exe' exited with return code -1073741701

    [02/17/11,17:05:03] Section [Files - .NET Framework netfxperf.dll] - start parsing entries

    [02/17/11,17:05:03] File C:\WINDOWS\system32\netfxperf.dll (version 1.1.4322.573) is installed on the system

    [02/17/11,17:05:03] Section [Files - .NET Framework netfxperf.dll] - stop parsing entries

    [02/17/11,17:05:03] ****ERROR**** Verification failed for product .NET Framework 2.0

  • Hi Monica - If you have your .NET Framework verification log, can you please upload it to a file server such as http://skydrive.live.com and then reply back here and provide a link that I can use to download your log file and take a further look?

  • Hi Manish - The .NET Framework verification tool runs a small .NET application to verify that basic functionality works, and that application is failing on your computer for some reason.  The tool should create a log file named %temp%\setupverifier_netfx20testapp_*.txt with more detailed error information.  Can you take a look and see if you have that log file?

    Also, would it be possible for you to zip and upload your full verification log file to a file server (such as http://skydrive.live.com) and then reply back here with a link I can use to download your log files and take a further look?

  • Thanks Aaron,

    Here is the verification log.  You will be able to see how many times I have tried to repair .NET Framework and hopefully you can spot the problem and suggest a solution!

    cid-55c7d83cd0d2161c.office.live.com/.../cleanup%5E_main.log

    I appreciate any help you can offer!

    Monica

  • Hi Monica - I tried to download your log file, but SkyDrive told me that the file doesn't exist or was removed.  Can you please double-check the link and post an updated link so I can take a look?

  • Sorry, I am not too good at this :)

    Hope this helps:

    cid-55c7d83cd0d2161c.office.live.com/.../cleanup%5E_main.log

  • Hi Monica - I don't see anything that you should need to worry about in the cleanup log file.  Can you try to re-install the .NET Framework 3.5 SP1 from www.microsoft.com/.../details.aspx and see if that will allow you to install TurboTax?

    If you still get an error from TurboTax saying that the .NET Framework 3.5 SP1 is not installed, can you please see if you can find any TurboTax setup log files in your %temp% directory?  Also, could you try to run the .NET Framework verification tool and see if it reports any errors?  If it does report errors, please upload that log file as well.

  • When I try to re-install .NET Framework 3.5 SPI it says setup.exe has stopped working and the error log has this on it:

    [02/20/11,22:11:44] Microsoft .NET Framework 3.5 (x64) 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) 'package'. MSI returned error code 1603

    Here is the log after running the verification tool:

    cid-55c7d83cd0d2161c.office.live.com/.../setupverifier%5E_main%5E_02-20-11%5E_22.18.09.txt

    Sorry, I'm not having much luck finding log files in %temp%directory

    Again, thank you for your help!

  • Hi Monica - Your verification log files shows that the following file is missing:

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

    To fix this, you can do the following:

    1.  Open the folder C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG in Windows Explorer

    2.  Make a copy of the file machine.config.default

    3.  Rename the copied file that you created in step 2 above to be machine.config

    This might also help solve the .NET Framework 3.5 SP1 installation failure that you're seeing.  If 3.5 SP1 still fails after doing this, then can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your .NET Framework setup log files, upload the file named %temp%\vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com), and then reply back here with a link that I can use to download your log files and take a further look?

Page 5 of 23 (343 items) «34567»
Leave a Comment
  • Please add 4 and 3 and type the answer here:
  • Post