Updates today seem to have killed my Server 2003 :-( Any ideas?

My remote Windows 2003 web editon server "died" suddently today. Having
managed to extract the event log from it via a recovery console, I can see
(surprise surprise!) that the very last entry before its death was this:

=============================================
Restart Required: To complete the installation of the following updates, the
computer will be restarted within 5 minutes:
- Cumulative Security Update for ActiveX Killbits for Windows Server 2003
(KB950760)
- Cumulative Security Update for Internet Explorer 6 for Windows Server 2003
(KB950759)
- Security Update for Windows Server 2003 (KB951698)
- Security Update for Windows Server 2003 (KB950762)
- Windows Malicious Software Removal Tool - June 2008 (KB890830)
- Security Update for Windows Server 2003 (KB948745)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
==========================================

As it is a remote server, I cannot see the BSOD which is presumably
occuring, but as the disk is accesible via a recovery console, we are clearly
dealing with an update induced bug rather than a hardware issue. Is there
any way (from a recovery console!) to roll back these problem updates and get
back to a bootable system?

--
Dave Harvey
Medical Connections

Dave:
Sounds like the same problem I had with my Windows XP. I think you'll find
that there wasn't a BSOD at all, but just that Windows won't start.

This smells like a faulty Windows Update. I'm surprised we're not hearing
more about it in the forums.

Some of the stuff I've read today suggests that hardware could play a role
in why this happens. One article went so far as to suggest that simply
changing the keyboard could make a difference (skeptical).

I'd be grateful if you would share any progress you make on this.
Naturally, I'm happy to do the same.

TIA,

Dave


"Dave Harvey" wrote:

> My remote Windows 2003 web editon server "died" suddently today. Having
> managed to extract the event log from it via a recovery console, I can see
> (surprise surprise!) that the very last entry before its death was this:
>
> =============================================
> Restart Required: To complete the installation of the following updates, the
> computer will be restarted within 5 minutes:
> - Cumulative Security Update for ActiveX Killbits for Windows Server 2003
> (KB950760)
> - Cumulative Security Update for Internet Explorer 6 for Windows Server 2003
> (KB950759)
> - Security Update for Windows Server 2003 (KB951698)
> - Security Update for Windows Server 2003 (KB950762)
> - Windows Malicious Software Removal Tool - June 2008 (KB890830)
> - Security Update for Windows Server 2003 (KB948745)
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ==========================================
>
> As it is a remote server, I cannot see the BSOD which is presumably
> occuring, but as the disk is accesible via a recovery console, we are clearly
> dealing with an update induced bug rather than a hardware issue. Is there
> any way (from a recovery console!) to roll back these problem updates and get
> back to a bootable system?
>
> --
> Dave Harvey
> Medical Connections

Dave,

Thanks for the info - I had seen your post, but of course XP is not EXACTLY
the same as server 2003!

In my case I don't have the luxury of changing a keyboard - it is a blade
server sitting in Germany (I'm in the UK)....can you give me a pointer to the
other postings/info you've seen on this?

At the moment I'm simply rescuing files - but I will certainly let you know
if I find anything useful.
--
Dave Harvey
Medical Connections


"dw9357" wrote:

> Dave:
> Sounds like the same problem I had with my Windows XP. I think you'll find
> that there wasn't a BSOD at all, but just that Windows won't start.
>
> This smells like a faulty Windows Update. I'm surprised we're not hearing
> more about it in the forums.
>
> Some of the stuff I've read today suggests that hardware could play a role
> in why this happens. One article went so far as to suggest that simply
> changing the keyboard could make a difference (skeptical).
>
> I'd be grateful if you would share any progress you make on this.
> Naturally, I'm happy to do the same.
>
> TIA,
>
> Dave
>
>
> "Dave Harvey" wrote:
>
> > My remote Windows 2003 web editon server "died" suddently today. Having
> > managed to extract the event log from it via a recovery console, I can see
> > (surprise surprise!) that the very last entry before its death was this:
> >
> > =============================================
> > Restart Required: To complete the installation of the following updates, the
> > computer will be restarted within 5 minutes:
> > - Cumulative Security Update for ActiveX Killbits for Windows Server 2003
> > (KB950760)
> > - Cumulative Security Update for Internet Explorer 6 for Windows Server 2003
> > (KB950759)
> > - Security Update for Windows Server 2003 (KB951698)
> > - Security Update for Windows Server 2003 (KB950762)
> > - Windows Malicious Software Removal Tool - June 2008 (KB890830)
> > - Security Update for Windows Server 2003 (KB948745)
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > ==========================================
> >
> > As it is a remote server, I cannot see the BSOD which is presumably
> > occuring, but as the disk is accesible via a recovery console, we are clearly
> > dealing with an update induced bug rather than a hardware issue. Is there
> > any way (from a recovery console!) to roll back these problem updates and get
> > back to a bootable system?
> >
> > --
> > Dave Harvey
> > Medical Connections

I've applied these patches to several 2k3 systems with no issues.

BSOD's are driver related not usually patch related.

ballzie wrote:
> Dave,
> I ran into the same problem when these updates went out. Actually
> didn't realize my system was blue screening because it would turn off
> so quick after POST and the CPU fan wasn't turning so I assumed
> overheating, however after replacing the fan and still seeing the same
> problem I turned off the auto reboot on failure and noticed the BSOD.
> The BSOD I had was BAD_POOL_HEADER which, after reading through some
> forums, seems like it can be related to alot of different things
> however one of the entries mentioned USB problems so I removed the usb
> mouse and pulled a stick of memory and the problem was resolved. Not
> sure which fixed the BSOD but I'm guessing it was removing the USB
> mouse. I'm hesitant to T/S the system to figure out which removed
> piece of HW fixed it since it is now running again, but when I do I'll
> update this post. As far as what you can do remotely, I haven't a
> clue. Not sure if you can get into the BIOS remotely, you may be able
> to turn off some devices (like USB) in the BIOS and see if it will
> allow you to boot.
>
> --Brian
>
>