![]() ![]() If you are unlucky, there are two ways to make Windows try to roll back the updates: If you are lucky the updates will finish installing in safe mode, and all you have to do is reboot. It was Windows that got us into this mess in the first place, so surely now is the time to point the finger of blame at the software side? If that does not help, blame the software A quick memory test would also be good, as memory failures are one of the most prevalent physical causes of such problems. If you are experiencing this issue on a physical server, check any relevant ILO/IDRAC/IMM/BMC logs, and visit the server to check for warning lights. Hardware errors can cause all kinds of issues during the update process. Sometimes that will cancel the stuck update, allowing the boot sequence to continue. Another trick is to send a Ctrl+Alt+Del to the server. Thus, it is worth letting it roll overnight just in case it is really slow. ![]() More so if the server is an underpowered VM. Some updates may take a very long time to complete. If you do not understand how to perform the procedures listed below, you should not attempt them on your own. Warning: this post contains last-ditch attempts and other dangerous stuff that could destroy your server. ![]() That makes it a bit harder to troubleshoot though. I do experience this issue from time to time, but thankfully it is pretty rare. I will try to give a somewhat chronological approach to get your server running again. You can wait for several days, but nothing happens, the process is stuck at X%: ProblemĪfter installing updates through Microsoft Update, the reboot never completes. Update 2017.01.24: Several people have reported that adding a blank pending.xml file helps, so I have added it to the list. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |