ML10 G9 Hyper-V not starting upon Windows 2012 R2 january 11 security update

[Storberg]

Hyperv-V stopped working on ML10 G9 with Windows 2012 R2 after the January 11, 2022—KB5009624 (Monthly Rollup) and event ID 80 was thrown "Hypervisor launch failed; The operating systems boot loader failed with error 0xC00000BB."

The suggested requisites within Hyper-V manger to make the hypervisor start are 1) A processor that support vitualization. 2) Virtualization enabled in bios. 3) Settings in boot configuration data store that launch the hypervisor automatically.

None of these things were modified upfront and the only actual change to the system was the patch update. The Hyper-V starts again when the patch was uninstalled. No other measures have been reported succesful!

Is this actually related to an outdated bios (latest version is 1.13 from 12/05/2019) not compatible with  windows recent patching, or is the problem only related to KB5009624 itself?

Other reports for the same problem on other servers with Windows 2012 R2 exists on the web!

[MDavidRichard]

No it's nothing to do with HPE. Just remove the Microsoft update KB5009586 and reboot...

Good luck!

[Storberg]

Yeah so I did and it helped, but in the beginning there were quite few reports about KB5009624 breaking Hyper-V, so I thought the problem might be isolated to a few server models. Now the reports are exploding and it is clear that it is epidemic and not isolated. The idea that future security updates would not work on certain models like ML10 G9 due to outdated bios would not be appealing!

Thanks!

[Storberg]

Now also offcially recognised by Microsoft Windows 8.1 and Windows Server 2012 R2 | Microsoft Docs