[German]Microsoft Hyper-V users running Windows Server 2012/R2 should be cautious about installing update security update KB5009586 or KB5009624 for Windows Server 2012/R2. The security updates released on January 11, 2022 have several unpleasant collateral damages at once. After installing the security updates, the Hyper-V host (Windows Server 2012, Windows Server 2012 R2 or Hyper-V Server 2012) can no longer be started. Here's an overview of what's currently known about this in reader comments from the blog and elsewhere.
Advertising
Hyper-V fails after update installation
Regarding the German blog post Patchday: Windows 8.1/Server 2012 R2-Updates (11. Januar 2022), mögliche Boot-Probleme erreichten , I received several reader comments complaining about a Hyper-V host not starting. From user TomTom there is in this German comment with the following details (I've translated the text):
VM's on Server 2012 R2 Hypervisor do not start anymore.
The error message is that the hypervisor is not running.In the event log is logged when starting the HyperV server: (ID 80, Hyper-V hypervisor)
Hypervisor launch failed; The operating systems boot loader failed with error 0xC00000BB.Error was on multiple servers, KB5009624 uninstalled, hypervisor restarts normally.
And German blog reader Bernhard, who is also affected, told me the following:
Our 2012 Hyper-V server doesn't want after KB5009586 update either!
"Error while trying to start the selected virtual computers".
"Virtual computer XXXXX could not be started because the hypervisor is not running."
After uninstalling KB5009586 it runs again, but unfortunately it crashed the Linux virtual machines, so by means of Restore they had to be restored.
German blog reader Bruno Studerus wrote in this comment:
We also had the same problem with KB5009624 on a customer installation with Windows 2012 R2 this morning. The virtual Hyper-V hosts could not be started.
Error message then: Error during initialization: The virtual computer could not be started because the hypervisor is not running.
Removed the service pack KB5009624 from the server and restarted the host server. After that the virtual Hyper-V servers worked again. The KB5009624 now immediately excluded from the Windows updates.
I also received similar comments here within my English blog. German blog reader LV mentioned in this comment:
And another thing: HyperV cluster: Livemigration broken.
After uninstallation ok again..
In all cases, the only solution I know of is to uninstall the January 11, 2022 security update.
Advertising
Similar articles:
Microsoft Office Updates (January 4, 2022)
Microsoft Security Update Summary (January 11, 2022)
Patchday: Windows 8.1/Server 2012 R2 Updates (January 11, 2022), boot loop reported
Patchday: Windows 10 Updates (January 11, 2022)
Patchday: Windows 11 Updates (January 11, 2022)
Patchday: Updates for Windows 7/Server 2008 R2 (January 11, 2022)
Windows Server: January 2022 security updates are causing DC boot loop
Windows VPN connections (L2TP over IPSEC) broken after January 2022 update
Windows Server 2012/R2: January 2022 Update KB5009586 bricks Hyper-V Host
Advertising
I just wanna say thanks for this, i was blowing my mind trying to faind what the hell is going on.
This Is really a great site. Everyday news very usefull to sysadmis
I did not have this update installed but I did have KB5009624 that was causing this problem. I uninstalled it and then Hyver-v works again.
hi how to uninstalled KB5009624 please guide me
Same here, did not have KB5009586 installed but KB5009624. Removed KB5009624 and Hypervisor working
Took us down too. Thanks Microsoft.
me paso lo mismo ojala resuelvan esto!
Had the same problem this morning…thank you for this !!!
Same issue here. Removing the 3 Windows Updates from last night fixed the issue.
Many thanks for the update here! It was driving me crazy trying to figure out what the issue was.
Spent last night until midnight first trying to understand what the heck just happened and eventually rolling back the updates. The Windows 2012R2 update also caused frequent system reboots with following error message so even without Hyper-V this update was complete crap.
The process wininit.exe has initiated the restart of computer xxxx on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
You are hit by two bugs – the Hyper-V thing and the DC but – see my linked articles at the end of the blog post.
you have saved my life man , i was pulling my hair for 2 day literary , i almost burned the server . i was planning to run the DRP to make the system run for the company. you r the man. appreciate your help .
Thanks for this article! The same problem for me this mornig!
Windows Server 2012, Hyper-V
The process wininit.exe has initiated the restart of computer VILFS1 on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
Uninstalled KB5009586 only, all running present and correct after.
wusa /uninstall /kb:5009596 /quiet
Thanks for the info guys…..
Thanks for the info, had me stumped for most of the day.
You're a legend man! Thanks a lot dude!! I had the same problem this morning
This has also fixed an issue where the lsass.exe was running into a problem and needed to restart the server every 1-4 hours with no BSoD. Thank you!
Uhg… Just finding this article now. What version of Server? I have a W2012 R2 server restarting randomly with lsass errors…
The same problem here this morning…thank you for this !!!
Thanks a lot roll back the updates and it works
just spent 2 hours pulling my hair out, and found your article. Thank You so much!
thanks
Thank you very much for the information! I was already about to send someone at 6am tomorrow to check the BIOS settings on the servers.
Microsoft, we started badly this year
my system is shutting down within 1.5 min which is not allowing me time to uninstall the KB. Any ideas?
Try entering Safe Mode and uninstall.
This article just saved my life ! This f**** update blows my 7 VMs and my users were close to hang me. Thanks a thousand times !
viele danken !
Thanks,this site helped me twice this week (both regarding windows updates),is there any way to subscribe to mailing list or something?
I don't have a mailing list – it has some GDPR reasons (GDPR=General Data Protection Rules), which I would be responsible for.
I equally had a similar challenge, been cracking my head with it from the 12th of January, this information was very helpful,. Uninstalled KB5009624 update and all the VMs are now up.
Thank you
Hey everyone, this affected us as well. However a KB not mentioned to this point is what caused the "Virtual machine could not start because the hypervisor is not running" error we were experiencing.
On Server 2012 Standard (old dog slated for replacement), we needed to uninstall: KB5009619
Relevant Microsoft Post:
https://support.microsoft.com/en-us/topic/kb5010797-out-of-band-update-for-windows-server-2012-january-17-2022-1f14f497-8404-404d-8d78-0c962c9e486d
"This update resolves the following issues:
Virtual machines (VMs) located on a server that has Unified Extensible Firmware Interface (UEFI) enabled fail to start after installing the January 11, 2022 Windows update."
Microsoft Catalog with the fixed out-of-band update:
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5010797
We uninstalled KB5009619, rebooted, and verified the VMs would launch again (they did). Then we installed KB5010797 from the catalog, rebooted, and again tested and confirmed the VMs will still launch with KB5010797 installed.