Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

One of our Windows Server 2008 boxes is stuck in a reboot cycle. It was rebooted after installing updates that Microsoft released on Tuesday.

When I boot into Safe Mode it says "Configuring Updates Stage 3 of 3" and then reboots. In Normal mode it says "Waiting for Windows Module Installer..." then it starts a reboot cycle.

How can I tell Windows to either not install the update that is not working, or somehow convince the server to start?

Last Known Good Configuration from the boot menu did not help.

Selecting the "Disable Automatic Restart after STOP Error" is now showing me a STOP 0x000000F4 error when doing a normal start-up, Safe Mode does not generate a BSOD.

WindowsUpdate.Log -

Thank you.

share|improve this question
Have you tried booting from the installation CD/DVD and then performing a chkdsk against the system volume? – user48838 Jun 16 '11 at 14:24
Yes I have run a chkdsk it found a few errors and repaired them, problem still the same. – SnAzBaZ Jun 16 '11 at 16:36
up vote 2 down vote accepted

You can convince the server to start by renaming C:\windows\winsxs\pending.xml to C:\windows\winsxs\pending.bak.

This will get your server to boot, but it will also leave it in an unsupported state. If you do this, you should backup your system and rebuild.

If you don't want to do that, maybe you could give us some more details like which updates you installed or maybe a copy of some log files.

share|improve this answer - Here is the WindowsUpdate.log which shows the updates that were installed and maybe something else? – SnAzBaZ Jun 16 '11 at 16:33

C:\err.exe 0x000000F4

#for hex 0xf4 / decimal 244 :
CRITICAL_OBJECT_TERMINATION                                   bugcodes.h
# A process or thread crucial to system operation has
# unexpectedly exited or been terminated.

If System Startup Repair is already installed, reboot, F8, Advanced boot options, and select it from the menu. If it's not there...

Put a CD in (or mount if it's a VM), reboot, boot from CD. Try System Startup Repair.

Give that a go and come back to us.

Do you have a recent backup?

share|improve this answer
As far as I can tell Startup Repair is not available on Windows Server 2008 so I cannot try that option. We do have a backup, and I can reload the server if necessary, I would just like to try and find a manual fix before going down that road. – SnAzBaZ Jun 16 '11 at 17:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.