Welcome to MSDN Blogs Sign in | Join | Help

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 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>

 

Published Tuesday, October 11, 2005 8:11 PM by astebner

Comments

Sunday, October 23, 2005 12:01 PM by Clive

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

Hi,

The cleanup tool and instructions worked for me, I now have a upgraded MCE system.

Many thanks...
Wednesday, January 04, 2006 4:41 PM by Tink

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

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.

Tink
Wednesday, January 04, 2006 4:57 PM by astebner

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

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.

Tuesday, February 28, 2006 4:52 PM by W. Scott Webb

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

Since install my computer starts with a 8 bit display. How do I correct this? Usually my display is set to 32 bit.
Scott
Tuesday, February 28, 2006 5:01 PM by astebner

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

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.
Wednesday, March 22, 2006 12:08 AM by P. Murphy

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

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 100
Wednesday, March 22, 2006 2:20 AM by astebner

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

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.
Friday, April 21, 2006 7:08 PM by DaveTasker

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

I attempted to remove VS2003 because of an issue that I was having with ImageList failing to load. I belive that this issue due to installing Visual Assist which I believe altered VS2003 manifest and policy files.
I ran the Clean Up tool to remove .NET 1.1
I then installed the 1.1 redist from your link.
When I ran the Setup Verifier I got the following log.
When I attempted to install the 1.1 Service Pack it refused to install
claiming that v2.0.50727\mscorwks.dll could not be loaded.
04/21/06 15:58:23 Starting setup verification for product: .NET Framework v1.1 English
04/21/06 15:58:23 Running filelistgen.exe with command line: "C:\DOCUME~1\djt\LOCALS~1\Temp\IXP000.TMP\filelistgen.exe" /out="C:\DOCUME~1\djt\LOCALS~1\Temp\filelistgen_output.txt" /log="C:\DOCUME~1\djt\LOCALS~1\Temp\filelistgen_log.txt" /map="C:\DOCUME~1\djt\LOCALS~1\Temp\IXP000.TMP\v11_urt_std_enu_x86_ixp.sem"
04/21/06 15:58:24 Running setupverifier.exe with command line: "C:\DOCUME~1\djt\LOCALS~1\Temp\IXP000.TMP\setupverifier.exe" /mode install /filelist C:\DOCUME~1\djt\LOCALS~1\Temp\filelistgen_output.txt /outdir C:\DOCUME~1\djt\LOCALS~1\Temp\ /log C:\DOCUME~1\djt\LOCALS~1\Temp\setupverifier_log.txt /ignoreunv
04/21/06 15:58:28  
04/21/06 15:58:28  
04/21/06 15:58:28 *********** Log info from SetupVerifier.exe ***********
04/21/06 15:58:28  
04/21/06 15:58:28 #################  SUMMARY  ##########################
04/21/06 15:58:28 Number of files with correct attributes = 198
04/21/06 15:58:28 Number of files installed but not supposed = 0
04/21/06 15:58:28 Number of files with incorrect version = 0
04/21/06 15:58:28 Number of files with incorrect language = 0
04/21/06 15:58:28 Number of files missing = 0
04/21/06 15:58:28 Number of file warnings = 1
04/21/06 15:58:28
04/21/06 15:58:28 Total files = 198
04/21/06 15:58:28 ######################################################
04/21/06 15:58:28  
04/21/06 15:58:28 #################  WARNINGS  #########################
04/21/06 15:58:28 CompID File Version Language Shared Permanent CRC Excluded
04/21/06 15:58:28
04/21/06 15:58:28 *** File with greater version (expected/actual) ***
04/21/06 15:58:28 {77b2dbf7-665a-432c-b1b4-add82744de15} C:\Program Files\Internet Explorer\MUI\0409\mscorier.dll 1.1.4322.573 - false false 0x397a7aee false
04/21/06 15:58:28 {77b2dbf7-665a-432c-b1b4-add82744de15} C:\Program Files\Internet Explorer\MUI\0409\mscorier.dll 2.0.50727.42 ENU false false 0x18b18a53 false
04/21/06 15:58:28
04/21/06 15:58:28 ######################################################
04/21/06 15:58:28  
04/21/06 15:58:28 ******** End of log info from SetupVerifier.exe *******
04/21/06 15:58:28  
04/21/06 15:58:28 Verification thread is returning 0
Monday, April 24, 2006 8:41 PM by astebner

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

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_MACHINE\SOFTWARE\Microsoft\.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?
Friday, June 02, 2006 4:13 AM by Cloud

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

I was working with visual studio 2003 correctly until i had install the windows updates. It crashed on framework 1.1 servicepack1. From this moment i can't execute .net app, i get a double 0xc0000005 error. When i tried to reinstall the framework it crashes on system.enterpriseservices.dll.
I tried all the trick in your page like change the os languaje and the debbuger. I don't know what i have dane but now it installs framework 1.1 correctly. But .net apps still make the same error.
I've used the netfx_setupverifer with this log result:

