KB5009624 or KB5009595 Virtual Machine could not be started.
This month’s Patch Tuesday (January 11th, 2022) has featured two updates that appear to break Hyper-V on Windows Server 2012 R2 servers. If you installed either KB5009624 or KB5009595 and are receiving “Virtual Machine {VM NAME} could not be started because the hypervisor is not running”, then you should uninstall both updates and restart.
The following events will also be visible in the System Event Logs:
Source: Hyper-V-Hypervisor
Error ID: 80
Hypervisor launch failed; The operating systems boot loader failed with error 0xC00000BB.
Source: Hyper-V-VMMS
Error ID: 15350
The virtualization infrastructure driver (VID) is not running.
Source: Hyper-V-VMMS
Error ID: 15160
‘MACHINE NAME’ failed to restore virtual machine state.
Workaround
There is no permanent solution currently available. To fix this problem, you need to remove the update from the Hyper-V host by doing the following:
1) Open elevated command prompt on the Hyper-V Host
2) Run “wusa /uninstall /kb:5009624”
3) Run “wusa /uninstall /kb:5009595”
4) Reboot the Hyper-V Host
Microsoft has also publicly acknowledged the issues at Windows 8.1 and Windows Server 2012 R2 | Microsoft Docs. There is still no fix to resolve the issue. Also, both updates are still available and haven’t yet been pulled by Microsoft.
I hope this article was helpful, if you have any questions, please feel free to contact me. If you would like to be notified of when I create a new post, you can subscribe to my blog alert.
Loading ...