Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

More detailed troubleshooting ideas for .NET Framework 1.0 SP3 and 1.1 SP1 failures

Rate This
  • Comments 44

I have posted a couple of previous items about .NET Framework 1.0 SP3 and 1.1 SP1 installation issues (at http://blogs.msdn.com/astebner/archive/2004/09/20/232236.aspx and http://blogs.msdn.com/astebner/archive/2004/09/21/232653.aspx).  There is a KB article in the works with more information but it appears to not be posted for viewing yet, so I wanted to include the info that it contains here in the hopes that it might help some folks who are stuck installing one of these .NET Framework service packs.

.NET Framework SP Setup Issues




This document provides a reference to common setup issues and workarounds for .NET Framework 1.1 Service Pack 1 (SP1) and .NET Framework 1.0 Service Pack 3 (SP3).


Windows Update Failures


Windows Update Failed – Detailed Error Code “E0434F4D”


0xE0434F4D (-532459699) is a generic COM exception.  This is caused by a failure in the managed patch wrapper.  There are 3 recommended steps that may fix this problem.  If these do not work, further investigation will be required.


1.                  Repair .NET Framework 1.1 RTM (click Start, click Control Panel, click Add or Remove Programs, click Microsoft .NET Framework 1.1, click “Click here for support information”, click the Readme link).  This page has the 4 steps you will need to run to repair the .NET Framework

2.                  Clear the Windows Update temporary downloads cache.  See http://support.microsoft.com/kb/193385 for more information.

3.                  Clear the temporary directory.  Click Start, click Run, type “%temp%”, click Ok.  An Explorer window will open.  Select all of the files, and hit the delete key.


If these steps do not solve the problem then more information must be gathered.  To see a more detailed error, download the service pack from http://download.microsoft.com/ and then double-click the EXE package.  If the issue occurs again, a crash dialog will be displayed this time.


Windows Update Failed – Detailed Error Code “643”


0x643 = 1603 = ERROR_INSTALL_FAILURE.  This error can be caused by one of the issues listed in the Error Dialogs section below.  The two most likely causes are the netfx.msi resolve source issue or the info 9002 issue.


To see a more detailed error, download the service pack from http://download.microsoft.com/ and then double-click the EXE package.  If the issue occurs again, an error dialog will be displayed this time.


Windows Update Failed – Detailed Error Code “652”


0x652 = 1618 = ERROR_INSTALL_ALREADY_RUNNING.  This error is caused by the item titled Windows Installer Error 1618 – Another installation is already in progress described below.


Crash Dialogs


TargetInvocationException in SLxxx.tmp – missing registry key


TargetInvocationException in SLxxx.tmp can occur for many different reasons.  One of the reasons that this crash occurs is when the Windows Installer registry hive is missing the LocalPackage value for the version of the .NET Framework being serviced. 


Use the registry editor (regedit.exe) to navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData.  Next, search for the string “.NET Framework”


When the search completes, several registry name/value pairs will be listed in the right-hand window pane.  If a DisplayName value of “Microsoft .NET Framework” exists but there is not a LocalPackage value then the TargetInvocationException is being caused by this issue.


Reinstalling .NET Framework 1.0 or 1.1 will fix this problem. 


TargetInvocationException in SLxxx.tmp – missing MSI file


Another variation of the TargetInvocationException error is caused by a missing cached MSI file in the %windir%\Installer directory.  This crash occurs when the Windows Installer registry hive contains a LocalPackage value that points to a nonexistent file.


See the previous topic (TargetInvocationException in SLxxx.tmp – missing registry key) for details on how to find the LocalPackage registry value.  Once the key is found open a command prompt (click Start, click Run, type cmd) and use the dir command to try to locate the target of the LocalPackage value.  For example, if the LocalPackage key was d:\windows\installer\f493a.msi you would type “dir d:\windows\installer\f493a.msi”.  If the dir shows “file not found” then the TargetInvocationException is being caused by this issue.  Reinstalling the .NET Framework 1.0 or 1.1 will fix this issue. 


If the file does exist then the TargetInvocationException is being caused by another issue. 


TargetInvocationException in SLxxx.tmp – virus scanner


A TargetInvocationException can occur if the service pack setup “cancel” button is pressed while a virus scanner is running.


In this scenario, the TargetInvocationException appears right before the success dialog is displayed and does not harm the computer.  This TargetInvocationException can be ignored.


TargetInvocationException in SLxxx.tmp – low system resources


A TargetInvocationException can occur when the system is out of memory.


Rebooting the computer and then re-running the service pack setup can correct this problem.


SLxxx.tmp – Configuration Error


The error "Configuration Error: Unable to load JIT compiler (MSCORJIT.DLL) File may be missing or corrupt.  Please check your setup or rerun setup!" is a known issue with the setup for both the .NET Framework 1.1 SP1 and .NET Framework 1.0 SP3 releases.  The error is harmless and does not damage the machine.  On heavily loaded machines (machines in which it takes at least 5 seconds for setup to launch), before setup has begun installing, a dialog can be displayed that warns about an issue with any one of the following files:


1.                  fusion.dll

2.                  mscorjit.dll

3.                  mscorlib.dll

4.                  mscorsn.dll

5.                  mscorwks.dll

6.                  perfcounter.dll

7.                  corperfmonext.dll

8.                  aspnet_isapi.dll 

The workaround is to reduce the load on the machine by closing applications before re-running setup. 


SLxxx.tmp – Unable to Locate DLL


This dialog is a variation of the SLxxx.tmp – Configuration Error issue described above.


SLxxx.tmp – Common Language Runtime Debugging Services


This crash dialog can be displayed for many reasons. A list of known causes and workarounds follows.


·         Check the My_Computer_Zone has FullTrust permissions enabled


1.       Click Start, Control Panel, and open Administrative Tools.

2.       Select the latest version of the Microsoft .NET Framework Configuration tool.

3.       Drill-down to Runtime Security Policy, Machine, Code Groups, All_Code, My_Computer_Zone.

4.       Right-click on My_Computer_Zone, select the Permission Set tab, and verify/change the permission set to FullTrust.


Installation Hangs


Service Pack installation hangs while running IIS


The service pack installation may hang due to unresponsive IIS services on the machine (specifically WS3SVC and SMTP).  This is because setup attempts to stop some services if they are running on the machine before patching.


If the service pack installation repeatedly hangs then the workaround is to manually stop the WS3SVC and SMTP services before running setup using the following steps:


1.       Run "%SystemRoot%\system32\services.msc /s" to start the Services Manager

2.       Find World Wide Web Publishing Service (WS3SVC) and Simple Mail Transfer Protocol Service (SMTP) in the services list.

3.       Right-click on each service name and select Stop


Alternately, turning off IISADMIN by opening a cmd prompt and running net stop /y iisadmin will also solve this service pack installation hang issue.  Both WS3SVC and SMTP are dependent on IISADMIN, so stopping IISADMIN will also stop WS3SVC and SMTP.


After the installation, rebooting the computer or restarting the services by clicking "Start" instead of "Stop" in the Services Manager will return the computer to its original state.


Error Dialogs


Windows Installer Error 1618 – Another installation is already in progress


Another installation is already in progress. Only one Windows Installer setup can run at a time.  You should complete the other installation before proceeding with this install.


Windows Installer Dialog – cannot find ‘netfx.msi’


Windows Installer may display a dialog asking the user to provide the location of netfx.msi.  This is called a Resolve Source Dialog.  Sometimes patches can prompt for the original installation media (asking the user for the location of netfx.msi).  This can happen when Windows Installer determines that the original product has missing or corrupt files which are not included in the patch package. 


Repairing or reinstalling the original product will fix this issue.  Here are the repair instructions for .NET Framework 1.0 and 1.1:


To repair the .NET Framework

Obtain the original installation source. For example, if you installed the .NET Framework from CD or DVD, insert the disk. Or, if you downloaded the .NET Framework, download again and choose to save to disk. If you installed from a network share, reconnect.

On the Start menu, choose Run.

For Windows 98 and Windows Me type:


For Windows NT, Windows 2000, Windows XP or later, type:


In the command window, type the following:

n:\<Installation Source>\dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"


For example:

d:\dotNetFramework\dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfx.msi"

To repair a .NET Framework Language Pack

Obtain the original installation source. For example, if you installed the .NET Framework Language Pack from CD or DVD, insert the disk. Or, if you downloaded the .NET Framework Language Pack, download again and choose to save to disk. If you installed from a network share, reconnect.

On the Start menu, choose Run.

For Windows 98 and Windows Me type:


For Windows NT, Windows 2000, Windows XP or later, type:


In the command window, type the following:

n:\<Installation Source>\langpack.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\langpack.msi"


For example:

d:\dotNetFramework\langpack.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\langpack.msi"


Info 9002: .NET Framework 1.1 Service Pack 1 (SP1) cannot be installed


The dialog “Info 9002: .NET Framework 1.1 Service Pack 1 (SP1) cannot be installed because you have one or more hot fixes installed.  Remove them and try again” is displayed when a blocking hot fix is already installed on the computer. 


The 2003 October SDK Documentation Update (KB 827821) as well as two other .NET Framework 1.1 SDK patches (KB 841510 and KB 823641) can block the installation of .NET Framework 1.1 SP1.  A workaround for this issue is to remove all of the following registry keys:


·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M827821

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M8278211028

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M8278212052

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M8278211042

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M8278211036

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M8278211031

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M8278211041

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M841510

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1\M823641


Removing the registry keys can be done by using the registry editor:


1.       Click Start -> Run, type “regedit.exe” and click OK

2.       Inside the Registry Editor, navigate the registry structure until you are in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.NETFramework\1.1

3.       Expand the registry key list by clicking the plus ‘+’ sign next to the ‘1.1’ registry hive

4.       Right-click on ‘M827821’ and select ‘Delete’

5.       Continue right-clicking and selecting ‘Delete’ for M827821028, M827822052, M827821042, M827821036, M827821031, M827821041, M841510 and M823641 if they are present


Windows Installer Error 1325 – ‘XXX’ is not a valid short file name


Windows Installer Error 1325 occurs when the service pack is deployed with the command line argument SHORTFILENAMES=1.  A transform file (.MST) is needed to update the short filename in the file table of the .NET Framework netfx.msi to fix this issue if it is necessary to use the SHORTFILENAMES parameter to deploy the service pack.


Windows Installer Error 1642 – The installer cannot install the upgrade patch


 The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates 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.


This dialog means that the wrong patch is being run.  This happens when the wrong version of the patch is accidentally downloaded.  For instance, .NET Framework 1.0 English (ENU) is installed but the .NET Framework 1.0 SP3 German (DEU) patch is being double-clicked.


Verify that the correct patch is being used.  The patch file name ends with the 3-letter language identifier (for instance –enu or –deu).


How to get help


Collect installation log data


Gather the following log files when none of the above items solves your problem and further investigation is required:


1.       %temp%\netfxsl.log

2.       %temp%\netfxupdate.log

3.       %temp%\MSI*.LOG


To get to the %temp% directory click Start, click Run, type “%temp%” and click OK.


The MSI*.LOG file(s) may not be created by default.  If an MSI*.LOG file does not exist please enable Windows Installer verbose logging and then re-run the installation so that an MSI*.LOG file is created.


The following steps can be used to enable Windows Installer verbose logging:


1.       Use the registry editor (regedit.exe) to navigate the registry hive HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer.

2.       Right-click in the right window pane, select New

3.       click DWORD Value

4.       Type “Debug” and hit enter

5.       Right-click the new registry value Debug and select Modify

6.       Set the Value Data field to “7”.

7.       Next, Right-click in the right window pane, select New

8.       click String Value

9.       Type “Logging” and hit enter

10.   Right-click the new registry value Logging and select Modify

11.   Set the Value Data field to “voicewarmup!”.


Note: After gathering MSI*.LOG, it is recommended that you disable verbose logging by deleting the Debug and Logging values under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer in your registry.  If these values are left behind, they will cause Windows Installer to create a verbose log for every MSI-based setup that is run on your computer, which can significantly impact the speed of installation.


<update date="10/9/2008"> Fixed a broken link to the Windows Update download troubleshooting knowledge base article. </update>


  • Every once in a while, I hear from a customer who is trying to install a hotfix or service pack for the

  • I am having automatic updates continue to try to install .NET Framework 1.1 everytime I start my computer. It fails everytime. I've tried several of these fixes and nothing is working. My computer is a Dell Dimension 4600, it's old and I'm thinking some of the WindowsXP files are corrupt or missing. I would like to try re-installing XP, I had to buy a disc from Dell because I can't locate any of the orig discs. Issue is this, if I do this will I lose all of the other programs such as my video-graphics card? I play a game called Sims2 and have had crashes with it, I un-installed the game, when I tried to re-install I'm unable to install the patches and upgrades. With each new Expansion pack comes upgrades to the previous. These will not install, I get an error and the computer removes the installation. So obviously it's not just Windows updates that I can't install.  Something is wrong and I don't know what to do. I've had this game on my computer for years and never had a problem until recently. Both issues began at the same time. I'm thinking they're realted?

    Should I just wipe it out and start over? I don't have any of the original discs for this computer and I don't want to have to buy new graphics-video cards. I want to be able to play my games!!! HELP!!

    You can email me at sheilacgraham@yahoo.com if that works better for you.

    Thanks so much for your time.  

  • Hi Sheila - I'm sorry for the hassles that these issues are causing for you.  For the .NET Framework installation issue, I'd suggest trying the steps listed at blogs.msdn.com/.../9912209.aspx to see if they help.

    If you have a Windows XP installation disc, it is possible to repair your OS without needing to re-install all of your applications.  You can check out the article at www.informationweek.com/.../showArticle.jhtml for more information about how to do this.

    I'm not sure what to suggest for the problem you're encountering while trying to re-install The Sims.  If the repair steps listed above don't end up helping with this, you may need to contact Electronic Arts to see if they can provide any troubleshooting steps for installing this game.

  • Hi, I was using the dotnetfx cleanup

    tool on my computer (windows xp), when I

    was trying to install them back, an

    error came Microsoft .NET Framework

    Setup failed (this is for .NET

    Framework v1.1), thank you!!!

  • Hi Sergio - I'd suggest trying to install the .NET Framework 3.5 SP1 from www.microsoft.com/.../details.aspx and then try again to install the .NET Framework 1.1.

    If the .NET Framework 1.1 still fails after that, then please use the steps listed at blogs.msdn.com/.../help-me-help-you-if-you-have-setup-bugs.aspx to enable verbose logging, reproduce the failure, then upload your log file to http://skydrive.live.com and reply here with a link I can use to download the log file and take a further look.

  • Have error  stating not having net 4.0 or there is a problem with net 4.0. Do you have any thoughts on how to fix this please. Thank you

  • Hi Kenneth Wolfson - What are you doing when you see this error?  If you are trying to run an application, which application is it, and what version of Windows are you running on your computer?

    If you haven't yet, I'd suggest trying to install the .NET Framework 4, or uninstall it and re-install it if it is already installed.  You can find instructions describing how to do this at blogs.msdn.com/.../8108332.aspx.

  • Part 2/2:

    The versions of .NET which are installed on this desktop according to the list in the Windows\Microsoft .NET\Framework subdirectory are 1.0.3705 (mscorlib.dll version 1.0.3705.0), 1.1.4322 (1.1.4322.2502), 2.0.50727 (2.0.50727.3643), 3.0 (no mscorlib.dll), 3.5 (no mscorlib.dll, but has successfully been updated with SP1 and various security updates), 4.0.30319 (4.0.30319.296), and VJSharp (no mscorlib.dll).  This machine had a problem installing a different .NET patch several months ago, and in the process of getting that resolved I used the cleanup tool to remove all the versions and rebuilt them from the ground up.  When this SP3 patch wouldn't go, I went through that process a 2nd time, but KB867461 simply won't install no matter what -- I've allowed all the various FixIt tools that have been offered in following the "Windows Update won't install" options to run, and while they always seem to find something to repair the outcome produces no success.

    I use MSE as my primary AV and Windows Firewall for that purpose, and run weekly manual scans with several other malware detection agents (Malwarebytes, Super AntiSpyware, Kaspersky TDSS rootkiller, Panda Cloud AV), plus use CCleaner on a monthly basis to remove temporary files, cookies and such.  Nothing more than cookies have been found since long before this problem arose.  I've tried shutting down the MSE functions and services before attempting the installation of this patch with no difference in success.  I've used online scans from other AV vendors (ESET, AVG F-Protect) to verify there's really nothing in the way of malware lurking to block this installation.

    I'm reasonably competent with computers from being a civil engineer who's personally dealt with them from 1970s mainframes onward through the era of PCs as both a user and a self-taught IT administrator for hardware repairs and OS reccovery when needed, but this particular problem has me stumped at this point and I've expended far too much time and effort in attempting to resolve it.  I intend to replace this machine in another month or so and aren't inclined to do a repair installation or a wipe-and-rebuild at this point, so if there are no viable approaches which might be suggested in response to this post I'll just live with the foible and ignore that patch while I accelerate the replacement process a bit.

  • Hi Jim Vance - I'm sorry for the hassles that this issue is causing for you.  The first part of your comment didn't post correctly, so I'm not sure what version of Windows you are running.  The steps that I normally suggest for this type of .NET Framework installation problem are listed at blogs.msdn.com/.../8108332.aspx.  If you haven't yet, I'd suggest trying those steps to see if they help resolve these issues.

    If you're still seeing .NET Framework installation issues after trying those steps, can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your setup log files, upload the file named %temp%\vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com), and then reply back here and provide a link that I can use to download your log files and take a closer look?

  • Aaron, many thanks for the reply despite the failure of part 1 of the message to post.  I discovered that fact late yesterday afternoon and attempted to summarize it with an additional post, but the system came back with a message that there was some problem and the administrators have been notified; since that message didn't post either, I just quit for the evening.

    Hopefully, this one will go through so I'll try to summarize briefly again.  The machine in question is running XP Pro SP3, and the problem lies with installation of the .NET Framework 1.0 SP3 (KB867461) patch which fails with this message: "This install cannot continue because this version of the .NET Framework is incompatible with a previously installed one.  For more information, see..." a MS KB article URL reference (Q312500) which no longer exists.  The URL reference leads to some troubleshooting options, and I've allowed the various Fixit tools which are offered to run, but while they claim to have repaired certain things (Windows Installer and .NET), it hasn't produced any difference in terms of an outcome.  Although my primary browser is Firefox, for all of that online troubleshooting I was using IE (v8.0.6001.18702).

    I've downloaded and run offline the latest Windows Installer just to make sure nothing was somehow getting blocked.  I have tried running offline the .NET repair tool, and have used the cleanup tool twice to remove all .NET versions, then went laboriously through the process of running Windows Update repeatedly, rebooting between in order to reinstall all the .NET versions offered -- the 2nd time I used separately downloaded versions of the installation patches rather than running through the Windows Update shell, but all were completely unsuccessful in the end and that .NET 1.0 SP3 patch simply will not install.  So, posting something on this blog was really the last shot because I plan to replace that desktop with a Win7 machine in another month, then recycle the old machine's hardware components after wiping everything on the hard drives following a complete backup and transfer with PC Mover to the new machine.  Ultimately, I decided if I can't get this patch to go through, I'll just ignore it for the remainder of its functional life.

    I have not run the verification tool which your other post referenced, though it appears I have done everything else -- I'll download the verification tool and run that tomorrow morning, then collect the setup log files and upload them to the server and provide a follow-up post here where they can be found.

  • Hi, Aaron -- If I've done everything properly, you should be able to access 2 files: 1) the vslogs.cab file and 2) the setupverifier text file at the following link:


    Please let me know if I somehow screwed up with either of those, and once again many thanks for your time and efforts to help me resolve this particular gremlin.

  • Hi Jim Vance - You've got the .NET Framework 4 installed on your computer.  The .NET Framework 4 installs a registry key that prevents the .NET Framework 1.0 from being installed or repaired.  When you try to install the .NET Framework 1.0 SP3, it triggers a repair of the .NET Framework 1.0 as part of the service pack installation process, and that in turn sees the registry key created by .NET Framework 4 setup and blocks the install.

    In order to resolve this issue, you'll need to uninstall the .NET Framework 4 (both the Client Profile and Extended), install the .NET Framework 1.0 SP3, then re-install the .NET Framework 4.

    Please let me know if that doesn't end up resolving this issue.

  • Hi, Aaron -- I tried to post something last night but again got a system error message and it doesn't appear this morning, so I'll reprise it this morning.  I've uninstalled both the .NET Framework 4 Client and Extended without any issues, rebooted and then attempted to install the .NET Framework 1.0 SP3 patch without success.  I tried it two different ways -- first the direct route using the downloaded installation file, but as before (which was described in that earlier Part 1/2 posting that evaporated) this generates an intermediate notice that it cannot find 'netfx.msi' in a temporary folder at the default subdirectory C:\Documents and Settings\Administrator\Local Settings\Temp.  The specific message is: "The feature you are trying to use is on a network resource that is unavailable."  When I manually try and navigate to the default location in Windows Explorer, that temporary folder doesn't exist  If I bypass the default location in the notice and attempt to manually browse to a different location where I have previously extracted this netfx.msi file (per the instructions in another of your blog postings), the message changes to "Accessing the feature" for awhile and then changes back to the one about the network resource being unavailable.  Nothing seems to work, so canceling out reverts the installation progress bar and that box disappears.

    If I run Windows Update instead and deselect anything other than the .NET Framework 1.0 SP3 patch (the .NET Framework 4 Client is listed as an optional item, and perhaps an MSE definitions update), allowing it to proceed onward fails with the same 0x643 error code as has typically been the case since this issue first arose months ago.

    Any other ideas?

  • Hi Jim Vance - The "feature you are trying to use is on a network resource that is unavailable" error message means that there is something wrong with the base version of the .NET Framework 1.0 that is on your computer and it needs to be repaired before you can install 1.0 SP3.  The easiest way to do that is to use the steps and the cleanup tool described at blogs.msdn.com/.../8108332.aspx to fully remove all versions of the .NET Framework, then re-install them.

Page 3 of 3 (44 items) 123
Leave a Comment
  • Please add 2 and 2 and type the answer here:
  • Post