The server was up to date so it was just missing the latest Security Update for CU11 and the latest cumulative 2022-01 update.
As a result, you may fail to access the Exchange Admin Center (EAC) or Exchange Management Shell (EMS).Īs explained by an Exchange administrator on Spiceworks community, “Today I was patching our exchange 2019 server (running on server 2019 Core). If you are running Microsoft Exchange Server on Windows Server 2012 or a later operating system, the update may break the server. When administrators start the Hyper-V, they receive an error, such as, "Virtual machine xxx could not be started because the hypervisor is not running." Damaged Exchange Server However, it may affect newer versions as well. This bug is reported in Windows Server 2012. Some administrators have also reported Hyper-V crashing and not starting after installing the January 2022 updates. The system will now shut down and restart. The process wininit.exe has initiated the restart of computer DEIMOS on behalf of the user for the following reason: No title, for this reason, could be found Reason Code: 0x50006Ĭomment: The system process 'C:\WINDOWS\system32\lsass.exe' terminated unexpectedly with status code -1073741819. If you check the event log after the restart, it displays the following information, Therefore, if this process is terminated, the operating system automatically restarts.Īfter the update, LSASS.exe was found utilizing all CPU resources on the server and then terminating automatically, leading to endless reboot cycles and BSODs. Windows operation system requires the LSASS.exe process to work properly. The boot loop is caused by a critical Windows process called LSASS.exe. The server reboots with error codes 0xc0000005 and 0xc0000006. This issue is reported in all supported Windows Server versions.
Endless Boot LoopĪfter installing the updates installing Windows Server operating system updates, administrators encounter endless boot loops where Windows Server starts and then automatically reboots after a few minutes. Issues Caused by January 2022 Windows Server Updatesįollowing are the issues reported by administrators and users who experienced them just after installing the January 2022 updates on their Windows Server machine.
The Windows Server updates released on Patch Tuesday this month were supposed to fix the bugs and patch vulnerabilities on the server.
In this blog, you will learn about the bug causing the server crash and the steps to troubleshoot and fix the issue. Some users have reported on various forums about the bug in the update breaking the Hyper-V, causing Domain Controller to enter into boot loops, and leading to inaccessible or RAW ReFS volumes and Exchange Server. Summary: Microsoft's recent updates for supported versions of the Windows Server operating system released on Patch Tuesday this month reportedly led to server crashes.