Startup Repair Infinite Loop: Real Fixes That Work

If Windows 10 Startup Repair keeps looping and never finishes, the automatic repair process is failing to fix the underlying boot problem and restarting instead of giving you options. The fix is to break the loop by booting from installation media, then either repairing the boot configuration, disabling automatic restart, or restoring the system to a working state.

Why Startup Repair Loops Instead of Fixing

Startup Repair is a Windows recovery tool that runs when the system detects a boot failure. It scans for common issues like missing boot files, corrupted registry hives, or invalid boot configuration data (BCD). When it works, it repairs the problem and reboots normally. When it fails, it should show a message saying it couldn’t repair your PC. But on many systems, it simply restarts and runs again, creating an infinite loop.

This happens for a few reasons. The most common is that the boot configuration data (BCD) is so corrupted that the repair tool cannot read it to even start a repair. Another cause is a failing hard drive or SSD that produces read errors during the scan, causing the repair process to crash and restart. Sometimes a recent Windows update or driver change leaves the system in a state where the repair tool itself cannot load properly. The loop is not a separate bug; it is the system repeatedly trying and failing to boot into the recovery environment.

How Startup Repair Actually Works

When you see the spinning dots and the message “Preparing Automatic Repair,” Windows has already detected a boot failure and is loading the Windows Recovery Environment (WinRE). Startup Repair then performs a series of checks:

• It verifies that all required boot files exist and are readable.
• It checks the BCD store for valid entries pointing to the Windows installation.
• It examines the master boot record (MBR) or GUID partition table (GPT) for integrity.
• It looks for corrupted system files in the Windows directory.

If any check fails, it attempts to fix it automatically. The tool writes a log file at C:\Windows\System32\Logfiles\Srt\SrtTrail.txt that records what it found and what it did. If you can access that file from another bootable environment, it will tell you exactly why the repair failed. The loop occurs when the repair tool itself crashes or when the boot failure is so severe that the tool cannot even write to the disk.

First: Break the Loop with Installation Media

You cannot fix the loop from within the loop. You need to boot from a Windows 10 USB drive or DVD. You can create one on another working PC using the Microsoft Media Creation Tool. Once you have it:

1. Insert the USB drive and restart the computer.
2. Press the key to open the boot menu (usually F12, F11, or Esc) and select the USB drive.
3. Choose your language and click “Next,” then click “Repair your computer” at the bottom-left corner.
4. Select “Troubleshoot” > “Advanced options” to see the full recovery tools.

From this menu, you have several repair options that do not require reinstalling Windows. The most useful are Command Prompt, System Restore, and Startup Repair itself — but you will run them from the USB, which avoids the loop because the repair tool loads from the USB rather than the broken hard drive.

Run Boot Configuration Repairs from Command Prompt

Most infinite loop cases are caused by a corrupted BCD. From the Advanced options menu, open Command Prompt and run these commands in order:

1. bootrec /fixmbr — rewrites the master boot record without touching the partition table.
2. bootrec /fixboot — writes a new boot sector. If you get “Access is denied,” skip this and continue.
3. bootrec /scanos — scans for Windows installations and shows if it finds your OS.
4. bootrec /rebuildbcd — rebuilds the BCD store. When prompted, type Y to add the installation.

After these commands, type exit and restart. If the BCD was the problem, Windows should boot normally. If /fixboot gave an access denied error, your system may use GPT with UEFI firmware, and you may need to use diskpart to assign a drive letter to the EFI system partition and then run bcdboot C:\Windows to rebuild the boot files. This is more advanced, but it is the standard fix for UEFI systems.

Disable Automatic Restart to See the Real Error

Sometimes the loop is not Startup Repair itself but the system restarting during a blue screen or black screen error. Windows has a setting that automatically restarts on system failure, which can hide the actual error code. To disable it from the recovery environment:

1. Open Command Prompt from Advanced options.
2. Type regedit and press Enter.
3. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl.
4. Double-click AutoReboot and change the value from 1 to 0.
5. Close the registry editor and restart.

Now if the system crashes, it will stay on the error screen instead of restarting. The error code or message (like INACCESSIBLE_BOOT_DEVICE or CRITICAL_PROCESS_DIED) will tell you what is actually wrong. A common cause is a driver that fails to load or a hardware component that is failing.

Use System Restore or Reset This PC

If the boot configuration repairs do not work, the next step is to restore the system to a point before the problem started. From Advanced options, select System Restore. If you have a restore point from before the issue, choose it and follow the prompts. This does not affect personal files but will remove recently installed drivers and updates.

If you do not have a restore point, or if System Restore fails, you can use Reset This PC. From the same Advanced options menu, select “Reset this PC” and choose “Keep my files.” This reinstalls Windows while preserving your documents and photos, but it will remove installed applications and drivers. It is a more drastic step but often resolves persistent boot issues that other repairs cannot.

Check for Failing Hardware

If all software repairs fail, the loop may be caused by failing hardware, especially the hard drive or SSD. A drive with bad sectors can cause the repair tool to crash repeatedly. You can check the drive from Command Prompt by running chkdsk /f /r C:, but this may take a long time and may not complete if the drive is failing badly. If you have another computer, you can remove the drive and test it there using the manufacturer’s diagnostic tool. If the drive is failing, you will need to replace it and reinstall Windows from scratch.

Frequently Asked Questions

Will I lose my files if I use these fixes?

Most of the fixes described here — bootrec commands, disabling auto restart, and System Restore — do not delete personal files. Reset This PC with “Keep my files” also preserves your documents, but always back up important data if you can, because any repair can go wrong.

How long should Startup Repair take before I assume it’s looping?

A single Startup Repair pass can take 15 minutes or more on a slow system. If it restarts and immediately begins “Preparing Automatic Repair” again, that is the loop. If it stays on the same screen for over an hour, it is likely hung, and you should force a shutdown and boot from installation media.

Can I fix the loop without a USB drive?

If you can reach the Advanced options menu (by interrupting boot three times or using the Shift+Restart method), you can try the fixes from there. But if the loop restarts before you can select anything, you need installation media to break it.

Why does Startup Repair say it couldn’t repair but then run again?

This usually means the repair tool found a problem it could not fix, but the system still thinks it needs repair, so it restarts the process. The SrtTrail.txt log file contains the specific error, but you need to boot from media to read it.

Is there a way to skip Startup Repair and boot normally?

If the underlying issue is minor, you might try disabling automatic repair by running bcdedit /set recoveryenabled no from Command Prompt. This stops the automatic repair loop, but if the boot issue remains, Windows will still fail to start.

Related

• Remove Remembered Email Address in Gmail
• Share One GPU Between Models: 4 Methods Tested
• Install Ubuntu on Chromebooks: Full Guide