Solved: Windows Server 2019 Boot Loop After Update

User case: Windows Server 2019 stuck in boot loop

“ Hello, I have 2 Windows Server 2019 with SQL server installed, there are some Windows updates that require restart after restart both Windows Server failed to boot with restart loops. After 3 restart loop show the blue screen with error code: APC Index Mismatch... All in all, my Windows Server 2019 keeps rebooting. Is there any idea to resolve this issue...? Thanks a lot. ”

Numerous reports have surfaced from users indicating that after installing the January 2022 Windows Update, Windows Server 2012 R2, 2019, and 2022 are getting stuck in a continuous reboot loop. This can be a frustrating and disruptive issue. If you are experiencing this problem, continue reading to find a solution to resolve the Windows Server 2019 booting loop issue after the update.

What causes Windows Server 2019 to become stuck in boot loops?

Specific bugs are responsible for Windows Server reboot loop after update. After installing the January 2022 Windows Update, the system may fail to boot properly, resulting in a continuous reboot loop. This can be attributed to the changes made to the boot process by the update, which may conflict with certain system configurations or drivers.

The issue can be particularly problematic for Windows Server 2019 users, as it can result in downtime and loss of data. As a result, it is important to take appropriate measures to resolve the problem as quickly as possible. Of course, there may be some other reasons here as well:

• Update failure
• Corrupted RAM sticks
• Outdated drivers
• Bad Registry entries
• Hard drive issues

How to fix Windows Server 2019 boot loop issue

So in this section, we will show you how to fix this issue via Command Prompt.

How to access Command Prompt:

Step 1. Insert the Windows Server 2019 installation CD/DVD into the affected machine and modify the boot drive in the BIOS to boot from it.

Step 2. When prompted with Press any key to boot from CD or DVD, press a key to continue.

Step 3. Select your preferred language, time and currency format, and keyboard or input method, and click on Next.

Step 4. Select Repair your computer in Windows Server 2019, and click on Next to proceed.

Step 5. Within the System Recovery Options window, choose the Command Prompt option.

Once you have entered the Command Prompt, you may attempt one or more of the following solutions based on your specific circumstances.

1. Run DISM command to resume ongoing updates

If Windows Server 2019 becomes stuck on the restarting screen after an update and displays the message "We couldn’t complete the updates. Undoing changes. Don’t turn off your computer", you may restore the pending update by executing the following command to resolve the error.

mkdir d:\scratch (By executing this command, a new directory named "Scratch" will be created.)

D:\>dism /Image:D:\ /ScratchDir:D:\Scratch /Cleanup-Image /RevertPendingActions

Tip: Please note that the letter "D" in this context corresponds to the drive letter where the "Windows" folder is located. You may substitute this letter with the appropriate drive letter in your specific scenario.

Once the update has been successfully reverted, you may exit the Command Prompt and restart your machine from the system hard drive to check if Windows Server 2019 boot loop is solved.

2. Recover bad registry from Regback

To restore system registry files from a backup for resolving the Windows Server2019 automatic repair loop issue caused by missing or corrupted registry files, follow the steps below:

Tip: It is essential to backup system files to the recovery drive to effectively avoid data loss.

Step 1. Confirm your system drive. You can do this by running the command "dir c:" and checking if it lists folders such as "Program Files" and "Users", which are typically located on the system drive.

Step 2. Type the command:

"copy d:windowssystem32configRegBack* d:windowssystem32config" and hit enter.

This will copy the backup registry files located in the "RegBack" folder to the "config" folder, overwriting any corrupted or missing registry files.

▶Attention: If the drive letter of your system drive is not "d", please replace "d" with the appropriate corresponding letter. It is important to note that this method may not be effective if the backup of the registry is too outdated.

3. Run the Bootrec command to repair the MBR

Oftentimes, boot failure can be attributed to a corrupted MBR. To begin rebuilding the BCD and repairing the MBR, please enter the following command:

• bootrec.exe /fixmbr - This command writes a new MBR (Master Boot Record) to the system partition.
• bootrec.exe /fixboot - This command writes a new boot sector onto the system partition.
• bootrec.exe /scanos - This command scans all disks for Windows installations.
• bootrec.exe /rebuildbcd - This command provides a choice of which entries to add to the BCD store after scanning all disks for Windows installations.

Afterward, you may run Chkdsk to detect and repair any corruption in the hard drive filesystem. Please enter the following command with the letter of the partition driver.

• chkdsk/r c:

Reboot your computer to see if these steps have resolved the issue that Windows Server 2019 reboot loop after update.

4. Uninstall Windows update

The January 2022 Windows Update released by Microsoft has been found to cause Windows Server 2019 domain controllers to become stuck in boot loops. And there are certainly some reports that have also found Windows Server 2016 boot loop after update.

If you are experiencing this problem, you may attempt to resolve it by booting from the installation media and using the Command Prompt to uninstall specific updates using the command lines provided below:

To begin, boot your system from the installation media and access the Command Prompt as previously instructed. Next, enter the following command and press "Enter":

• wusa /uninstall /kb:4093123

Important Note: Create Windows Server 2019 backup to prevent data loss

After solving the Windows Server 2019 boot loop issue, we realized that it is important to create a backup before performing any operation that may result in data loss or system crashes, especially if you are experiencing issues with your computer. However, due to the limitations of Windows Server Backup, such as 2 TB storage capacity and restricted number of backups, it is recommended to use reliable server backup software such as AOMEI Backupper Server.

AOMEI Backupper Server offers a variety of rich features to meet all your server backup needs. It enables you to create backups of your system, disk, partition, and files. You can also create cloud backups to store important data in the AOMEI Cloud. Additionally, you can schedule automatic backups in five different modes - Daily, Weekly, Monthly, Event Triggers, and USB Plug In.

The software supports a wide range of backup destinations, including internal/external hard drives, network shares, and NAS devices, among others. It is compatible with various Windows Server systems, including 2003, 2008, 2012, 2016, 2019, 2022 (including R2), SBS 2003, 2008, 2011, as well as Windows PC systems.

Download this powerful Server backup software without hesitation and easily backup your Windows Server 2019 system now:

Step 1. Open AOMEI Backupper Server. Then click Backup > System Backup.

Note: Choose the appropriate backup option depending on whether you would like to back up the entire disk, partition, or specific files and folders.

Step 2. By default, the system data will be selected. Please select a destination path to store the backup image.

Step 3. Once you have confirmed the desired backup operations, click on Start Backup to initiate the backup process for Windows Server 2019.

Summary

This article aims to solve the Windows Server 2019 boot loop problem, and provides access to Command Prompt to solve this problem effectively. It is strongly recommended to use professional backup software - AOMEI Backupper Server to backup your Windows Server 2019 to avoid data loss. This software not only has backup function, but it can also backup Synology to Windows Server, try it now!