Can't Install KB886903: Security Update for .NET Framework, Ver 1.1 SP1

I can't install the following critical update on Windows XP:

Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1

I've tried applying it several times, including after rebooting the machine
and doing a disk cleanup. The error messages I see are the following:

Run #1:
Message Box Header: SLBE.tmp - Common Language Runtime Debugging Services
Message Box Body:
Application has generated an exception that could not be handled.
Process id=0x400 (1024), Thread id=0x39c (924)
Click OK to terminate the application.
Click CANCEL to debug the application.
[OK] [Cancel]

Run #2:
Message Box Header: SL8F.tmp - Common Language Runtime Debugging Services
Message Box Body:
Application has generated an exception that could not be handled.
Process id=0x830 (2096), Thread id=0xfb8 (4024)
Click OK to terminate the application.
Click CANCEL to debug the application.
[OK] [Cancel]

After clicking OK I see the following:

Message Box Header: Installing Updates
Message Box Body:
Updates were unable to be successfully installed:
Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1
The following updates wer not installed:
[Close]

I scanned this newsgroup for other mentions of this problem but am
unfamiliar with the tool referenced (some kind of Windows Update
Cleanup???). Could someone please advise... Don't like to see a critical
update not go on.

Can you try downloading and installing it from
http://www.microsoft.com/downloads/i...86903-X86.exe?

--
Ben B. [US]

"Ian" <anonymous@internet> wrote in message
news:%...
>I can't install the following critical update on Windows XP:
>
> Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1
>
> I've tried applying it several times, including after rebooting the
> machine and doing a disk cleanup. The error messages I see are the
> following:
>
> Run #1:
> Message Box Header: SLBE.tmp - Common Language Runtime Debugging Services
> Message Box Body:
> Application has generated an exception that could not be handled.
> Process id=0x400 (1024), Thread id=0x39c (924)
> Click OK to terminate the application.
> Click CANCEL to debug the application.
> [OK] [Cancel]
>
> Run #2:
> Message Box Header: SL8F.tmp - Common Language Runtime Debugging Services
> Message Box Body:
> Application has generated an exception that could not be handled.
> Process id=0x830 (2096), Thread id=0xfb8 (4024)
> Click OK to terminate the application.
> Click CANCEL to debug the application.
> [OK] [Cancel]
>
> After clicking OK I see the following:
>
> Message Box Header: Installing Updates
> Message Box Body:
> Updates were unable to be successfully installed:
> Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1
> The following updates wer not installed:
> [Close]
>
> I scanned this newsgroup for other mentions of this problem but am
> unfamiliar with the tool referenced (some kind of Windows Update
> Cleanup???). Could someone please advise... Don't like to see a critical
> update not go on.
>

I'm one o' those folks who've had NO success fixing this (MVP claimed there
are only *six* of us in the world with this problem!), so I gave your
suggestion a try. Result is a popup that says:

"SL7E.tmp - Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Process id=0x8a4 (2212), Thread id=0x43c (1084).

Click OK to terminate the application.
Click CANCEL to debug the application."

If I click CANCEL, I get:

"SL7E.tmp -No debugger found.
Registered JIT debugger is not available. An attempt to launch a JIT
debugger with the following command resulted in an error code of 0x2 (2).
Please check computer settings.

cordbg.exe !a 0x8a4

Click on Retry to have the process wait while attaching a debugger manually.
Click on Cancel to abort the JIT debug request."

This seems like a particularly frustrating bug, and I've religiously
followed EVERY suggestion I've seen in this group, but to no avail. I'm
willing to be patient....some more.

Next suggestion?


Yours truly,
Uncle Beer

http://www.dotnet247.com/247referenc...49/249097.aspx



uncle beer wrote:
> I'm one o' those folks who've had NO success fixing this (MVP claimed
> there are only *six* of us in the world with this problem!), so I
> gave your suggestion a try. Result is a popup that says:
>
> "SL7E.tmp - Common Language Runtime Debugging Services
> Application has generated an exception that could not be handled.
> Process id=0x8a4 (2212), Thread id=0x43c (1084).
>
> Click OK to terminate the application.
> Click CANCEL to debug the application."
>
> If I click CANCEL, I get:
>
> "SL7E.tmp -No debugger found.
> Registered JIT debugger is not available. An attempt to launch a JIT
> debugger with the following command resulted in an error code of 0x2
> (2). Please check computer settings.
>
> cordbg.exe !a 0x8a4
>
> Click on Retry to have the process wait while attaching a debugger
> manually. Click on Cancel to abort the JIT debug request."
>
> This seems like a particularly frustrating bug, and I've religiously
> followed EVERY suggestion I've seen in this group, but to no avail.
> I'm willing to be patient....some more.
>
> Next suggestion?
>
>
> Yours truly,
> Uncle Beer