Starting setup verification for product: .NET Framework v1.1 Spanish
Running filelistgen.exe with command line: "C:\DOCUME~1\prades\CONFIG~1\Temp\IXP001.TMP\filelistgen.exe" /out="C:\DOCUME~1\prades\CONFIG~1\Temp\filelistgen_output.txt" /log="C:\DOCUME~1\prades\CONFIG~1\Temp\filelistgen_log.txt" /map="C:\DOCUME~1\prades\CONFIG~1\Temp\IXP001.TMP\v11_urt_std_enu_x86_ixp.sem"
Running setupverifier.exe with command line: "C:\DOCUME~1\prades\CONFIG~1\Temp\IXP001.TMP\setupverifier.exe" /mode install /filelist C:\DOCUME~1\prades\CONFIG~1\Temp\filelistgen_output.txt /outdir C:\DOCUME~1\prades\CONFIG~1\Temp\ /log C:\DOCUME~1\prades\CONFIG~1\Temp\setupverifier_log.txt /ignoreunv

*********** Log info from SetupVerifier.exe ***********
 
#################  SUMMARY  ##########################
Number of files with correct attributes = 235
Number of files installed but not supposed = 0
Number of files with incorrect version = 0
Number of files with incorrect language = 0
Number of files missing = 1
Number of file warnings = 3

Total files = 236
######################################################
 
##################  ERRORS  ##########################
Contents of FileLangProb.txt
CompID File Version Language Shared Permanent CRC Excluded

 
Contents of FileMissing.txt
CompID File Version Language Shared Permanent CRC Excluded

{9294d21e-67d6-4cbe-a083-59e16a166774} C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.EnterpriseServices.Thunk.dll 1.1.4322.573 - true false 0xd9d8d79e false
 
Contents of FileVerProb.txt
CompID File Version Language Shared Permanent CRC Excluded

######################################################
 
#################  WARNINGS  #########################
CompID File Version Language Shared Permanent CRC Excluded

*** File with greater version (expected/actual) ***
{35abb1f7-175c-4012-b182-6722148c0f90} C:\WINDOWS\system32\mscories.dll 1.1.4322.573 - true true 0x1659cc02 false
{35abb1f7-175c-4012-b182-6722148c0f90} C:\WINDOWS\system32\mscories.dll 2.0.50727.42 ENU true true 0xad872b9e false

*** File with greater version (expected/actual) ***
{f3246a0b-ba15-4075-a153-62168d2ba49f} C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\mscormmc.dll 1.1.4322.573 - true true 0x8d85f0a3 false
{f3246a0b-ba15-4075-a153-62168d2ba49f} C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\mscormmc.dll 2.0.50727.42 ENU true true 0x3598b294 false

*** File with greater version (expected/actual) ***
{9294d21e-67d6-4cbe-a083-59e16a166774} C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.EnterpriseServices.dll 1.1.4322.573 - true false 0x4e16057b false
{9294d21e-67d6-4cbe-a083-59e16a166774} C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.EnterpriseServices.dll 2.0.50727.42 ENU true false 0x36851504 false

######################################################
 
******** End of log info from SetupVerifier.exe *******
 
****ERROR**** VerifySetup returned false for parameters v11_urt_std_enu_x86_ixp.sem and E_FILES
Verification thread is returning 100


I'm trying on a xp servicepack2 system.
And i can't reinstall the system
Sorry about my english but i'm spanish
Thank you for your help
Friday, June 02, 2006 4:39 AM by Cloud

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

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??

thanks
Sunday, June 04, 2006 9:23 PM by astebner

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

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.

Thursday, June 29, 2006 7:09 AM by MHA

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

Hi,

i need to use the verifier to silently check out the installation.
guess what - it does not work silently :)
i tried with the following command line:
setupverifier_netfxall.exe /q:a /c:"vsverify /q /p .NET Framework v1.1 /l English"
as defined in the readme but it simply hangs without writing any logfile.
for comparison if i start it without the "q" switch it gives me the gui with the correct framework select and the language grayed out showing "All". when i make a click into the product box the language is instantly changed to "English" and i'm able to do the verification.

know any fixes?

kind regards,
mike
Friday, June 30, 2006 11:10 PM by astebner

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

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"

Monday, July 03, 2006 6:16 AM by MHA

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

Hi Aron,

sorry to say but the only way the tool works in quiet mode is using this:
setupverifier_netfxall.exe /q:a /c:"vsverify /p .NET Framework v2.0 (x86) /q /l All"
everything else leads to a hangup or a simple close without any output.
it seems more like a programming bug when initializing the language. But i'm thinking about using the command line tools anyway.

kind regards,
mike
Monday, July 03, 2006 12:29 PM by astebner

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

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.
Sunday, August 27, 2006 6:44 PM by Aaron Stebner's WebLog : Unified .NET Framework Troubleshooting Guide

