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 Aaron,

    on startup (windows7)

    I get a root element missing message. Last few lines of setup verif are

    [04/20/13,12:35:27] Key: HKLM\SYSTEM\CurrentControlSet\Services\.NET CLR Data\Performance

    Value: Library

    Expected Data: netfxperf.dll

    Actual Data: netfxperf.dll

    [04/20/13,12:35:27] Key: HKLM\SYSTEM\CurrentControlSet\Services\.NET CLR Data\Performance

    Value: Counter Types

    [04/20/13,12:35:27] Key: HKLM\SYSTEM\CurrentControlSet\Services\.NET CLR Data\Performance

    Value: Counter Names

    [04/20/13,12:35:27] Section [Registry - .NET Framework 1.1 NT and higher (Wow6432Node)] - stop parsing entries

    [04/20/13,12:35:27] Not running action 'Files - .NET Framework netfxperf.dll' for product '.NET Framework 1.1 SP1' because the OS condition does not match

    [04/20/13,12:35:27] Verification succeeded for product .NET Framework 1.1 SP1

    any help welcome

  • Hi Peter P - What is the exact error message you see when you start up your Windows 7 computer?

    The entries from the verification log that you posted in your previous comment don't show any errors.  Could you please zip the full verification tool log file, upload it to a file server (such as http://skydrive.live.com), reply back here and post a link that I can use to download your log file and take a closer look?

  • I tried posting this message without signing in so it may show up twice. My bad!

    Aaron - Your program worked great verifying the net framework on my Windows-7 machine. Now for a bit of an unrelated issue. I need to install net framework 2.0 on a Windows-XP machine that doesn't have the net framework on it yet. The PC cannot be connected to the internet due to security measures in effect at work, so I need a way to do a total install without having to go online for any downloads. I will have to download the files at home and burn them to a CD or flash drive, but I don't know which files can do a full install. If you can point me in the right direction I would be very grateful since that information is not the easiest thing to find.

  • Hi BruceE52 - You can download the standalone version of the .NET Framework 2.0 SP2 from www.microsoft.com/.../details.aspx, or you can download the full version of the .NET Framework 3.5 SP1 (which also installs the .NET Framework 2.0 SP2 and 3.0 SP2 behind the scenes) from download.microsoft.com/.../dotnetfx35.exe.

  • Aaron using win7 sp1 and when downloading act 5.6 it requires .net 3.5 now when i load .net 3.5 error appear

    prompting window features to be altered i have used verification tool which indicates .net2.0 sp2 and .net 4 client and full version what can i try next

  • Hi johanloubser - Windows 7 includes the .NET Framework 3.5 SP1 as a part of the operating system, and it cannot be installed separately.  You can enable/disable the .NET Framework 3.5 SP1 by using the Windows Features control panel.

    If you see errors when trying to enable it in the Windows Features control panel, then I'd suggest trying the following:

    1.  Install the latest Windows service pack if you haven't yet.

    2.  Try to run the System Update Readiness Tool from support.microsoft.com/.../947821.

    3.  Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx.

    If none of the above help, you might need to repair/re-install Windows to fix this type of error.  It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.

  • Hi, Aaron, I have a problem with your tool.

    When I run your tool as administrator in normal boot environment after license dialog nothing is happening, but if I run it in safe mode everything is OK. Can you help me?

  • I forgot to write: I'm running Windows 7 SP1 and I tried on two PCs with same OS

  • Hi LionMK - I'm sorry for the hassles.  I haven't run into this behavior yet on my computers, and I haven't heard of any issues from anyone else until now.  Can you please check to see if the tool got far enough to be able to create any log files in %temp%?  If not, can you please check in the application event viewer to see if there are any errors/warnings that get reported there in this scenario?

  • Hi Aaron,

    I experienced same effect (nothing happened) reported by LionMK and because I ran netfx_setupverifier.exe using a combination of  history.txt examples so here's the fix I found :

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

    P.S. Any specific reasons why :

    A) inside my_error_log.txt I only found these 2 warnings below related to .NET Framework 1.1 only (my registry contained '.NET CLR 1.1.4322.2502') but nothing else for later .NET versions I checked ? (since I'm on Windows XP SP3 I'm only missing .NET 1.0 and 4.5)

    ...

    [06/24/13,17:13:29] ***WARNING*** Key: HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform

    Value: .NET CLR 1.1.4322

    Expected Data:

    Actual Data: NOT FOUND

    [06/24/13,17:14:53] ***WARNING*** Key: HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform

    Value: .NET CLR 1.1.4322

    Expected Data:

    Actual Data: NOT FOUND

    B) netfx_setupverifier.exe includes unicows.dll v1.0.4018.0 while latest I downloaded from MS site time ago was v1.1.3790.0 ?

    P.P.S. Because of above solution I reported, if you can, please feel free to let me receive some points on my account on social.msdn.microsoft.com/Profile

    Thanks in advance. Regards

    Rob

  • Hi _RobMer_ - Those 2 registry values are not required for the .NET Framework to function correctly, so the verification tool reports warnings instead of errors for them.

    The version of unicows.dll shouldn't affect any functionality on Windows XP.  That DLL was included for backwards compatibility for Windows 95/98 back when this tool supported those versions of Windows.  The tool no longer supports Windows 95/98 though.

  • Hi Aaron,

    many thanks for both clarifications.

    P.S. To let the tool run properly I hope in this page you can soon fix 'netfx_setupverifier.exe /q:a /c:"setupverifier.exe /a"' example to become 'netfx_setupverifier.exe /q:a /c:"setupverifier2.exe /a"' and then, in next tool version, also other examples inside readme.txt.

    Regards

    Rob

  • I've setup a fresh installation of Windows 2000 SP4 in a Virtual Machine and get the following error when checking if .NET 2 is installed.

    Error creating process <C:\DOCUME~1\Adm\Local Settings\Temp\IXP000.TMP\setupverifier2.exe>. Reason: C:\WINDOWS\system32\advpack.dll

    I've seen your previous comment about advpack.dll but this is a fresh 'out of the box' install of Windows 2000 so it ought to work.

    Andrew

  • Hi _RobMer_ - I've updated the command lines in the text of this blog post as you suggested, and I'll update readme.txt the next time I post an updated version of this verification tool to the download shares.

  • Hi Andrew - I updated the version of the Visual C++ compiler used to build the verification tool a while back, and when I did that, it caused the tool to no longer work on versions of Windows older than Windows XP.  You will not be able to use this tool on Windows 2000 as a result.  I'm sorry for the inconvenience.

Page 17 of 22 (326 items) «1516171819»
Leave a Comment
  • Please add 1 and 3 and type the answer here:
  • Post