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 Tmoss - Yes, that link worked correctly and I'm able to look at your log files.  All of your attempts to install the .NET Framework 2.0 are cut off during creation of registry keys, and at different places in each attempt.  There isn't anything in the normal process of creating Windows registry keys that would cause a computer to spontaneously reboot like that.  The .NET Framework 4 client profile installed successfully, but the .NET Framework 4 full appears to have rebooted during installation of files.  There isn't anything in the normal process of copying a file that would cause a computer to spontaneously reboot either.

    I still suspect that this could be a hardware problem on your computer.  Have you had a chance to try running chkdsk.exe /R yet to see if it is able to find and fix any errors?

  • Yes, that is actually one of the first things I did.  I suspect that it has to do with the fact that I had to do a system restore over the summer--I ran TurboTax 2009 last year with no problems, so I had to have had .net framework 3.5 at that time, right?  Is there any way to find out if there are any leftover files hanging the install up even after I run the cleanup tool?  If it is indeed a hardware problem, how is that best handled?

  • Hi Tmoss - I don't know of a way that doing a system restore would cause this type of reboot problem.  I also have never seen a case where leftover files caused reboots during the middle of an installation like you're seeing.  Yes, you would have had to have had the .NET Framework 3.5 to be able to install and use TurboTax 2009.

    I'm not sure how best to narrow this down to be honest.  It might help to try to update your system BIOS and see if there are any updated drivers for the hardware components on your computer.  It might also help to try to unseat and reseat the RAM on your computer and/or swap out RAM if you have other sticks available to try out.

    If none of the above help, then I think your best bet may be to contact Microsoft technical support for more in-depth troubleshooting assistance.  You can find contact information at http://support.microsoft.com.

    I'm very sorry that I haven't been able to be more helpful in this scenario.

  • I just purchased a new laptop yesterday.  Everything was working fine until I installed my wireless printer.  My computer started asking for .net framework 2.0.  I downloaded 4.0 b/c I figured it would support 2.0 requirements.  My computer is still asking for 2.0 and now I can't open anything on the computer.  I want to uninstall the printer and see if that works but I can't open any programs or files.  The computer will turn on though.

  • Hi Aimee Morrison - Unfortunately, .NET Framework applications that require the .NET Framework 2.0 will not automatically use the .NET Framework 4, so installing the .NET Framework 4 won't help for this type of error.

    What version of Windows are you running on your computer?  If it is Windows XP, you can re-download and re-run .NET Framework 3.5 SP1 setup and it will put back the .NET Framework 2.0 for you.  If it is Windows Vista or Windows 7 though, the .NET Framework 2.0 is installed as a part of the OS and it cannot be installed separately.  You can try to use steps like the ones listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx to repair the files that are a part of the .NET Framework.

    Also, can you try to run the .NET Framework setup verification tool and see if it reports any errors for the .NET Framework 2.0?  You can find the verification tool at blogs.msdn.com/.../8999004.aspx.

  • Hi,

    I uninstalled and reinstalled .net 3.5 between these states I was watching these keys:

    "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager" , "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" and "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce".

    I see no difference, do I need to look somewhere else too? Does these locations varry according to the versions? Actually, I am looking for what is the side effect if I install 2 or more versions of .net in a row suppressing the restart? Is there something or somewhere I can see to know this?

    The thing I want to know is that, say if I uninstall/install .net 3.5 suppressing the restart and it writes bunch of variables and registry keys, then I uninstall/install .net 4 and it over writes the previous variables and registry keys. This I think will have side effects isn't it so? I just want to find out what happens so that I don't mess up .net. In that scenario.

  • Hi Shoeson333 - The only thing that will cause .NET Framework setup to request a reboot is if files are in use that need to be updated during setup.  If there are files in use, you will see setup return exit code 3010, and in some cases, you will see entries added to the PendingFileRenameOperations registry value.  If you are installing several versions of the .NET Framework in a row, you shouldn't see any side effects of suppressing reboots until the end of installation.

    However, you could see problems if you try to suppress reboots during an uninstall + re-install combination.  The danger there is that there could be a file in use during the uninstall that is marked for deletion after the next reboot, but you suppress the reboot and re-install the .NET Framework.  It could re-install the file marked for deletion, but the marking to delete it after the next reboot will remain.  Then, that file will be deleted the next time you reboot your computer.

    Because of this type of issue, I don't recommend suppressing reboots that are requested during a product uninstall if you are going to proceed with re-installing that product or a related product immediately afterwards.

  • I am installing .net framework 2.0 and it occurred the error      "error 25007.error occupied while initializing fusion.setup could not load fusion with loadlibraryshim().Error : 0x80131700 "

    plz give me solution of this problem as soon as possible..........

  • Hi Vibhanshu - For this 0x80131700 error, I'd suggest using the cleanup tool and the steps described at blogs.msdn.com/.../8108332.aspx to fully remove all versions of the .NET Framework from your computer, then try again to re-install the .NET Framework 3.5 SP1 (which will also install the .NET Framework 2.0 SP2 and 3.0 SP2 for you behind the scenes).

  • plz help me i still got the error and somehow i cant download the link of the cleaner :(

  • Hi Alan - Have you tried both of the download links for the cleaup tool that are listed at blogs.msdn.com/.../8904493.aspx  If you still can't download from either of them, please send me a comment using the link at blogs.msdn.com/.../contact.aspx and I can email you a copy instead.

  • plz help me... i cant play virtua tennis 4 in pc...

    error like this " virtua tennis 4 has encountered a pblm and needs to close .we are sory for the convienince ... "

    plzzzzzzz hlp me :(((((((

  • Hi Shamil - This sounds like a problem with this game as opposed to a problem with the .NET Framework.  I'd suggest looking on the website for the manufacturer of this game to see if they have any troubleshooting steps that you can try and/or if they have a support alias that you can contact to get help resolving this error.

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