Updated Microsoft’s first Patch Tuesday of 2022 has, for some folk, broken Hyper-V and sent domain controllers into boot loops.
A Register reader got in touch concerning KB5009624, which they said “breaks hypervisors running on WS2012R2.”
“I’m currently dealing with this right now and it’s a hassle,” our reader said.
“After several tries and fails, I deinstalled the KB and tadaa! Everything went back to normal.”
Our reader is not alone. As well as the broken Hyper-V, popular tech blog Born City noted problems with boot loops on domain controllers, with other versions of Windows Server affected.
Posters in a Reddit thread complained that KB5009546 (for Windows Server 2016) and KB5009557 (for Windows Server 2019) were probably also to blame and recommended a swift uninstall of the patches for those affected.
The breaking of Hyper-V means that virtual machines can’t be started on the server. Constant reboots are not… good. Oh, and some users have also reported that Windows Resilient File System (ReFS) volumes are left inaccessible after the update. It’s a veritable three-ring circus of fun from your friends at Microsoft.
As for the updates, a common thread appears to be an Active Directory fix, although a TITSUP* hypervisor and boot loop problems are not listed as known issues for any.
Still, if you’re running Windows Server 2012 R2, you might not have much longer to worry about Microsoft breaking things. Extended support ends next year (although you can prolong the pain with extended security updates into 2026). Windows Server 2016 went out of mainstream support on 11 January 2022.
Going out with a bang in an all too real sense of the word.
While uninstalling the patches appears to resolve the issues for those affected, the patches also contain important security fixes. Their removal should therefore be a last resort and only if the issues are being experienced.
The Register asked Microsoft if it was aware of the problems and planned to issue further fixes. We will update this piece should the company respond. ®
*Tired IT Staffers Uninstall Patches
Updated at 17.08 UTC on 13 January 2022 to add:
Following publication of this article, Microsoft sent us a statement: “We are aware of the reports and are investigating.”
So that’s ok then.