Our hosts decided to reboot. Only one of the hosts wouldn’t start VMs. They’d sit there fine while off but attempt to start them and they’d fail.<\/p>\n\n\n\n
<\/p>\n\n\n\n
“Virtual machine ‘VM Name’ could not be started because hypervisor is not running.”<\/p>\n\n\n\n
<\/p>\n\n\n\n
Turns out this is because of Windows update<\/p>\n\n\n\n
KB5009624<\/p>\n\n\n\n
KB5009595<\/p>\n\n\n\n
<\/p>\n\n\n\n
Are the cause. Uninstall and all will be fine.<\/p>\n\n\n\n
wusa \/uninstall \/kb:5009595 \/quiet \/norestart<\/p>\n\n\n\n
wusa \/uninstall \/kb:5009624 \/quiet \/norestart<\/p>\n\n\n\n
<\/p>\n\n\n\n
You’ll probably need to do a restart but you might want to control it rather than the command doing it.<\/p>\n\n\n\n
Probably a good idea to remove from WSUS for now if still using WSUS.<\/p>\n","protected":false},"excerpt":{"rendered":"
Our hosts decided to reboot. Only one of the hosts wouldn’t start VMs. They’d sit there fine while off but attempt to start them and they’d fail. “Virtual machine ‘VM Name’ could not be started because hypervisor is not running.” … Continue reading