Product reviews, deals and the latest tech news

There is a fix for the Microsoft patch that broke some virtual machines (VMs)

Because the most recent Patch Tuesday update prevented certain users from building new virtual machines in select Hyper-V hosts, Microsoft has provided an emergency remedy.

The update KB5021249 or KB5021237 installed on Windows Server or Azure Stack HCI hosts caused the problem, which affected users of Windows Server 2019 and Windows Server 2022.

According to the status update, the defective update only affects new virtual machines (VMs) generated after installation and not existing ones.

When will things improve for users?

By releasing out-of-band (OOB) upgrades for Hyper-V hosts on December 20, Microsoft has fixed the problem.

According to Microsoft, there is no need to apply updates or make modifications to other servers or client devices in the system in order to fix this problem.

The KB number for these OOB updates may be looked up in the Microsoft Update Catalog if you wish to download the standalone package (opens in new tab).

According to Microsoft, these patches may then be imported into WSUS and ECM manually.

This isn’t the first Patch Tuesday update to have major consequences for consumers in 2022.

The KB5019980 upgrade in December 2022 broke connections to databases that relied on the Microsoft ODBC SQL Server driver.

However, weekly updates, or “Patch Tuesdays,” may not be around for much longer.

Microsoft released a programme in July 2022 that will automate the distribution of critical updates through Windows Update for Business.

With a Windows Enterprise E3 or E5 licence, you can have access to Microsoft Autopatch, a patching solution for Windows 10, Windows 11, Microsoft Edge, and Microsoft 365.