What to do if other .NET Framework setup troubleshooting steps do not help
March 7, 2008 update - I have written a replacement version of these instructions. Please refer to https://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:
- Download the .NET Framework cleanup tool and choose to cleanup the version of the .NET Framework that is causing problems on your system
- 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)
- (optional) Download and run the .NET Framework verification tool to double-check that all .NET Framework files are correctly installed
- 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 https://blogs.msdn.com/astebner/archive/2008/03/07/8108332.aspx instead of using the steps listed above. </update>
Comments
Anonymous
October 23, 2005
Hi,
The cleanup tool and instructions worked for me, I now have a upgraded MCE system.
Many thanks...Anonymous
January 04, 2006
Hello Aaron,
Your cleanup tool worked for me, but I'm very curious. Why didn't the "security update" from MS install (KB886903)? This happened on 2 machines that I was "clean installing." Both systems had some identical custom settings prior to doing the MS updates, I'm wondering if this has anything to do with it? i.e. temp dirs and pagefile are setup for the D drive, with XP installed on C (multi-partitions, several primaries.)
So...the question is, if both XPs were "vanilla" installs with no custom settings, would this "security update" have worked?
What concerns me is that I'll be living with this XP for quite a while and probably have to do a number of clean installs along the way. I will then have to do more updates and I don't want to get into this fix again if I can avoid it. I can't avoid it if I am clueless about what caused it. If it is my setup, perhaps I can do my custom settings after the fact.
Thanks in advance.
TinkAnonymous
January 04, 2006
Hi Tink - I'm not sure why the security update was failing for you on these systems. There are a lot of possible causes. I haven't heard of any cases where updating the location of the temp directories or the pagefiles would cause this. If you run into this error again, you can use the steps listed in the How To Get Help section of the blog post at http://blogs.msdn.com/astebner/archive/2004/11/23/268934.aspx to gather verbose log files and hopefully we can try to figure out why it is failing based on that.Anonymous
February 28, 2006
Since install my computer starts with a 8 bit display. How do I correct this? Usually my display is set to 32 bit.
ScottAnonymous
February 28, 2006
Hi W. Scott Webb - The .NET Framework setup does not touch anything to do with display settings. You should be able to change this back by right-clicking on your desktop, choosing Properties, then choose the Settings tab and change the Color Quality drop-down.Anonymous
March 21, 2006
I received the following error after working through your fix's. Any suggestions?
03/21/06 23:04:50 ERROR VerifySetup returned false for parameters v20_urt_std_x86_ixp.sem and E_FILES
03/21/06 23:04:50 Verification thread is returning 100Anonymous
March 21, 2006
Hi P. Murphy - This error you are seeing typically means that the version of the .NET Framework you are trying to verify is not installed on your system. Are you sure you have the .NET Framework 2.0 installed on this system? Or did you mean to verify one of the other versions of the .NET Framework? If needed, you can choose a different product to verify on your system, depending on what is appropriate for your scenario.Anonymous
April 21, 2006
The comment has been removedAnonymous
April 24, 2006
Hi Dave Tasker - Does your system have the .NET Framework 2.0 installed? It appears that it does not, but that some part of the .NET Framework thinks that you do. Can you take a look at the registry sub-key located at HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFramework and see if there are any 2.0 or v2.0 values listed in there and if so, let me know what they are?Anonymous
June 01, 2006
The comment has been removedAnonymous
June 01, 2006
I copy a few dll and now the setupverifer tell me "product verification succeeded".
But i still can't ejecute .net apps. And the framework 1.1 servicepack1 gives me the same error. A double 0xc0000005.
What can i do on it to work??
thanksAnonymous
June 04, 2006
Hi Cloud - I am not sure what else to suggest because it sounds like you have already tried the steps in this blog post to remove and reinstall the .NET Framework 1.1. I think your best option at this point would be to contact the Microsoft technical support team for further troubleshooting. You are entitled to a free support case for setup-related .NET Framework issues. I'm sorry I'm not able to be more helpful here.Anonymous
June 28, 2006
The comment has been removedAnonymous
June 30, 2006
Hi MHA - You need to make sure that the product name and language match exactly what is displayed in the UI. In this case, you should be able to run the following:
setupverifier_netfxall.exe /q:a /c:"vsverify /q /p .NET Framework v1.1 /l All"Anonymous
July 02, 2006
The comment has been removedAnonymous
July 03, 2006
The comment has been removedAnonymous
August 27, 2006
PingBack from http://blogs.msdn.com/astebner/articles/454956.aspxAnonymous
October 21, 2006
The comment has been removedAnonymous
December 21, 2006
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.Anonymous
December 21, 2006
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.Anonymous
January 05, 2007
Voila! Problem SolvedAnonymous
January 08, 2007
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, SarreAnonymous
January 10, 2007
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 HTHAnonymous
June 23, 2007
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/160Anonymous
September 13, 2007
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.Anonymous
September 14, 2007
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?Anonymous
September 27, 2007
Do you have a verify tool for 2.0 compact, 3.0 and 3.5?Anonymous
September 27, 2007
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?Anonymous
September 27, 2007
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.Anonymous
October 25, 2007
Question: I would like to try to automate the instructions for removing and reinstalling the .NET FrameworkAnonymous
October 30, 2007
I am created a VB.Net 2005 Windows application and deployed on a machine. The application worked perfectly some days. However now whenever the application is started it gives the error "Unable to find a runtime version to Run this application". Then the .Net Framework 2.0 and the application is reinstalled then it works properly. But when the machine is rebooted the problem starts again. I have tried all the things you have said in the above article but could not find a solution. Any ideas why is this problem occuring. Thanks & Regards VineedAnonymous
October 31, 2007
Hi Vineed_menon - I haven't heard of a problem like this before, but it looks like there are a few reports of similar issues on the MSDN forums. If you have already repaired the .NET Framework and it works once, then it is possible that something in your application is changing the state of the .NET Framework on your system. You may need to use a tool like Process Monitor (http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/processmonitor.mspx) to narrow down exactly what files and registry values are being looked at during the startup sequence for your application to figure out what is missing/broken. The most common causes of .NET Framework startup errors that I've seen are an incorrect version of mscoree.dll in c:windowssystem32, and missing registry values under HKLMSoftwareMicrosoft.NETFramework. I listed a partial set of keys that need to be present in your registry for the .NET Framework to be able to initialize correctly at http://blogs.msdn.com/astebner/archive/2007/06/12/3260076.aspx. It might help to check there and verify that those keys are all present on your system. I'd also suggest posting a bug on the Visual Studio and .NET Framework bug reporting site about this issue so that the feature teams can investigate it in more detail. You can report bugs at http://connect.microsoft.com/visualstudio/.Anonymous
November 04, 2007
After about 3 hours of manually attempting to repair, uninstall, and reinstall net 1.1, I finally used your cleanup tool to wipe everything out. This was the only solution that worked. I had framework setup failed errors, unable to find source errors, and one error led to another. Thanks for the tool. SteveAnonymous
November 26, 2007
Aaron, you are a complete star for posting this - I've been stuck with a broken installation of .NET 3.5 for the last week and I tried everything I could possibly think of to fix it - this tool finally did the job! Many thanks indeed :) ChrisAnonymous
November 26, 2007
Troubles with installing .NET 3.5Anonymous
December 07, 2007
The comment has been removedAnonymous
December 07, 2007
The comment has been removedAnonymous
December 07, 2007
Hi again Aaron. Thanks for the quick response. I will try the things above and let you know how it goes. Thanks again JohnAnonymous
December 28, 2007
The comment has been removedAnonymous
December 28, 2007
The comment has been removedAnonymous
March 06, 2008
Hi Aaron, I'm using Vista, IIS7 and VS2003. I failed to open new project. I've registered framework 1.1 successfully. The error message is "...web server is running ASP.NET 1.0...However, the application will not be able to use the new features from ASP.NET 1.1" I've tried a couple of times the steps you mentioned but still failed. Please help.... oslAnonymous
March 07, 2008
Hi osl1511 - I don't have much experience troubleshooting this type of ASP.NET error. I typically use aspnet_regiis.exe to try to configure the chosen version of ASP.NET when I get this type of error. If that doesn't help in your scenario, I'd suggest trying to post a question on the ASP.NET forums at http://forums.asp.net/ and hopefully someone there will be able to suggest other workarounds for you. I'm sorry I'm not able to be more helpful in this scenario.Anonymous
March 07, 2008
A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installationAnonymous
March 07, 2008
A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installationAnonymous
March 07, 2008
PingBack from http://msdnrss.thecoderblogs.com/2008/03/07/updated-what-to-do-if-other-net-framework-setup-troubleshooting-steps-do-not-help/Anonymous
March 07, 2008
PingBack from http://msdnrss.thecoderblogs.com/2008/03/07/updated-what-to-do-if-other-net-framework-setup-troubleshooting-steps-do-not-help-2/Anonymous
March 07, 2008
PingBack from http://msdnrss.thecoderblogs.com/2008/03/07/updated-what-to-do-if-other-net-framework-setup-troubleshooting-steps-do-not-help-3/Anonymous
March 07, 2008
PingBack from http://msdnrss.thecoderblogs.com/2008/03/08/updated-what-to-do-if-other-net-framework-setup-troubleshooting-steps-do-not-help-6/Anonymous
May 10, 2008
PingBack from http://www.the3factory.com/post/2008/05/20-Framework-won't-install.aspxAnonymous
November 20, 2009
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, JoyceAnonymous
November 21, 2009
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.Anonymous
August 26, 2010
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 4Anonymous
August 27, 2010
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.Anonymous
November 14, 2010
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' WARNINGFailed 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, TimAnonymous
November 14, 2010
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, TimAnonymous
November 15, 2010
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.Anonymous
November 15, 2010
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.Anonymous
November 15, 2010
Hi Tmoss - Please also try running chkdsk.exe /R if you haven't yet to see if that helps with this type of issue.Anonymous
November 16, 2010
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?Anonymous
November 16, 2010
Like this? cid-03dd5acf9b77bb7d.office.live.com/.../Tmoss%20VSlogAnonymous
November 18, 2010
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?Anonymous
November 18, 2010
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?Anonymous
November 19, 2010
The comment has been removedAnonymous
January 30, 2011
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.Anonymous
January 31, 2011
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.Anonymous
February 21, 2011
Hi, I uninstalled and reinstalled .net 3.5 between these states I was watching these keys: "HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession Manager" , "HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRun" and "HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRunOnce". 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.Anonymous
February 21, 2011
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.Anonymous
March 21, 2011
The comment has been removedAnonymous
March 22, 2011
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).Anonymous
June 10, 2011
The comment has been removedAnonymous
June 11, 2011
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.Anonymous
August 08, 2011
The comment has been removedAnonymous
August 08, 2011
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.