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>

 

  • PingBack from http://msdnrss.thecoderblogs.com/2008/03/07/updated-what-to-do-if-other-net-framework-setup-troubleshooting-steps-do-not-help-2/

  • PingBack from http://msdnrss.thecoderblogs.com/2008/03/07/updated-what-to-do-if-other-net-framework-setup-troubleshooting-steps-do-not-help-3/

  • PingBack from http://msdnrss.thecoderblogs.com/2008/03/08/updated-what-to-do-if-other-net-framework-setup-troubleshooting-steps-do-not-help-6/

  • PingBack from http://www.the3factory.com/post/2008/05/20-Framework-won't-install.aspx

  • Hi Aaron,

        I never post on these blogs but HAD to sign up just to thank you from the bottom of my heart for your weblog on .NET Framework setup troubleshooting steps.  You totally saved my life.  It must be quite rewarding to help so many struggling souls.  You ROCK!

    Many thanks,

    Joyce

  • Hi Wagner1000 - Thank you for taking the time to sign in and post this comment.  I'm glad to hear that the information on my blog has been helpful to you, but I'm sorry for the hassles that these .NET Framework issues have caused for you in the first place.  Please don't hesitate to contact me if you run into any additional issues in the future.

  • I have remnants of .netframework 2- 3- 3.5- and two versions of .net4framework  client and full. I am having all sorts of problems including 1938 08002802. Alos the windows time ans scheduler are not working..any idea..can I safel delete reg keys for all but version 4

  • Hi Art - I'd suggest using the cleanup tool and the steps listed above in this blog post to remove all versions of the .NET Framework from your system and then re-install the .NET Framework 4 and the .NET Framework 3.5 SP1 to fix these issues.  I would not suggest trying to manually delete registry keys to try to solve this type of problem.

  • Aaron,

    I have used the cleanup tool, and have been able to re-install .net 1.1 and 1.1 SP1.   (Can't re-install 1.0 b/c I'm on XP and it is part of the OS).  When I try to re-install 2.0, it get to a point registering keys that it re-starts the computer every time, and then I get a blue screen error--"the system has recovered from a serious error" when it starts back up.  When I ran the clean-up tool, I got a series of warnings:  

    Attempting to stop the service 'msftpsvc'

    ***WARNING***Failed to open the service 'msftpsvc'

    (repeated for the services 'nntpsvc', 'smtpsvc', 'w3svc' and 'iisadmin'.

    I recently added a registry cleanup tool.  When I use it to search for registry entries containing '.net framework' or any of the above services, the computer also shuts down and gives me the same "serious error" message.  The registry cleanup tool I am using is jv16 powertools.  I have also checked the registry to look for 2.0 entries, and can't see any.  

    Any ideas?

    Thanks,

    Tim

  • i wanted to clarify--it always shuts down while "writing system registry values".  Would it be helpful for you to know what folders ARE in the registry under .net framework?

    Thanks again,

    Tim

  • Hi Tmoss - I haven't heard of a case where the computer spontaneously rebooted during .NET Framework setup like this before.  It is possible that there is something going bad with your hard drive or RAM or something like that.  You may want to try running chkdsk.exe /R to find and fix any bad sectors on your hard drive to see if that helps.

    It is also possible that setup is actually installing or starting a service as opposed to writing registry values when it triggers the reboot and the setup UI just hasn't updated to reflect that.  It might help to look at the setup log files to see if there is more information there about exactly what it is doing at the time of the reboot.  You can use the tool at blogs.msdn.com/.../6458047.aspx to gather your setup log files, and then upload them to a file server such as http://skydrive.live.com and reply here with a link so I can take a quick look to see if I can spot anything.

    Finally, it might help to try to install the .NET Framework 3.5 SP1 (which will install the .NET Framework 2.0 SP2 behind the scenes) or the .NET Framework 4 instead of installing the .NET Framework 2.0 to see if those versions can install without triggering a reboot.

  • I've tried installing 3.5 SP1 and 4 already, and both of those trigger a reboot, also.  I will upload my setup log files and reply with a link as soon as I have the time to figure that out--not a computer pro!  It may be a couple of days.  Thanks for the help, though.

  • Hi Tmoss - Please also try running chkdsk.exe /R if you haven't yet to see if that helps with this type of issue.

  • ok, I have the setup log files saved in skydrive--how do I post a link to them, or should I email them to you?

  • Like this?

    cid-03dd5acf9b77bb7d.office.live.com/.../Tmoss%20VSlog

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