Taurarian replied with this link:
http://www.dotnet247.com/247referenc...49/249097.aspx

....that contained this registry entry:
HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramewor k\DbgJITDebugLaunchSetting
which unfortunately doesn't exist on my machine, although .Net 1.1 *is*
installed.

Also, Taurarian's link contains another link:
http://msdn.microsoft.com/library/de...us/cpguide/htm
which only says "Page Cannot be Found".

Keep 'em coming; all SIX of us with this bug would like to join the rest of
you whose Updater actually works. :^ \


Yours truly,
Uncle Beer

http://support.microsoft.com/default...b;en-us;824643
How to troubleshoot Microsoft .NET Framework 1.1 installation issues


uncle beer wrote:
> Taurarian replied with this link:
> http://www.dotnet247.com/247referenc...49/249097.aspx
>
> ...that contained this registry entry:
> HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramewor k\DbgJITDebugLaunchSetting
> which unfortunately doesn't exist on my machine, although .Net 1.1
> *is* installed.
>
> Also, Taurarian's link contains another link:
> http://msdn.microsoft.com/library/de...us/cpguide/htm
> which only says "Page Cannot be Found".
>
> Keep 'em coming; all SIX of us with this bug would like to join the
> rest of you whose Updater actually works. :^ \
>
>
> Yours truly,
> Uncle Beer

Taurarian wrote:

>http://support.microsoft.com/default...b;en-us;824643

After carefully following all steps on the indicated page (oy: I've done
this several times before, too-- just was hoping someone had a new angle), I
get this:

"SLAF.tmp -Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Process id=0xb0 (176), Thread id=0x1c8 (456).

Click OK to terminate the application.
Click CANCEL to debug the application."

If I click CANCEL, I get the very same "No debugger found" message.

Folks, I'm not a newbie to computers; I followed these instructions to the
letter. No joy.

Any more suggestions?


Yours truly,
Uncle Beer

I'm out of ideas, but perhaps the last post from Mark P may or may not be of
assistance to you

http://www.microsoft.com/windowsxp/e...7-046fd08b93f5

Link may wrap to more than one line.




"uncle beer" <> wrote in message
news:d3e0s8$2ik$...
> Taurarian wrote:
>
>>http://support.microsoft.com/default...b;en-us;824643
>
> After carefully following all steps on the indicated page (oy: I've done this
> several times before, too-- just was hoping someone had a new angle), I get this:
>
> "SLAF.tmp -Common Language Runtime Debugging Services
> Application has generated an exception that could not be handled.
> Process id=0xb0 (176), Thread id=0x1c8 (456).
>
> Click OK to terminate the application.
> Click CANCEL to debug the application."
>
> If I click CANCEL, I get the very same "No debugger found" message.
>
> Folks, I'm not a newbie to computers; I followed these instructions to the letter.
> No joy.
>
> Any more suggestions?
>
>
> Yours truly,
> Uncle Beer
>
>

Hellllooooo:

I noticed the helpful suggestions have come to a halt. I've literally tried
EVERYTHING suggested to fix this, more than once. To the letter.

Any chance of MVP's passing a message on to Redmond (or wherever the MS
folks chill): that some of us are having ongoing problems with the .NET
security update? That would be greatly appreciated.


Yours truly,
Uncle Beer

Taurarian wrote:

>http://www.microsoft.com/windowsxp/expertzone/newsgroups/reader.mspx?>&query=security+update+for+microsoft& lang=en&cr=US&guid=&sloc=en->us&dg=microsoft.public.windowsupdate&p=1&tid=3e24 d981-d176-4542-b462-618f69a368b4#b7d5e8b3-a3e7->4097-a7c7-046fd08b93f5

I did this (as I have before, more than once...): Windows Install Clean-Up
shows *NO* programs to clean up, so this is a no-go.

Any more suggestions? Anyone? . . . . .


Yours truly,
Uncle Beer