Aaron Stebner's WebLog

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

Problems installing the new ASP.NET hotfix (KB886903 or KB887219)

Problems installing the new ASP.NET hotfix (KB886903 or KB887219)

  • Comments 42

I got a question from a customer this week who could not get an ASP.NET hotfix installed by launching it from Windows Update (due to an error like some folks have seen with other .NET Framework service packs that I described here).  As a result, he was trying to download the package directly, extract it and install manually, but he was having trouble trying to locate the underlying package and download it.  So I decided to try to do this myself to see how the process really works for an IT admin in the field, and I'm surprised by how complicated this process is.  Here are the specific steps I had to follow to locate and download this ASP.NET hotfix:

  1. I retrieved the KB article number from the Windows Update site
  2. I went to the Microsoft support site and found a link here that announces the security bulletin
  3. From there I followed the link for IT professionals since those links typically contain direct links to download packages to stage for installation in corporate networks or other scenarios where Windows Update is not an ideal option
  4. From there I followed the link to the Microsoft download center and used the suggestion to search for the keyword security_patch and filtered based on the .NET product family.  This gave me this results page
  5. From there I could choose what version(s) of the .NET Framework I wanted to patch and download the appropriate hotfix.  For example, this link leads to the hotfix that applies to .NET Framework 1.1 with SP1
  6. Now that I have downloaded the hotfix package, I can go back to the link for IT professionals and drill down to the details of the version of the hotfix I downloaded to figure out what command line switches to use to extract the contents of the package

It really seems like there should be an easier way to locate, download and extract a hotfix package from Microsoft.  If there is a simpler way that I have missed, please post a comment and let me know.

As a side note, this and any other .NET Framework or ASP.NET hotfixes are packaged using the same self-extracting wrapper as the .NET Framework 1.0 SP3 and 1.1 SP1, and therefore are all susceptible to the same set of issues as those service packs.  There is one big issue (that I consider to be a flaw) in the design for the packaging of the .NET Framework service packs and hotfixes.  The self-extracting wrapper EXE is written in managed code, so that means that if the .NET Framework is broken in any way and needs to be repaired, then the patch package will not even extract and launch correctly, and it cannot even give a useful error message.


  • Hi Genans - Can you please try to use the steps listed at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx to clean off and re-install the .NET Framework 1.1 and see if that will resolve this issue? The item you listed is Service Pack 1 for the .NET Framework 1.1 and it would definitely be good to install that if possible.
  • I hope to be alive to see Microsoft going to the drain
    Do people have to suffer and guess what secrecy is beyond their reach in order to fix problems that MS created?
    Do people have to waste countless hours and risk their health just because MS?
    How did we get to this point, were we have to consider ourselves lucky because we can fix some of the countless probles MS created?

    M should be switch to B then we have BS
    I will use every opportunity in my reach to contribute tu put BS down

  • Hi Justme - I would like to try to help you resolve the problems that you have run into.  Can you please provide more details about the exact error you are seeing so I can try to narrow down the cause and determine a workaround/fix?
  • Why doesn't MS just pull this piece of crap until they get a version that doesn't require a rocket scientist?
  • Hi Bob - I'm sorry that you have been encountering problems installing this hotfix.  I cannot tell from your post whether or not you are still having problems.  If so, can you please try the steps listed at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx and see if they help resolve this issue on your system?
  • I am facing an issue with installation of the .net framework patches (KB886903 and KB886906). I get the following error: SLxx.tmp - Common Language Runtime Debugging Services

    I referred your suggestions in the following links and have tried most of the troubleshooting steps informed. Yet, my problem is not solved.

    I had the same issue while I was trying to deploy the same two patches about a year back. I solved this issue at that moment by performing the steps in the following URL:
    If I create the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\DbgJITDebugLaunchSetting with value as 1, the patches got installed at that time.

    But now, even that is not solving this issue. I am getting this error inconsistently on my client machines.

    My workstation is a standard Windows XP Pro SP2 with Office 2003 SP1 configuration.

    I need to deploy these patches along with some other applications to my users ASAP and would greatly appreciate any inputs from you regarding this. Please let me know if you need any more information.

    Thanks in advance.
  • Hi Vijay - I would suggest trying the workaround described at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx and see if that solves this issue.
  • Hi Aaron,

    Firstly, thanks for the great work you're doing here by posting information about problems with security updates.

    I received a question about a problem someone's having installing the security update describe by KB 886903, and was pointed to your post. This got me reading ;-)

    You've listed the steps necessary to find and download update, the posed the question whether this can be done in an easier way.

    Here's how I actually did it :

    1. Get the KB number from Windows Update just like you did - this is KB886903.
    2. In my IE search bar (I'm using IE7 RC1 and live search), I entered "KB886903" (without quotes). Hit search.
    3. The first result is a direct link to the download page and the second link takes me to the bulletin for IT professionals. Both are exactly what I wanted. So I went ahead and downloaded the update from the download page, and then looked up the command line switches in case I want to use any.

    Note: You can simply double-click the package to apply the patch, no need to extract it's contents first unless you have a specific reason for that.

    Now I understand that not everybody uses Live Search and search results may vary from one update to another. Assuming I did not get a quick hit for my KB number in my first search, I would do the following:

    1. Go to http://support.microsoft.com and enter the KB number 886903. Click Search.
    2. The search results will show me to the bulletin page: http://www.microsoft.com/technet/security/bulletin/ms05-004.mspx . I open up this page (the bulletin)
    3. Under Affected Software, I click on the version of .Net I want to patch (in my case this is 1.1). Right there I see listed every patch for this bulletin organized by the different operating systems.
    4. I pick my OS (Windows XP in my case) and that takes me to the download page for the patch for Windows XP.

    Overall I feel there is never any need to go to the download center and start searching for an update. In general no download is ever published without a corresponding KB page and a bulletin in case of security updates. The bulletin will *always* directly take you to the correct download link.

    Program Manager, Developer Division Sustained Engineering Team
  • 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.)



  • i was wanting to know what this means...Process ID= 0x1718 (5912), Thread ID= 0xac4 (2756)....when i get on facebook and i try playing a game or upload vidoes on it it says that the internet stopped working and then that appears...

  • Hi Irma - Troubleshooting crashes in web browsers is not in my areas of expertise.  You may want to try to upgrade to a new version of your browser or try a different browser to see if that helps in this scenario.

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