Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

One of our Windows 2008 R2 SP1 servers hung during a shutdown whilst performing a Windows Update - I elected to "Shutdown and apply updates" - which with hindsight may not have been an optimal choice.

The server hung on the regular grey "Shutting Down Windows" screen, not the one where it tells you it's installing updates and not to pull the plug.

I waited around an hour before deciding to force a reboot. When the server re-started it's now displaying a black screen with the following:

Applying update operation nnnn of 16703 (\Registry\....)

The value of nnnn is incrementing steadily and the value in the brackets has changed variously from system files to registry keys.

Can anyone tell me what might have happened here to trigger this behaviour? I've never seen this before.

I have googled around and found various solutions to errors that may occur during this process, but none of them explain why my server is doing this in the first place.

share|improve this question

1 Answer 1

up vote 2 down vote accepted

This is by design. It's common for the OS to install updates before the reboot, and then after. You will see this screen when you have updates with huge files. The updates are queued up, then installed. We tend to see it more when installing Language Packs, Service Packs, large updates, etc. If your concern you can always check out the server event logs, and the windowsupdate.log. (C:\Windows\windowsupdate.log)

share|improve this answer
    
Ok that puts my mind at rest. Thanks. –  Kev Apr 19 '13 at 0:55

Your Answer

 
discard

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.