The recently rolled out Windows Server updates are causing critical issues with the Windows domain controller going to boot loops, and Hyper-V to break till the updates are reverted back.
Several system admins are facing the aforementioned issues after they installed January 2022 Patch Tuesday update released for Windows Server 2012 R2 KB5009624 update, Windows Server 2019 KB5009557 update, and the Windows Server 2022 KB5009555 update.
One of the most critical issues introduced by these updates is the Windows domain controller going into the boot loop thereby putting the servers into a never-ending cycle of Windows boot.
According to the report by BornCity, the issue affects all supported Windows Server versions.
Talking about this DC boot loop issue, a Reddit user said, “Looks KB5009557 (2019) and KB5009555 (2022) are causing something to fail on domain controllers, which then keep rebooting every few minutes.”
Meanwhile, Windows Server admins say that they observe the LSASS.exe process use all of the CPU resources on the server and then eventually terminate.
LSASS is a highly critical process needed for the efficient running of Windows systems. If the process gets terminated, the whole Operating System will automatically restart.
Another Reddit user shares that when the system restarts due to a crashed LSASS process, the event viewer logs the following error:
"The process wininit.exe has initiated the restart of computer [computer_name] 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 -1073741819. The system will now shut down and restart."
Hyper-V Breaks After Installing Patch Update
Besides the boot loops, the patch update also breaks the Hyper-V and admins are unable to start Hyper-V on the server.
This bug mainly affects the Windows Server 2012 R2 server.
As the bug leads Hyper-V to break, whenever the users try to launch a Virtual machine, they get the following error message:
“Virtual machine xxx could not be started because the hypervisor is not running.”
Looking for more Microsoft news? Signup for our newsletter for the latest update.
