How To Restart Windows Server 2012 Machine

If you encounter a Windows Server 2012 reboot loop issue, let me share a workaround for information technology. The workaround here is to uninstall the updates or interrupt the kicking and use Safety Manner.

Update – Microsoft released the Windows Server 2012 R2 KB5009624 update, Windows Server 2019 KB5009557 update, and Windows Server 2022 KB5009555 update every bit role of the January 2022 Patch Tuesday. Installing these updates will crusade Windows domain controller kicking loops.

The updates also touch on the Hyper-V servers and most admins have observed the Hyper-5 non starting, and inaccessible ReFS volumes until the updates are rolled back.

Note: All these Ad patches are bad, seeing tons of wacky and unexpected behavior subsequently install

KB5009624 – Applies to Windows Server 2012
KB5009557 – Applies to Windows Server 2019
KB5009555 – Applies to Windows Server 2022

Windows Domain Controller Boot Loops Issue

Installing the updates KB5009624, KB5009557 and KB5009555 are causing the domain controllers to reboot and cause the boot loops. These updates are impacting the LSASS.exe process that use all the CPUs on a server and then ultimately finish.

Equally LSASS.exe is a disquisitional procedure on Windows Server required to operate correctly. The server operating system volition automatically restart when the process is terminated and cause Windows Server 2012 reboot loop.

The Windows domain controller server boot loops issue is reported on Reddit by a user who says January 2022 updates causing unexpected reboots on domain controllers. Looks like KB5009557 (2019) and KB5009555 (2022) are causing something to fail on domain controllers, which then keep rebooting every few minutes.

After installing the updates KB5009624, KB5009557 or KB5009555, Windows Server 2012 reboot loop event occurs and the following details are logged in the event viewer.

"The process wininit.exe has initiated the restart of computer [computer_name] on behalf of user for the following reason: No championship for this reason could be found Reason Code: 0x50006 Shutdown Type: restart Annotate: The system process 'C:\WINDOWS\system32\lsass.exe' terminated unexpectedly with status lawmaking -1073741819. The system volition now shut downwardly and restart."

Fix January 2022 Updates Domain Controller Boot Loop Event

If you lot have updated the domain controllers with the Jan 2022 updates, the simply way to fix the domain controller reboot outcome is past uninstalling the updates.

If you have installed any of these updates on Hyper-Five servers, y'all may run into the following mistake while powering on the VMs.

"Virtual machine xxx could not exist started considering the hypervisor is not running."

System admins managing the Windows Servers can manually uninstall the updates with the following commands.

Windows Server 2012 R2: wusa /uninstall /kb:KB5009624
Windows Server 2019: wusa /uninstall /kb:KB5009557
Windows Server 2022: wusa /uninstall /kb:KB5009555

Note: Some users are noticing that from the above command removing the KB prefix from the command works. So, you can use the below commands if the above ones don't work.

Windows Server 2012 R2: wusa /uninstall /kb:5009624 Windows Server 2019: wusa /uninstall /kb:5009557 Windows Server 2022: wusa /uninstall /kb:5009555

If your Windows Server 2012 goes into kicking loop, don't worry because a lot of Information technology admins are really dealing with the aforementioned issue. Information technology'due south non your fault, either, it'south an update that has caused the reboot loop on your Windows Server 2012.

We have still got few VM'due south running Windows Server 2012 while near of the VMs are running 2012 R2 and in a higher place. Today, on two VMs'due south running SCCM distribution bespeak role, I noticed the reboot loop consequence.

After restarting the VMs I never saw any login screen. It simply stays at "please look" and and then the server restarts.

Fix Windows Server 2012 Reboot Loop Issue

If you lot practice a scrap of inquiry on why this reboot loop issue occurs, you will notice a lot of info on the spider web. A reboot loop on Windows Server 2012 could be due to the installation of the Servicing Stack Update (KB4523208). In this thread, one of the users identified the Malicious Software Removal Tool (MSRT) update, KB890830, as the cause of the installation loop.

The workaround here is to interrupt the boot and utilise Safe Mode. It will notwithstanding reboot at the same stage trying to boot into safe manner but next boot works.

Fix Windows Server 2012 Reboot Loop Issue

To gear up the Windows Server 2012 boot loop upshot, perform the following steps.

Offset of all restart the VM or motorcar running Windows Server 2012.
Go to Advanced Kicking Options by pressing F8 key.
Nether Advance boot options, select Condom Fashion and printing enter key.
In one case the Bone boots in safe mode, don't login. Reboot the Windows Server again.
This fourth dimension let the server start normally. You should see a login screen.