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
  • I have fixed the problem!

    I had to completely format my system drive and reinstall windows 7, only absolutely clean windows installation fixed it.

  • An excellent tool! Please see my post at forums.asp.net/.../4006570.aspx

  • LOL, Murray, what a genius solution. I hate this windows crap for this. You have a problem? Format and reinstall your system. Yay, great. Keep the user busy. Somehow …

  • Hi, everybody.

    Having exactly the same situation as Murray K. OS: Windows 7 x64 Ultimate.

    Verification tool is failing to run test application while verifying .Net Framework 4

    Log:

    [08/22/10,10:27:04] Beginning of new SetupVerifier error logging session

    [08/22/10,10:27:04] Activity log file location: C:\Users\Boos\AppData\Local\Temp\setupverifier_main_08-22-10_10.27.04.txt

    [08/22/10,10:27:04] Error log file location: C:\Users\Boos\AppData\Local\Temp\setupverifier_errors_08-22-10_10.27.04.txt

    [08/22/10,10:27:04] Build created on August 16, 2010

    [08/22/10,10:27:04] Detected operating system: Windows 7 (x64)

    [08/22/10,10:27:44] File C:\Windows\Microsoft.NET\Framework\sbscmp20_mscorlib.dll is not installed on the system

    [08/22/10,10:27:47] File C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpftxt_v0400.dll is not installed on the system

    [08/22/10,10:27:50] File C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\WPFFontCache_v0400.exe is not installed on the system

    [08/22/10,10:27:50] File C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpftxt_v0400.dll is not installed on the system

    [08/22/10,10:27:51] Process 'Netfx40TestApplication.exe' exited with return code -2146232576

    [08/22/10,10:27:51] Verification failed for product .NET Framework 4 Client

    [08/22/10,10:28:37] File C:\Windows\Microsoft.NET\Framework\sbscmp20_mscorlib.dll is not installed on the system

    [08/22/10,10:28:37] File C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpftxt_v0400.dll is not installed on the system

    [08/22/10,10:28:37] File C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\WPFFontCache_v0400.exe is not installed on the system

    [08/22/10,10:28:37] File C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpftxt_v0400.dll is not installed on the system

    [08/22/10,10:28:47] Process 'Netfx40TestApplication.exe' exited with return code -2146232576

    [08/22/10,10:28:47] Verification failed for product .NET Framework 4 Full

    [08/22/10,10:28:58] SetupVerifier exiting with return value 100

    It's also impossible to install MS Office 2010 because of error 2908 that is related to .Net Framework.

    Some ideas how to fix it?

  • Hi Fin - The verification log shows that a few files are missing, but those are expected to not be installed on Windows 7, so those are safe to ignore.  The test application is failing with an error that means "Failed to load the runtime."  This means that there is something wrong with the loading of the .NET Framework runtime on your computer for some reason.  Can you please run verification for the .NET Framework 3.5 as well as the .NET Framework 4 on your computer and see if it reports any issues?  Also, can you please let me know what the exact file version is for the file %windir%\system32\mscoree.dll and %windir%\syswow64\mscoree.dll on your computer?

    It might also help to try to uninstall the .NET Framework 4 (full and client profile) and then try again to install Office 2010.  The Office installer does not require the .NET Framework 4, and it should install correctly with the versions of the .NET Framework that come with the Windows 7 OS (.NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1).

  • gashto......the application was unable to star correctly (0x00007b)...what the hell is this....when i try to run my windows form application in visual studio 2005 ...it pops out ...and says press ok to terminate.....help help help....otherwise... i will die...

  • Hi Raja Tajamul Iqbal - I'm sorry for the hassles that this issue is causing for you.  This type of error could be a problem with the application itself or it could be something wrong with your .NET Framework or Windows.  Do you see this error for only that one specific WinForms application that you're working on, or for all applications on your computer?  Does it help to try to repair the .NET Framework by using the entries in the control panel on your computer?

  • Hi astebner,

    thanks for this tool. the old ones of tool doesn't give error, but the last one failed to verify the .NET Framework 1.1 SP1.

    If you want to try, please download .NET framework AIO from here;

    www.wincert.net/.../index.php

    here is the direct link;

    hotfile.com/.../XForce_dotnetaio_Addon.7z.html

    and then download this tool from the same page;

    hotfile.com/.../XForce_Setup_Verifier.7z.html

    you will see .NET Framework 1.1 SP1 does verify with this one. then try to verify .NET Framework 1.1 SP1 with the last verify tool above this page.

    yup!! It's failed.

  • Hi Alpercatak - I made a change to the verification tool earlier this week to allow errors to be treated as warnings for missing/incorrect registry keys.  I inadvertantly caused the .NET Framework 1.1 to start failing verification as a result of that change.  I've made a fix and posted an updated version of the verification tool this morning.  Could you please try again with the build of the tool dated October 15, 2010 or later and verify that it works as expected in your scenarios?

  • Hi again,

    @astebner it's ok now! Now it works as expected :) Thanks so much for your effort.

  • hi, the verification app verifies the .net but in the event log it is still showing an error: .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Service reached limit of transient errors. Will shut down. Last error returned from Service Manager: 0x80029c4a.

  • Hi Soldier1st - The HRESULT value that you're seeing (0x80029c4a) means "Error loading type library/DLL."  I don't know from this message exactly which type library or DLL is failing to load or why though.  The verification tool is not a 100% guarantee that everything in the .NET Framework is working correctly though, so I'd suggest trying to repair the .NET Framework and see if that helps solve this error.

  • Hi astebner,

    Got a bit of a problem. I'm running Windows 7 Home Premium, and a lot of programs I am trying to use bring back problems that say I need .NET Framework "v4.0.30319". I tried to install .NET Framework 4 Full, and it didn't work. Used your install verifier, and got some unusual errors, though they seem to be happening a lot from what other people here are reporting.

    "[11/08/10,20:17:58] ****ERROR**** Process 'Netfx40TestApplication.exe' exited with return code -2146232576

    [11/08/10,20:17:58] ****ERROR**** Verification failed for product .NET Framework 4 Full"

    Also happens with .NET Framework 4 Client. Did a full uninstall, then a reinstall. Didn't help. Did a full uninstall, cleaned out the %temp% folder, did a reinstall. Didn't help. Used your clean-up tool, did a reinstall. Didn't work. This has been vexing me something fierce, and I would greatly appreciate any advice you could send my way. Other than a full system wipe and reinstall...

    Did some searching, and you asked someone with a similar problem for the mscoree.dll versions in %windir%\system32 and syswow64. They both have the same version. File version "2.0.50727.4927". I'm not sure what to do here, but I know this can be fixed without a system wipe...

  • Hi Lacynth - I'm sorry for the hassles that this issue is causing for you.  Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to gather all of your .NET Framework setup log files, then upload the file named %temp%\vslogs.cab that this tool creates to a file server such as http://skydrive.live.com, then reply back here with a link I can use to download your logs and take a further look?

  • The .cab file is located at cid-8c3bbf819504dd6a.office.live.com/.../vslogs.cab Hope you can find something. Thank you for your time.

Page 3 of 24 (347 items) 12345»
Leave a Comment
  • Please add 2 and 6 and type the answer here:
  • Post