Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
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:
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>
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
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:\windows\system32, and missing registry values under HKLM\Software\Microsoft\.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/.
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.
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 :)
Troubles with installing .NET 3.5
Hi Aaron, first I want to thank you for taking the time to gather all this information and creating the tools then putting them all in one place. Great Job!
Now to the problem I am having. I am working on my grand daughter’s computer because it just quit displaying anything on the screen. I did a non destructive restore so she wouldn’t lose her school work. After the restore I had to download and install 82 critical updates from Microsoft. Everything went well except for .NET. It seams that .NET V1.0 is in a state that I can’t update it and I can’t install any other version. I’ve tried everything and I can’t get your cleanup tool to remove .NET V1.0. The fallowing is in the Cleanup_Main.log file after installing the tool but prior to running it.
[12/07/07,18:50:07] Beginning of new cleanup utility session
[12/07/07,18:50:07] Not adding product '.NET Framework - All Versions' because the OS condition does not match
[12/07/07,18:50:07] Not adding product '.NET Framework - All Versions (Windows Server 2003)' because the OS condition does not match
[12/07/07,18:50:07] Not adding product '.NET Framework - All Versions (Windows Vista and Windows Server 2008)' because the OS condition does not match
[12/07/07,18:50:07] Not adding product '.NET Framework 1.0' because the OS condition does not match
I am hoping you can give me idea as what to do to get your tool to remove .NET V1.0.
When I run your cleanup tool the fallowing is the first line after the above text:
[12/07/07,18:50:07] Starting cleanup for product .NET Framework - All Versions (Tablet PC and Media Center)
This is correct, I am working with a HP laptop Media Center PC about a year old.
Hi JohnS2000 - The .NET Framework 1.0 is installed as an OS component on Windows XP Media Center Edition. The cleanup tool does not allow you to remove versions of the .NET Framework that are OS components. You can try to use the steps at http://blogs.msdn.com/astebner/archive/2005/09/01/459631.aspx to attempt to repair the version of the .NET Framework 1.0 that is installed as a part of the OS on this system. If those steps do not work, then you may have to try to repair/re-install your OS.
Alternatively, it might work to try to install a newer version of the .NET Framework like 1.1 or 2.0. It sounds like you may have already tried that and failed as well. If so, you can send me the log files from the .NET Framework installs that are failing and I can try to take a look. .NET Framework 2.0 log files are created automatically and are named %temp%\dd_netfx*. For .NET Framework 1.1 logs, you need to use steps like the ones at http://blogs.msdn.com/astebner/archive/2005/03/29/help-me-help-you-if-you-have-setup-bugs.aspx.
You can send the logs to Aaron.Stebner (at) microsoft (dot) com.
Hi again Aaron. Thanks for the quick response. I will try the things above and let you know how it goes.
Thanks again John
PingBack from http://forums.electronicarts.co.uk/simcity-series/290787-simcity-societies-feedback-thread-3.html#post4820372
PingBack from http://forums.electronicarts.co.uk/simcity-series/290787-simcity-societies-feedback-thread-3.html#post4820812
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.
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.
A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation
PingBack from http://msdnrss.thecoderblogs.com/2008/03/07/updated-what-to-do-if-other-net-framework-setup-troubleshooting-steps-do-not-help/