If you’re unfamiliar, Patch Tuesday is a term used to refer to monthly security updates from Microsoft and other tech companies. The Windows maker usually releases this update on the second Tuesday of the month. The latest release came on December 13, 2022, with around 50 vulnerability fixes across the Windows OS and other first-party Microsoft software. But this release broke the VM functionality for some users. Precisely speaking, users of Windows Server 2019 and Windows Server 2022 were unable to create new VMs in some Hyper-V hosts. The bug originated from the KB5021249 and KB5021237 updates on Windows Server or Azure Stack HCI hosts. It impacted hosts managed by System Center Virtual Machine Manager (SCVMM) and using software-defined networking (SDN) technologies. The issue prevented affected users from creating new virtual machines. While the existing VMs worked fine, users couldn’t add a network adapter to those. As soon as users started complaining about the issue, Microsoft provided a workaround that involved using an elevated PowerShell window. A few days later, it has now released a proper fix for the problem. The company says users don’t need to make any other changes or install/uninstall additional updates to resolve the issue. The new OOB release will do the trick. The KB update number for users of Windows Server 2019 is KB5022554, while that for Windows Server 2022 is KB5022553. Affected users can search for the KB number in the Microsoft Update Catalog to install the new OOB release (via). As said earlier, the update must be installed manually. Microsoft has provided instructions for importing the update into Windows Server Update Services (WSUS) here, and Endpoint Configuration Manager here.
The latest Patch Tuesday update is causing more headaches for Microsoft
Microsoft’s December Patch Tuesday update contains more bugs, it seems. The company recently warned that some versions of Windows 10 are crashing with the Blue Screen of Death (BSOD) error after installing the KB5021233 update part of this release. Multiple Windows 10 versions appear to be affected, including 22H2, 21H2, 21H1, and 20H2. Microsoft has yet to fix this problem. Meanwhile, affected users can try this official workaround using Windows Recovery Environment (WinRE). Hopefully, a proper fix will arrive soon. Stay tuned.
