The system will now shut down and restart." Hyper-V no longer starts
#DISM FOR CRITICAL UPDATES CODE#
"The process wininit.exe has initiated the restart of computer 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 following error will be logged to the event viewer when restarting due to a crashed LSASS process, as another user on Reddit shared. "Looks KB5009557 (2019) and KB5009555 (2022) are causing something to fail on domain controllers, which then keep rebooting every few minutes," a user posted to Reddit.Ī Windows Server administrator told BleepingComputer that they see the LSASS.exe process use all of the CPU on a server and then ultimately terminate.Īs LSASS is a critical process required for Windows to operate correctly, the operating system will automatically restart when the process is terminated. The most serious issue introduced by these updates is that Windows domain controllers enter a boot loop, with servers getting into an endless cycle of Windows starting and then rebooting after a few minutes.Īs first reported by BornCity, this issue affects all supported Windows Server versions.
#DISM FOR CRITICAL UPDATES UPDATE#
Yesterday, Microsoft released the Windows Server 2012 R2 KB5009624 update, the Windows Server 2019 KB5009557 update, and the Windows Server 2022 KB5009555 update as part of the January 2022 Patch Tuesday.Īfter installing these updates, administrators have been battling multiple issues that are only resolved after removing the updates. The latest Windows Server updates are causing severe issues for administrators, with domain controllers having spontaneous reboots, Hyper-V not starting, and inaccessible ReFS volumes until the updates are rolled back Update 1/17/21: Microsoft has released OOB updates to fix the Windows Server bugs.
0 kommentar(er)
