Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

What to do if other .NET Framework setup troubleshooting steps do not help

What to do if other .NET Framework setup troubleshooting steps do not help

  • Comments 73

March 7, 2008 update - I have written a replacement version of these instructions.  Please refer to http://blogs.msdn.com/astebner/archive/2008/03/07/8108332.aspx instead of using the steps listed below.

I have heard from many customers who have run into various types of installation problems while trying to install the .NET Framework 1.0 or 1.1 or .NET Framework hotfixes and service packs.  Some of my other blogs posts have described various workarounds, and I am working on an article that consolidates these workarounds.  However, there are some problems that aren't able to be resolved with the other workarounds I have posted.

Nearly every time when I run into a scenario where my other posts do not help, I try to use the following steps to get the machine back into a known state and then install things back one by one:

  1. Download the .NET Framework cleanup tool and choose to cleanup the version of the .NET Framework that is causing problems on your system
  2. Download and install the version of the .NET Framework that you cleaned up in step 1 (such as the .NET Framework 1.0, .NET Framework 1.1 or .NET Framework 2.0)
  3. (optional) Download and run the .NET Framework verification tool to double-check that all .NET Framework files are correctly installed
  4. Download and install the desired .NET Framework service pack (such as .NET Framework 1.0 SP3 or .NET Framework 1.1 SP1) by running the setup package directly instead of using Windows Update.  Running it directly will allow the service pack setup to display error dialogs instead of having Windows Update suppress them

Running these steps should ideally put your machine back into a known good state with the .NET Framework plus a service pack installed.  From there, it will usually work to install applications that require the .NET Framework (such as Visual Studio) or to install additional .NET Framework hotfixes (such as the security updates listed here).

<update date="3/7/2008"> I have written a replacement version of these instructions.  Please refer to http://blogs.msdn.com/astebner/archive/2008/03/07/8108332.aspx instead of using the steps listed above. </update>

 

  • Hi MHA - The verification tool will only accept a specific set of products and languages.  You can check what version and language combinations are allowed to be verified by launching the program in full UI mode and looking at what options are available in the UI dropdown listboxes.  In addition, the verification tool will very quickly report failure if the product you are trying to verify isn't actually installed on your system.

    You can check the results of the cleanup tool by looking at the logs it produces.  They are named *vsverify* and are located in the %temp% directory on your system.  I have tested the silent mode scenarios thoroughly, but it is possible there is still a bug somewhere in the command line parsing.  If you can send me the log files, I can take a look and see if there are any bugs in the cleanup tool UI itself.  You can send them to Aaron.Stebner (at) microsoft (dot) com.
  • PingBack from http://blogs.msdn.com/astebner/articles/454956.aspx
  • Details about the .NET Framework 2.0 setup packaging Available command line switches for .NET Framework

  • Hello! I'm at my wit's end - just bought a program Sony Movie Studio 6.0b and after it  installs it will not launch.  Their support told me to install version 6.0d but when I try to install it, a window pops up saying I have to install .NET Framework 1.1 with 2 links.  When I try to install those 2 files I get these errors:

    Microsoft .NET Framework Setup -

    Microsoft .NET Framework Setup cannot write to the setup log

    NDP1.1sp1-KB867460-X86exe -

    The upgrade patch cannot be installed by Windows Installer Service because the program to be upgraded may be missing or the upgrade patch may update a different version of the  program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.

    I have Windows XP Home edition and .NET Framework 1.0 came with it.  Apparently version 1.1 is different.

    My error message when I try to launch the Sony program is a 16 bit windows subsystem error that no one seems to figure out how to fix. So I'm trying to install 1.1 but get those errors listed above.

    Any suggestions?  Other than take the Sony program back?

    Thank you for your time.

  • Hi Lizziandme - I suggest trying the steps listed in this blog post to try to fully remove and then re-install the .NET Framework 1.1 and see if that helps.  If you still cannot install the .NET Framework 1.1, please use the steps listed at http://blogs.msdn.com/astebner/archive/2005/03/29/403575.aspx to gather, zip and send me verbose log files for the failed installation?  You can mail the logs to Aaron.Stebner (at) microsoft (dot) com.

  • Voila! Problem Solved

  • Hi Aaron,

    First of all, many thanks for all your effort to help us poor amateurs. I spent a couple of days, trying to find help concerning my rather vague "Microsoft .NET Framework Setup failed. If this problem continues, contact Product Support Services." and came to your blog. Still nothing helped.

    But finally, http://support.microsoft.com/kb/824643/en-us?spid=1249&sid=global did it!

    I don't know whether it was the reregistering of Windows Installer or the Temp folder cleaning, but the .NET Framework 1.1 Setup went just perfect after that.

    I thought I ought to mention it to those that (just like me) for some reason sometimes think that the official Microsoft web pages don’t tell the whole truth...

    Kind regards,

    Sarre

  • A recent Windows Update failure (Error number 0x80190193)

    encountered when applying patch kb886903 to .NET 1.1 SP1

    was completely resolved and eliminated by temporarily

    shutting down an old version of the ZoneAlarm firewall.

    (A dozen other, more complicated fixes had no effect.)

    YMMV

    HTH

  • I came across this blog desperate for help installing .Net Framework 3.0 and did three things - the third made it work. disabled the DTC (distributed transaction coordinator)

    Start....Run....type: services.msc....R. click on DTC - properties/disabled

    Then edited boot.ini from notepad from "Optin" to

    "AlwaysOff"

    Third: Disabled the network adapters (even the ethenet, which was not enabled anyhow.

    The one that made the install go finally was disabling the network adapters.

    Tip: leave the Device Manager window up, when you get to the install wizard you'll need a connection or the setup will timeout and you'll be back at square one.

    kiriaka

    Toshiba M55

    1.99GB RAM

    2 external HD 80/160

  • I also got the error:

    ****ERROR**** VerifySetup returned false for parameters v20_urt_std_x86_ixp.sem and E_FILES

    Verification thread is returning 100

    I already did a repair, .NET 2.0 is installed for sure, but still I get this error.

  • Hi Dimitri.dhuyvetter - The cleanup tool creates a more detailed log file that should tell you the exact list of file(s) that it thinks are missing or an incorrect version.  Can you please look for that more detailed log in %temp% on your system and paste the contents of that here or send it to me via email at Aaron.Stebner (at) microsoft (dot) com so I can take a further look?

  • Do you have a verify tool for 2.0 compact, 3.0 and 3.5?

  • Hi Bsaucer - No, there is not a tool to verify the .NET Compact Framework.  We have not heard of very many setup issues, so this type of tool hasn't been needed so far.  Are you seeing some kind of installation problem for the .NET Compact Framework in your scenarios?

  • I just like to check ALL of my .Net Framework versions to make sure theey're all right. Anyway, I use VS 2003, 2005, and am installing 2008 Beta 2, I need to verify the installations of 3.0 and 3.5, and whatever other ones VS 2008 uses.

    Of course, I'll be needing to install VS 2008 final release when it comes out, so I'll have to clean up the Beta 2 when I do.

  • Question: I would like to try to automate the instructions for removing and reinstalling the .NET Framework

Page 2 of 5 (73 items) 12345
Leave a Comment
  • Please add 8 and 3 and type the answer here:
  • Post