Re: KB925902 update causes STOP:c000021A fatal error at boot
Ottmar Freudenberger
> 2) There's some other incompatibility on my machine which is causing the
> BSOD when the KB925902 update is applied.
Most likely. Do you have overclocked your machine? Or "tuned" otherwise?
Bye,
Freudi
J Barker
I've just called Product Support Services.
They tell me that the KB925902 update is incompatible with my XP Home SP2
and they recommend that I hide the update to prevent its installation.
I can't see the sense in this. KB925902 was issued to fix a security
vulnerability which I would then still have, so this doesn't fix the problem.
Ottmar Freudenberger
> No overclocking or tuning applied.
Hm, which appications/services are running in the background and
were running while applying the update?
Do you have looked for updated system drivers (BIOS, chipset etc.)
for your system?
Bye,
Freudi
Ottmar Freudenberger
> I've just called Product Support Services.
>
> They tell me that the KB925902 update is incompatible with my XP Home SP2
> and they recommend that I hide the update to prevent its installation.
>
> I can't see the sense in this.
Me neither. What informations did "they" asked you for to come to that
IMHO braindead conclusion?
> KB925902 was issued to fix a security
> vulnerability which I would then still have, so this doesn't fix the problem.
ACK
Bye,
Freudi
T_Oli
"J Barker" wrote:
> My PC automatically downloaded update KB925902 yesterday. With the update
> installed, the PC would boot into a BSOD with "STOP:c000021A {Fatal System
> Error} The Session Manager Initialization System terminated unexpectedly with
> a status of 0xc000026c (0x00000000 0x00000000) The system has been shut down.
>
> None of the start up options would get the machine booted. It's running XP
> Home SP2 with all prior updates installed.
>
> In the end, I got the Recovery Console up and running and removed the
> KB925902 update by running 'batch spuninst.txt' This removed the BSOD problem
> and allowed the machine to boot OK.
>
> So, the machine's now running but I'm without the KB925902 update and have
> disabled Automatic Updates to prevent it installing for the time being.
>
> Two possibilities seem to exist:
>
> 1) There's a problem with the KB925902 update which needs to be fixed.
>
> 2) There's some other incompatibility on my machine which is causing the
> BSOD when the KB925902 update is applied.
>
> Any thoughts please? I gather elsewhere that the STOP message above is
> indicative of a security or permissions problem with system processes
> towards the end of the boot.
>
> JB
T_Oli
on a users pc, performed this fix and machine is now working with out any
issues.
PA Bear
w/out problem on 2 WinXP Home machines here.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org
J Barker
"T_Oli" wrote:
> The fix stated here works perfectly. I was receiving this same exact error
> on a users pc, performed this fix and machine is now working with out any
> issues.
I'm glad I'm not the only one with this problem, then.
I've now installed the hotfix for the Realtek HD Audio that MS issued and
then re-installed KB925902. The system then crashes as before, so I've had to
go and remove it again through Recovery Console. I can't find a way of
telling Microsoft Update to stop installing it, so Automatic Updates will
have to remain off for now.
After the disappointing telephone support I got (see above), I'm going to
try and raise a support call by e-mail. Anyone else had this problem or got
any ideas?
Thanks
JB
Daniel@discussions.microsoft.com G. Daniel
>> In the end, I got the Recovery Console up and running and removed the
> KB925902 update by running 'batch spuninst.txt' This removed the BSOD problem
> and allowed the machine to boot OK.
Hi there, me and some guys using XP Home have the same problem with the
halting system after the Hotfix.
So can you tell me where I can find the 'batch spuninst.txt' and if it gives
me any info on how to remove the hofix again? - I have to say here I never
uninstalled a hotfix by using the console, so I dunno how to do it. thanks,
Daniel
J Barker
>
> So can you tell me where I can find the 'batch spuninst.txt' and if it gives
> me any info on how to remove the hofix again? - I have to say here I never
> uninstalled a hotfix by using the console, so I dunno how to do it. thanks,
> Daniel
You need to boot your PC from a Windows XP install CD (*not* a PC recovery
disk some vendors provide with them). When you start XP from the CD, one of
the options is to launch the Recovery Console.
After answering a few questions, you should end up with a C:\WINDOWS prompt,
or something similar.
At this prompt, type
cd $NtUninstallKB925902$\spuninst
Then type
batch spuninst.txt
All being well, a handful of files will be replaced with the original
versions (before the update was installed) and when you reboot your machine,
it shouldn't blue screen.
When the machine reboots, you should disable Automatic Updates temporarily.
Then go to Control Panel and remove the KB925902 patch from Add/Remove
Programs (make sure Show Updates is ticked at the top of this page).
You then need to go to the Microsoft web site and download the KB925902
patch without installing it.
Then, boot your PC into Safe Mode by pressing F8 when the boot process starts.
When it's booted into Safe Mode, run the KB925902 patch you downloaded
earlier and reboot again normally.
All being well, this should install the patch without trashing your machine.
JB
T. Knuppe
Thank you very very much for this workaround. My Notebook crashed with this
fatal error Wednesday in the evening.
It took me 7 hours of my life to find out what happened and fixing it.
Thank you Microsoft for nothing!!! No patch can help on this problem for
normal customers because they can't even boot their systems!
FYI: My System is a BenQ 5100E with a Windows XP Pro (upgraded from the
original BenQ XP Home recovery set) OS.
--
Thomas
NetAdmin@discussions.microsoft.com LA NetAdmin
"J Barker" wrote (paraphrased):
Boot PC from Windows XP install CD.
Launch the Recovery Console.
In Recovery Console:
cd $NtUninstallKB925902$\spuninst
batch spuninst.txt
Disable Automatic Updates temporarily.
(Note: You can also do this in the Recovery Console: disable wuauserv)
Reboot normally.
Go to Control Panel \ Add/Remove Programs and remove the KB925902 patch.
(make sure Show Updates is checked at the top of this page)
Manually download KB925902 from Microsoft web site without installing.
Boot your PC into Safe Mode.
Run the KB925902 patch you manually downloaded
Reboot again normally.
-----------------------------------------------------------
Great call JB, had exact same symptoms on Dell Optiplex OEM pre-install with
Windows XP Pro SP2.
FYI: All booting options, including all variations of Safe-Mode and Last
Known Good failed miserably. Since my machine had Automatically Restart on
System Failure enabled, all I would see is the initial Windows XP graphic
with the scrolling bar at the bottom, then bang, reboot.
When I enabled Safe-Mode from the F8 screen, I would see the AGP440.SYS
driver load last in the character-based mode and then as XP changed into GUI
mode...reboot.
I had none of the driver conflicts MS has identified, so far, to blame.
Just the likelihood that one or more of the replaced files, gdi32.dll,
mf3216.dll, user32.dll, or win32k.sys, was locked in a way that the patch
installer could not overcome.
MS Support was even less helpful for me, offering only upgrade in-place,
with possible/probable loss of data stored in All Users and possibly
Administrator profiles too. Instead, I have a fully recovered system, with
no loss at all.
Thanks for posting your solution.
marcus5285
with both windows 2000 pro and windows xp pro sp2. thankfully, i found this
solution. I uninstalled both patches kb925902 and kb890859 from my machine,
and then it booted. i have yet to try and reinstall it in safe mode, but at
least i have a solution for now.
when i first uninstalled kb925902, my machine would still not boot, so i
then uninstalled kb 890859 which i also found in this site.
thank you very much.
"J Barker" wrote:
> My PC automatically downloaded update KB925902 yesterday. With the update
> installed, the PC would boot into a BSOD with "STOP:c000021A {Fatal System
> Error} The Session Manager Initialization System terminated unexpectedly with
> a status of 0xc000026c (0x00000000 0x00000000) The system has been shut down.
>
> None of the start up options would get the machine booted. It's running XP
> Home SP2 with all prior updates installed.
>
> In the end, I got the Recovery Console up and running and removed the
> KB925902 update by running 'batch spuninst.txt' This removed the BSOD problem
> and allowed the machine to boot OK.
>
madbob
BSOD with error message 0xc000026c (0x00000000 0x00000000)
damn microsoft
...
Re5cue911
to approx 50%, then I got an "unstable system" message recommending uninstall
from Add/Remove Programs, followed by a "failed to install SP2" message.
After rebooting the machine, I got a BSOD with the C000021A {Fatal System
Error} and 0xc000026c 0x00000000 error codes. It's not my computer
(thankfully), but I was wondering if anyone had this issue with the SP2
update or has it just been with Security Updates? Any reason for SP2 to have
this type of error? Will the fix for J Barker's problem work with mine?
I forget the machine specs other than it's custom built (not by me) with an
ASUS P5P800 motherboard and 1gig of RAM
Thanks in advance
Larry
madbob
> I had this same error, i thought i had a bad piece of hardware. it happened
> with both windows 2000 pro and windows xp pro sp2. thankfully, i found this
> solution. I uninstalled both patches kb925902 and kb890859 from my machine,
> and then it booted. i have yet to try and reinstall it in safe mode, but at
> least i have a solution for now.
> when i first uninstalled kb925902, my machine would still not boot, so i
> then uninstalled kb 890859 which i also found in this site.
> thank you very much.
>
JBaker's way almost worked but something missing, windows could not
autenticate.
I reformat and reinstall the damn Windows XP again (too much investment).
Then one by one istalled the updates and tested.
Until installing KB 890859 it was still okay.
Now only KB 925902 was excluded from the system.
__
ljwolfe
the drive." I have the recovery disk in the CD drive. What should I do?
ljwolfe
drive." I have the Recovery CD in the drive. What should I do?
madbob
(Notes: Ghost backup needed Net framwork)
Then I installed kb925902, and it booted up and worked okay.
No BSOD.
I don't know after sometimes of usage, I'll let you know.
ubetcherazz
Once again, thanks for nothing Microsoft !!! what a bunch of morons.
Microsoft help and support is totally useless...they want money just to get
support for a product I ALREADY PAID FOR.
OK, now that i have had my rant...
my XP Pro SP2 machine worked fine last night, no updates were performed
recently. this evening i booted it up and got:
STOP: c000021a (fatal system error) The session manager initialization
process terminated unexpectedly with a status of oxcoooo26c
the system has been shut down
---if i could id punch bill gates in the mouth. Any suggestions???
McCoy@discussions.microsoft.com P. McCoy
old Windows NT (2000) system at work crash out with the same symptoms after
doing a Windows Update last weekend (looks like the first one that was done
since last December).
Can anyone advise on a fix specific to NT, or is it the same as the
procedure listed below?
Many thanks in advance...
PBM
acguarnica
raphaelnikolai
This article can give you another alternative in resolving this issue:
'STOP:c000021A fatal error'
(http://www.out-of-warranty.com/stopc000021a-fatal-error-windows-will-not-boot-or-start)
--
raphaelnikolai
------------------------------------------------------------------------
raphaelnikolai's Profile: http://forums.techarena.in/members/69664.htm
View this thread: http://forums.techarena.in/windows-update/726552.htm
iamneo
I noticed your searching and posting about this issue on the web... and
finally came across your solution..
Many thanks, as this stupid update took down my windows 2003 server... Not
wanting to lose a whole week of clients data, I was so glad to see this
solution..
I thank you... for saving my server...
I only wish Microsoft would own up to issues like this one. How an update
can take down systems is beyond me.
Interesting is that this kb925902 update only killed one of my 2003 servers.
Of course it had to kill the one that had the most important info...
Thanks again....
Neo... June 22, 2010
![Harry Johnston [MVP]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjWpkBAPqvc839nzAtvH7xG03OwcxExyoyKpBgg3G7rKJeLEHQ=s40-c)
Harry Johnston [MVP]
Why are you only now installing a security update from 2007?
The corresponding KB article mentions an issue with some printer drivers which
can cause a system crash, but nothing about failures to boot. If they were
common, it is likely that the problem would be documented.
In more general terms, when an update causes a system to fail the most common
causes are an already existing malware infection or faulty device drivers or
other third-party kernel-mode components (such as antivirus software).
Unfortunately there are too many possible combinations of hardware and software
out there for Microsoft to test updates on all of them.
(Once in a while the update really is at fault, of course, in which case
Microsoft usually withdraw the update until it can be corrected.)
Harry.
--
Harry Johnston
http://harryjohnston.wordpress.com