# Aaron Stebner's WebLog : Unified .NET Framework Troubleshooting Guide

PingBack from http://blogs.msdn.com/astebner/articles/454956.aspx
Saturday, October 21, 2006 12:16 PM by Aaron Stebner's WebLog

# Unified .NET Framework Troubleshooting Guide

Details about the .NET Framework 2.0 setup packaging Available command line switches for .NET Framework

Thursday, December 21, 2006 4:35 PM by lizziandme

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

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.

Thursday, December 21, 2006 10:37 PM by astebner

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

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.

Friday, January 05, 2007 5:28 PM by Rydal Williams

# Voila! Problem Solved

Voila! Problem Solved

Tuesday, January 09, 2007 2:26 AM by Sarre

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

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

Wednesday, January 10, 2007 9:43 AM by i32123

# Windows Update Failure Fix = Shutdown ZoneAlarm (Temporarily)

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

Saturday, June 23, 2007 11:50 PM by kiriaka

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

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

Friday, September 14, 2007 7:21 AM by dimitri.dhuyvetter

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

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.

Friday, September 14, 2007 11:07 AM by astebner

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

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?

Thursday, September 27, 2007 2:04 PM by bsaucer

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

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

Thursday, September 27, 2007 2:29 PM by astebner

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

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?

Thursday, September 27, 2007 2:55 PM by bsaucer

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

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.

Thursday, October 25, 2007 10:27 PM by Aaron Stebner's WebLog

# Mailbag: Can the .NET Framework verification tool be run in silent mode?

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

Wednesday, October 31, 2007 12:41 AM by vineed_menon

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

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

Vineed

Wednesday, October 31, 2007 10:32 AM by astebner

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

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/.

Sunday, November 04, 2007 6:35 PM by smf111

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

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.

Steve

Tuesday, November 27, 2007 4:24 AM by DigitalStrawberryGirl

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

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 :)

Chris

Tuesday, November 27, 2007 4:37 AM by Digital Strawberry Girl

# Troubles with installing .NET 3.5

Troubles with installing .NET 3.5

Friday, December 07, 2007 7:40 PM by JohnS2000

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

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.

Friday, December 07, 2007 7:59 PM by astebner

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

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.

Friday, December 07, 2007 8:36 PM by JohnS2000

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

Hi again Aaron. Thanks for the quick response. I will try the things above and let you know how it goes.

Thanks again John

Friday, December 28, 2007 5:35 PM by SimCity Societies - Feedback thread - Page 3 - Electronic Arts UK Community

# SimCity Societies - Feedback thread - Page 3 - Electronic Arts UK Community

PingBack from http://forums.electronicarts.co.uk/simcity-series/290787-simcity-societies-feedback-thread-3.html#post4820372

Friday, December 28, 2007 8:37 PM by SimCity Societies - Feedback thread - Page 3 - Electronic Arts UK Community

# SimCity Societies - Feedback thread - Page 3 - Electronic Arts UK Community

PingBack from http://forums.electronicarts.co.uk/simcity-series/290787-simcity-societies-feedback-thread-3.html#post4820812

Friday, March 07, 2008 4:21 AM by osl1511

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

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....

osl

Friday, March 07, 2008 1:01 PM by astebner

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

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.

Friday, March 07, 2008 7:54 PM by Aaron Stebner's WebLog

# Updated: what to do if other .NET Framework setup troubleshooting steps do not help

A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

Friday, March 07, 2008 8:18 PM by Noticias externas

# Updated: what to do if other .NET Framework setup troubleshooting steps do not help

A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

Friday, March 07, 2008 9:40 PM by MSDN Blog Postings » Updated: what to do if other .NET Framework setup troubleshooting steps do not help

# MSDN Blog Postings &raquo; Updated: what to do if other .NET Framework setup troubleshooting steps do not help

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

Friday, March 07, 2008 9:40 PM by MSDN Blog Postings » Updated: what to do if other .NET Framework setup troubleshooting steps do not help

# MSDN Blog Postings &raquo; Updated: what to do if other .NET Framework setup troubleshooting steps do not help

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

Friday, March 07, 2008 9:40 PM by MSDN Blog Postings » Updated: what to do if other .NET Framework setup troubleshooting steps do not help

# MSDN Blog Postings &raquo; Updated: what to do if other .NET Framework setup troubleshooting steps do not help

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

Saturday, March 08, 2008 12:32 AM by MSDN Blog Postings » Updated: what to do if other .NET Framework setup troubleshooting steps do not help

# MSDN Blog Postings &raquo; Updated: what to do if other .NET Framework setup troubleshooting steps do not help

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

Saturday, May 10, 2008 10:48 PM by 2.0 Framework won't install

# 2.0 Framework won't install

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

Anonymous comments are disabled
 
Page view tracker