According to customer reports, this month’s Patch Tuesday updates are breaking virtual machines on Hyper-V hosts, causing them to no longer boot and display “failed to start” errors.
According to complaints from Windows admins, the issue is triggered after installing KB5031361 and KB5031364 on Windows Server 2019 and Windows Server 2022 systems.
The following errors will be logged to the event viewer when trying to start a VM on an affected Hyper-V system:
- Failed to start virtual machine TOOLS. Error: ‘TOOLS’ failed to start.
- Failed to Power on with Error ‘Incorrect function.’
- Failed to open attachment ‘vhdx_path’. Error: ‘Incorrect function.’
While Microsoft has yet to acknowledge this as a known issue, administrators with impacted devices have noted that uninstalling the problematic updates resolves the issue, allowing all virtual machines (VMs) to start up without any problems.
This can be accomplished using the Windows Update Standalone Installer (WUSA) tool, which helps install and remove update packages through the Windows Update Agent API.
To fix the Hyper-V boot issues, open an elevated command prompt by clicking the Start menu, typing cmd, right-clicking the Command Prompt application, and choosing ‘Run as Administrator.’
Next, run the following commands, depending on what cumulative update you have installed on your system:
wusa /uninstall /kb:5031364
wusa /uninstall /kb:5031361
​Microsoft has yet to add this as a known issue to the Windows Health Dashboard or confirm the customers’ Hyper-V complaints.
Nonetheless, when it released the buggy cumulative updates, the company revised the support document for KB5031364, including and removing a known issue related to VMware ESXi, describing boot issues encountered by guest VMs operating Windows Server 2022 with Secure Boot enabled.
“After installing this update on guest virtual machines (VMs) running Windows Server 2022 on some versions of VMware ESXi, Windows Server 2022 might not start up,” the now-removed known issue said.
“Only Windows Server 2022 VMs with Secure Boot enabled are affected by this issue. Affected versions of VMware ESXi are versions vSphere ESXi 7.0.x and below.”
Redmond also released emergency out-of-band Windows Server updates in January and December 2022 to fix known issues that caused Hyper-V VMs to no longer start and problems creating new VMs on some Hyper-V hosts.
Microsoft acknowledged a similar issue earlier this year affecting VMware ESXi VMs with Secure Boot after installing February 2023 cumulative updates. VMware issued emergency vSphere ESXi updates that fixed a bug causing boot issues after failing to locate a bootable operating system.
A Microsoft spokesperson could not provide a statement regarding these Hyper-V VM issues when contacted by BleepingComputer on Monday.