عربي
Windows

How to Fix Windows 10 Automatic Repair Loop

By the TechBridge team 7 min read
Laptop computer showing the Windows automatic recovery troubleshooting screen on a desk

When your computer gets stuck displaying "Preparing Automatic Repair" or restarts continuously to the same blue recovery screen, your system is trapped in an automatic repair loop. This issue occurs when Windows detects that something interrupted normal startup but fails to resolve the underlying file, boot configuration, or hardware driver conflict on its own.

Rather than reinstalling your operating system immediately, you can resolve the boot failure using built-in Windows Recovery Environment (WinRE) utilities. Follow these proven diagnostic steps in order, starting with simple peripheral isolations before moving into command-line repairs and restore options.

Disconnect External Peripherals and Perform a Hard Reset

The simplest reason Windows fails to boot is an external device interfering with hardware detection during early initialization. Printers, external storage drives, USB hubs, webcams, and docking stations can cause the system firmware or startup drivers to stall, triggering an unnecessary repair cycle.

To rule this out, shut down your computer completely. Unplug every connected peripheral except your basic wired keyboard, mouse, and primary display monitor. If you are troubleshooting a desktop PC or a laptop with a removable power source, disconnect the power cable or battery, press and hold the physical power button for 30 seconds to drain residual electrical charge from the motherboard, and reconnect only the power cable. Turn the computer back on to see if Windows boots cleanly to the desktop.

Access Windows Recovery Environment (WinRE)

Most advanced fixes require access to the Windows Recovery Environment (WinRE). When your computer fails to boot two consecutive times, Windows automatically attempts to load this menu, presenting a blue screen labeled Automatic Repair with an option to select Advanced options. If your machine reboots before showing this screen, you can force WinRE manually using the hard interrupt method:
  1. Turn on your PC by pressing the power button.
  2. As soon as you see the computer manufacturer logo or the initial Windows loading dots, hold down the power button for 5 to 10 seconds until the system shuts off completely.
  3. Repeat this process twice. On the third restart, let the machine power up without touching the button.

Windows will display Preparing Automatic Repair followed by Diagnosing your PC, eventually presenting the Choose an option screen. From here, navigate to Troubleshoot > Advanced options to access recovery tools.

Repair Boot Configuration and Master Boot Record via Command Prompt

Corrupted Boot Configuration Data (BCD) or a damaged Master Boot Record (MBR) is the leading software cause behind an infinite repair loop. Fixing these records points Windows back to the correct system partition and startup loaders. From the Advanced options menu, click on Command Prompt. If prompted, select your administrator account and enter your password. Once the command window opens, type the following commands one by one, pressing Enter after each line:

bootrec /fixmbr

bootrec /fixboot

bootrec /scanos

bootrec /rebuildbcd

If the command bootrec /fixboot returns an "Access is denied" error, you may need to assign a drive letter to your hidden EFI system partition via diskpart to refresh the boot sector files. When bootrec /rebuildbcd asks if you want to add an identified Windows installation to the boot list, type Y and hit Enter. Close the window and select Continue to test the boot process.

Scan System Files and Disk Integrity with SFC and CHKDSK

Sudden power outages or unexpected reboots often corrupt core system files and introduce bad sectors on your drive. Windows provides System File Checker (SFC) and Check Disk (CHKDSK) to locate and repair these inconsistencies offline. Open Command Prompt from Troubleshoot > Advanced options again. First, determine your primary Windows drive letter, as recovery environments often reassign the system drive from C: to D: or E:. Type dir C: and check if the Windows folder exists. If not, check D:. Assuming your Windows drive is assigned to C:, execute this command to repair bad disk sectors:

chkdsk C: /f /r

Allow the disk check to complete, which can take anywhere from twenty minutes to several hours depending on your storage type and capacity. Once finished, run the System File Checker offline repair by entering:

sfc /scannow /offbootdir=C:\ /offwindir=C:\windows

This command instructs SFC to replace corrupted Windows system files using verified local backup copies without needing active background services.

Disable Early Launch Anti-Malware Protection

Windows contains an early-stage security feature called Early Launch Anti-Malware (ELAM) driver protection. While designed to block rootkits from executing before critical system services, it can mistake legitimate, outdated third-party security software or newly updated drivers for malicious files, creating an endless restart loop. To bypass this check and determine if an overzealous security driver is the culprit:
  1. From the recovery menu, select Troubleshoot > Advanced options > Startup Settings.
  2. Click the Restart button located at the bottom-right corner.
  3. When your computer restarts, you will see a numbered list of startup choices. Press 8 or F8 on your keyboard to select Disable early launch anti-malware protection.

If your computer boots normally after making this choice, immediately update or temporarily uninstall third-party antivirus utilities and update your chipset and graphics drivers.

Roll Back Recent Updates or Use System Restore

A problematic quality patch, cumulative update, or recently updated device driver can prevent Windows from completing initialization. If hardware scans and boot record repairs have not cleared the loop, reverting the system to an earlier known good state is the next logical step. Within Advanced options, select Uninstall Updates. Windows gives you two choices: Uninstall latest quality update (routine monthly patches) and Uninstall latest feature update (larger version upgrades). Start by selecting the latest quality update and follow the on-screen prompts. This preserves all user files while removing recent software modifications. If update removal fails or does not solve the problem, return to Advanced options and click System Restore. Select a restore point dated prior to when the repair loop began and confirm the operation. Windows will restore protected registry files and driver configurations back to that timestamp.

The bottom line

An automatic repair loop in Windows 10 is usually the result of damaged boot pointers, corrupted system libraries, or driver conflicts rather than permanent hardware failure. Working methodically through peripheral disconnection, BCD rebuilding, and disk verification typically restores your computer to operating status without personal data loss. If none of these solutions succeed, creating a bootable USB installer to run a repair in-place or choosing "Reset this PC" with file retention will provide a clean foundation.

Frequently asked questions

What causes the Windows 10 automatic repair loop?

The loop is commonly triggered by corrupted Boot Configuration Data (BCD), bad sectors on the primary drive, incomplete Windows updates, damaged registry hives, or third-party antivirus drivers conflicting with startup processes.

Will fixing the automatic repair loop delete my files?

No. Standard troubleshooting steps like CHKDSK, SFC, bootrec commands, and System Restore keep your personal files intact. Only factory resets or clean partition reinstallations risk data loss.

What should I do if bootrec /fixboot returns 'Access is denied'?

This happens on modern UEFI systems when the EFI partition requires reinitialization. You can resolve it using the diskpart utility in Command Prompt to assign a drive letter to the EFI system volume and running the bcdboot command to regenerate the boot files.

How do I boot into Safe Mode from the automatic repair screen?

From the blue Automatic Repair screen, navigate to Troubleshoot > Advanced options > Startup Settings, click Restart, and press 4 or F4 to enable standard Safe Mode.

Tags:

Related articles