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
  • .NET Framework 4.6.1

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_2015_12_18.zip
  • It seemed successful - I followed your steps, ran the clean up tool and reinstalled .NET Framework 3.5 SP1 and it all seemed to finally work.  However, Turbo Tax still doesn't think so and gives me the Error 123 which basically tells me to use the cleanup tool again.  So here is the vslogs created by the collection tool.  Maybe there is something there.


    Thank you for your continued help!

  • Hi Monica - In scenarios like this where the .NET Framework 3.5 SP1 is successfully installed but TurboTax won't install or run correctly, your best bet is to contact the TurboTax technical support team for more in-depth troubleshooting assistance because this sounds like an issue within their product as opposed to a general problem with the .NET Framework.

  • I have a new computer with Win 7. It seems that TurboTax does not work well with Win 7. While installing 2010 tx yr I had to go through a helluva procedure to install it (patches, utilities etc etc). Then I tried to load the 2 earlier years and had the same problem. I called TTax support and they were very helpful although it took 3 hours to get all installed, they did stay with me. I have used TTax since the 80's and this is a first! They say the problem really is with Microsoft and both Vista and Win 7. Win 7 was supposed to fix Vista's probs. but it seems it created new ones. Typical of Microsoft. They can't leave a good thing alone and really don't care that all your old software won't work even in compatibility mode. Its their attitude of "We're Microsoft and screw you"! At least this year you can get someone on the phone with TTax! That's an improvement instead of these stupid FAQ's pages of endless problems that seldom have what we are experiencing.

  • Seems Turbo tax is giving many people fits this year. My issue is that upon finishing installation I cannot run the program. I get Turboax.exe application error. I have the option to try to de-bug but, upon clicking de-bug it tells me no de-bugger found. Went to Ttax support and it said I have .NET framework issues which led me to this site. I am not very litertate in computer speak and your blog reads like a foreign language. Any help for a non-computer speak user? My computer is running WindowsXP and I had no issues last year.

  • I am running Windows 7 x64. I bought Windows Office 2010, and I can not install it. I keep getting Error #1935. I have heard that this is a .NET Framework issue. How do I fix this? I noticed that I have two .NET Framework 4 programs on my computer... Client Profile and Extended.Are both of these needed? Should I delete one... or both... to get this program installed?

  • Hi Linda - I am able to help troubleshoot errors that occur during .NET Framework installation or verification.  In this scenario, it sounds like you were able to install the .NET Framework with no errors, but TurboTax won't run afterwards.  I typically suggest contacting TurboTax technical support to get help figuring out why TurboTax won't run.  Did you talk to anyone on the TurboTax support team, or did you just read about this issue on their web site?  If you talked to someone, did they tell you why they think this is a .NET Framework issue as opposed to an issue with TurboTax itself?

    If you would like to be sure that the .NET Framework is installed properly, you can try to use the steps and the cleanup tool described at blogs.msdn.com/.../8108332.aspx to fully remove all versions of the .NET Framework from your computer, then re-install the .NET Framework 3.5 SP1.

    If TurboTax still will not work correctly after re-installing the .NET Framework 3.5 SP1, then I think the TurboTax support team needs to take a closer look at your computer.

  • Hi Ken - Some 1935 errors can be caused by issues with the .NET Framework, but not all of them.  I would need to look at your Office 2010 setup log files to narrow this down further.  The logs should be located in your %temp% directory, and you should be able to find them by sorting that directory by last modified date and looking for the files created at the time that you tried to install Office 2010.  Can you please take a look and see if you can find your Office 2010 setup log files, then zip them up, upload the zip file to a file server (such as http://skydrive.live.com), then reply back here and post a link that I can use to download your log files and take a further look?

  • If you already have dlmgr.dll located in your computer, simply copy that file into C:\Windows\Microsoft.NET\Framework\<your latest .net version>\ Start the installer again. I have a version of Visual Web Developer Express 2010 installed and took the dlmgr.dll from there. Hope this helps those who need it.

  • Hi Pollen Burst - What type of error were you seeing in the scenario where you copied dlmgr.dll to that location?  You shouldn't ever need to do something like that - if that file is needed, it will be in the .NET Framework setup package.

    Also, please note that this file is not used by all versions of .NET Framework setup.  Only the .NET Framework 2.0 SP1 and SP2, 3.0, 3.0 SP1 and SP2, 3.5 and 3.5 SP1 use it to download files during setup.  The .NET Framework 1.0, 1.1, the original version of 2.0, and 4 do not use it.

  • Hi,

    I've asked these questions in several newsgroups, but didn't got any answers, so far. Based on your contributions you might be able to help me.

    The system is XP Prof 32bit with SP3 and at that time .Net 3.5 SP1 and all updates installed.

    As a precondition for a program I need to install ASP.NET 2.0 AJAX

    Extensions 1.0. The installation goes through but at the end all steps are rolled back. The logfile contains the following information:

    Action 22:16:27: RollbackCleanup. Removing backup files

    ExecNetFx:  Microsoft (R) CLR Native Image Generator - Version


    ExecNetFx:  Copyright (C) Microsoft Corporation 1998-2002. All rights


    ExecNetFx:  Installing assembly System.Web.Extensions,

    Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35

    ExecNetFx:  Fehler beim Laden der Typbibliothek/DLL. (Exception from


    ExecNetFx:  Error 0x8007006d: failed to allocate output string

    ExecNetFx:  Error 0xffffffff: Command line returned an error.

    ExecNetFx:  Error 0xffffffff: failed to execute Ngen command:

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ngen.exe install

    "System.Web.Extensions, Version=1.0.61025.0, Culture=neutral,


    Action 22:16:28: Rollback. Rolling back action:

    I deinstalled all installed .NET-versions and installed only .NET 2.0 but the problem remains.

    In the event log the following error appears:

    .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.

    A search regarding this error recommends the following commands:

    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>ngen.exe ExecuteQueuedItems

    Microsoft (R) CLR Native Image Generator - Version 2.0.50727.42

    Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.

    Fehler beim Laden der Typbibliothek/DLL. (Exception from HRESULT:


    C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>ngen.exe Update

    Microsoft (R) CLR Native Image Generator - Version 2.0.50727.42

    Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.

    Fehler beim Laden der Typbibliothek/DLL. (Exception from HRESULT:


    I also tried to deinstall all .NET-Versionen with dotnetfx_cleanup_tool

    yielded no other results.

    What's wrong with my system?

  • Hi In_Scottish_Exile - Do you have a log file named %windir%\Microsoft.NET\Framework\v2.0.50727\ngen.log on your computer?  If so, could you upload it to a file server such as http://skydrive.live.com, then reply back here and post a link that I can use to download that log and take a further look?

  • Hi Aaron,

    you can find the ngen.log and if interesting the ngen_service.log at




    The .NET Framework Setup Verification Tool didn't reported any issues.

  • Hi Aaron,

    were you able to gather some information and advise from the data provided?

    Thanks in advance

  • Hi In_Scottish_Exile - I'm sorry for the delay looking at your log.  The ngen_service.log shows the same 0x80029C4A (TYPE_E_CANTLOADLIBRARY) error messages, without any better information about exactly what library is failing to load.  If the verification tool is not reporting any errors, then I'm guessing that there is not anything from the .NET Framework itself that is missing but that there is something missing in your OS installation that the .NET Framework depends on.

    It might help to try to run sfc /scannow to repair the files that are a part of Windows to see if that resolves this error.

    If that doesn't help, you may need to try using a tool like Process Monitor (technet.microsoft.com/.../bb896645.aspx) to try to narrow down what the NGen service is trying to access when it hits this error.

  • Hi Aaron,

    thanks for your answer. I only had a quick look on the capabilities of sfc. My laptop is running XP SP3 but I might only have a SP2 or even SP1 CD. Do I need have to create a SP3 installation CD?

    I also deinstalled all .NET versions again and only installed the big 3.5SP1 file from the Microsoft side. When I had a look at the ngen log afterwards there were several successful runs for negen. It only fails on specific ones.

    You can find the new ngen.log under


    The new installation was on 06/04/2011

    Pure guessing: Are these files related to IIS?

    Another background information: 2 years ago I had Visual Express installed for a while. Any possible side effects?

    Thanks in advance

Page 6 of 26 (378 items) «45678»
Leave a Comment
  • Please add 5 and 2 and type the answer here:
  • Post