Windows crumbles under own update system

Windows crumbles under own update system

Once upon a time when you updated Windows you would test an update and leave it for a couple of weeks in case there were any reported problems, and then install to your production environment. This usually went well, and with the advent of virtualisation you always had the snapshot to doubly make sure that if anything went wrong you could roll back and guarantee the system was recovered to the point before you made the change. However it seems with Windows 2008, and particularly R2, rather more subtle issues can arise and while not actually causing you major problems the fix involved is pretty arduous – especially if you don’t notice the problem straight away. The problem I first noticed this when an update was applied to a Windows 2008 R2 server and appeared to go through fine, it certainly reported as being installed successfully and tests of this patch had showed no issues. However I noticed on the console after rebooting the server that the Updating screen never went away to give a CTRL+ALT+DEL screen, even though I could access the server remotely. Logging on via Remote Desktop seemed OK and the server was working, except I then noticed the Roles and Features section on Server Manager was reporting an error and wouldn’t allow me to modify these features. I firstly rebooted the server (as you do) and sure enough the problem with the update screen cleared and a CTRL+ALT+DEL appeared on the server console. However Server Manager was still showing a problem, which meant it was investigation time. Checking the following log (Event Viewer -> Applications...