Skip to main content

Server 2012 Datacenter Windows update boot loop

  • December 11, 2019
  • 4 replies
  • 74 views

Forum|alt.badge.img

Several servers stuck on a reboot cycle after Windows Update last night (Tuesday - Wednesday).

This appears to be a combination of 2019-12 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB4530691)
and
2019-12 Servicing Stack Update for Windows Server 2012 for x64-based Systems (KB4532920)

The solution is to boot the server in safe mode and allow the update to fail. This can take a long time.

I think that the way to avoid this is to manually install 2019-12 Servicing Stack Update for Windows Server 2012 for x64-based Systems (KB4532920) before the rollup, but I am still testing this.

I don’t imagine this will impact too many users, but hopefully the above helps someone.

4 replies

Nic-Automox
  • Former Automox Employee
  • 832 replies
  • December 11, 2019

Thanks for sharing this @david.thomson!

Anyone else running into this issue?


Forum|alt.badge.img
  • Author
  • Novice
  • 34 replies
  • December 12, 2019

Some users on another forum are experiencing the same problem - apparently it is not limited to Server 2012. I walked in to the same three servers in a boot loop this morning, so I would be careful with the patches released this week.


  • Rookie
  • 1 reply
  • December 16, 2019

Had the same problem. Had to boot on safe mode, uninstall KB4530691 (2019-12 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems) and KB4530677 (2019-12 Cumulative Security Update for Internet Explorer 11 for Windows Server 2012 for x64-based Systems), reboot and reinstall the 2 KBs.
On an another server, to avoid the problem, I’ve installed first KB45332920 (2019-12 Servicing Stack Update for Windows Server 2012 for x64-based Systems), reboot and then install the 2 other KBs.


Nic-Automox
  • Former Automox Employee
  • 832 replies
  • December 16, 2019

Your fix sounds like the same approach @david.thomson is using, so it’s good to get confirmation on the workaround!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings