CAPS or caps is all the same to me - glad to have the info and feedback.
I've continued to investigate and it seems clear there's something wrong
with the .NET 1.1 SP1 update. It appears to install, but afterwards the
installation is rejected with the following sequence:
Fatal Execution Engine Error (0x7925e104)
SLA.tmp - Common Language Runtime Debuggins Services
Application has generated an exception that could not be handled.
Process id=0xa74 (2676, Thread id=0xa7c (2684).)
Click OK to terminate the application.
Click CANCEL to debug the application.
If click OK: the update is not installed
If click CANCEL: ... (see below) ... the update isn't installed
SLB.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 0xdc0
Click on Retry to have the process wait while attaching a debugger manually.
The same thing happens when installing .NET 1.1 itself, but in that case the
installation is accepted despite the error message!? A mystery. My hunch is
there's a file(s) version mismatch somewhere in those packages which causes
the after-the-fact errors but I'm not a guru. I've tried uninstalling /
reinstalling, including use of the .NET cleanup tool, but that's the bottom
line. Everything from .NET 1.0 to 3.5 including service packs installs
*EXCEPT* .NET 1.1 SP1. Like ANGEL says, maybe I should be grateful.
But then it's not reliable. Sometimes things install, sometimes they're
rejected. There's obviously something wrong with the basic MS Update service
in general. It looks like they've turned it back over to amateurs to write
the code and administer.
--
G3
"MowGreen" <> wrote in message
news:...
> Apparently one of the updates broke your keyboard because your post is
> ALL IN CAPITAL LETTERS !
>
> MowGreen
> ================
> * -343-* FDNY
> Never Forgotten
> ================
>
> banthecheck.com
> "Security updates should *never* have *non-security content* prechecked
>
>
> ANGELKISSES420 wrote:
>> I WOULDNT WORRY ABOUT THE UPDATE INSTALLING. FEEL LUCKY THAT IT DIDNT
>> INSTALL. EVERYONES PCS THAT DID INSTALL IT. CRASHED AND IT WONT OPEN
>> WINDOWS.
>> SO FEEL LUCKY. YOURE ONE OF THE SAFE ONES.
>>
>> "Gene3" wrote:
>>
>>> Hello,
>>> I'm running Windows XP Home SP3, IE6, Firefox 3.6 (default browser),
>>> ZoneAlarm 6.1, Avast 5.0.
>>>
>>> I have these .NET items already installed:
>>> ..NET 1.0.3705
>>> ..NET 1.0 Hotfix (KB928367)
>>> ..NET 1.1
>>> ..NET 2.0 SP2
>>> ..NET 3.0 SP2
>>> ..NET 3.5 SP1
>>>
>>> KB953297 shows as a High Priority .NET update at MS Update for me, but
>>> installation fails:
>>> Microsoft .NET Framework 1.1 Service Pack 1 Security Update for Windows
>>> 2000, Windows XP, Windows Vista, Windows Server 2008, Windows 7, and
>>> Windows
>>> Server 2008 R2 (KB953297)
>>>
>>> KB940157 an Optional Software update also fails to install:
>>> Windows Search 4.0 for Windows XP (KB940157)
>>>
>>> All other updates installed OK so it's just a problem with these two. I
>>> don't see any reason or error code for the failures, just a message that
>>> they were not installed. Should I try to fix something (is it
>>> important?) or
>>> forget about it?
>>>
>>> Thanks,
>>> --
>>> G3
>>>
>>>
>>> .
>>>