Update Microsoft’s first Patch Tuesday of 2022 has, for some people, broken Hyper-V and sent domain controllers into boot loops.
A Register reader contacted regarding KB5009624, which they claim “breaks hypervisors running on WS2012R2”.
“I’m dealing with this right now and it’s a problem,” our reader said.
“After several attempts and failures, I uninstalled the knowledge base and tadaa! Everything is back to normal.”
Our reader is not alone. In addition to broken Hyper-V, popular tech blog Born City Noted issues with boot loops on domain controllers, with other versions of Windows Server affected.
Posters in a Reddit thread complained this KB5009546 (for Windows Server 2016) and KB5009557 (for Windows Server 2019) were probably also to blame and recommended a quick patch uninstall for those affected.
Breaking Hyper-V means virtual machines cannot be started on the server. Constant reboots are not… good. Oh, and some users also reported that Windows Resilient File System (ReFS) volumes remain inaccessible after the update. It’s a real three-ring circus fun from your friends at Microsoft.
As for updates, a common thread appears to be an Active Directory fix, although a TITSUP* hypervisor and bootloop issues are not listed as known issues for any.
However, if you are using Windows Server 2012 R2, you may not have to worry about Microsoft’s problems much longer. Extended support ends next year (though you can prolong the pain with extended security updates until 2026). Windows Server 2016 is no longer supported as of January 11, 2022.
Going out with a bang in an all too real sense of the word.
Although uninstalling the patches seems to solve the problems for those affected, the patches also contain important security fixes. Deleting them should therefore be a last resort and only if problems are encountered.
The register asked Microsoft if they were aware of the issues and planned to release further fixes. We’ll update this article if the company responds. ®
* Tired IT staff uninstall patches
Updated 17:08 UTC Jan 13, 2022 to add:
Following the publication of this article, Microsoft sent us a statement: “We are aware of the reports and are investigating.”
So, how are you.