{"id":12074,"date":"2019-11-27T01:10:22","date_gmt":"2019-11-27T00:10:22","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=12074"},"modified":"2019-11-28T19:59:17","modified_gmt":"2019-11-28T18:59:17","slug":"windows-server-2012-goes-into-update-loop","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/11\/27\/windows-server-2012-goes-into-update-loop\/","title":{"rendered":"Windows Server 2012 goes into update loop"},"content":{"rendered":"

[German<\/a>]Today I want to bring up again another issue regarding the update behavior of Windows Server 2012 (default, not R2). Some machines running Windows Server 2012 have been in a pending update loop since early November 2019. Now some workarounds has been found.<\/p>\n

<\/p>\n

\"\"An old blog post from November 2019\"\"<\/h2>\n

I had already addressed the topic after a reader's tip in the blog post Pending Pending Update Issue with Windows Server 2012 Standard<\/a> at the beginning of November 2019. The problem: After installing the updates, some Windows Server 2012 goes into a restart loop, where the update process shows the status \"Pending restart\". This status is not vanishing, i.e. the updates are installed repeatedly or retain the status \"Pending restart\" even after a restart.<\/p>\n

\"Update-Verlauf<\/a>
\n(Click to zoom<\/a>)<\/p>\n

In the article, the blog reader had suspected that the \"Desktop Experience\" feature might be involved in this problem.<\/p>\n

Restart loops for Windows Server 2012<\/h2>\n

In Microsoft's Technet Forum there is now this thread<\/a> in which a person affected describes his observation.<\/p>\n

Windows Server 2012 stuck in reboot loop \"Configuring Updates: Stage 2 of 4<\/strong><\/p>\n

After installing November monthly updates from WSUS server, about 80% of 2012 Servers stuck in loop.<\/p>\n

Server (VMware VM) launches a stage 2 of 4 again, then it goes shutdown of services and reboot.<\/p>\n

All Servers restored from backup. Any updates tried to install cause loop.<\/p>\n

Previous monthly updates uninstalling cause loop. Renaming of SoftwareDistribution, rescanning of updates and installing cause loop.<\/p>\n

Last monthly installation has been made without any problems on all Servers.<\/p><\/blockquote>\n

All updates show the same behavior on the affected servers that the update cannot be completed successfully. Currently another administrator has posted this comment<\/a> in the blog. He has this on about 20 machines running Windows Server 2012 (partly virtualized). Microsoft's advice to perform an in-place upgrade for repair installation is not helpful. Programs and data are lost.<\/p>\n

Meanwhile, a reader of my blog has referred<\/a> to this article<\/a>, where the problem is also described. A few days ago Woody Leonhard also posted this article<\/a> on askwoody.com. It also describes a reboot loop on Windows Server 2012 following the installation of the Servicing Stack Update (KB4523208). The article goes back to this report<\/a> by an administrator. He observed the mentioned restart loop on different Windows Server 2012 systems with SSU KB4523208 installed. However, only 6 of 75 servers were affected (bar metal and virtual servers).<\/p>\n

Tip: How to avoid the Update Install loop<\/h2>\n

German blog reader Marco wrote within a comment<\/a>, that manually force Windows Server 2012 to install the Servicing Stack Updates (SSU) first, before the other updates are scheduled for in installation helps avoid the issue.<\/p>\n

Furthermore I was successful with most Win2012 servers after these experiences, if I had installed strictly as first the current \"Service Stack\" update.<\/p><\/blockquote>\n

If the latest SSU is installed, at least known (Microsoft) problems that prevent a successful update installation will be fixed. The description of\u00a0Servicing Stack Update KB4523208<\/a> in\u00a0Microsoft Update Catalog says, that the patch need to be installed\u00a0exklusive.<\/p>\n

Within the Technet forum thread<\/a> user Sasidhar Konduru reports that they identified the Malicious Software Removal Tool (MSRT), update KB890830, as the cause of the installation loop. If KB890830 was installed together with other updates, the installation loop occurred. Once the MSRT was blocked in WSUS for distribution, the update installations went through.<\/p><\/blockquote>\n

If you are caught in an update installation loop, the following solutions may help.<\/p>\n

Solution #1: Booting in Safe Mode<\/h2>\n

Within this post<\/a>, the person concerned writes that he was able to solve the problem by booting in the safe mode. In Safe Mode, the restart loop was interrupted and the update was successfully installed. Using the safe mode to fix the restart loop is also mentioned as a solution in the Technet forum<\/a> and in this article<\/a>.<\/p>\n

In safe mode, only basic Windows functions with a limited set of files and drivers are executed. Safe mode is described in this Microsoft document<\/a>.<\/p><\/blockquote>\n

Solution #1: Launch Trusted Installer Service<\/h2>\n

Other German blog readers commented (here<\/a> and here<\/a>) that the following solution helps:<\/p>\n