The Automatic Repair loop is Windows trying to be helpful and failing at it: your PC can’t boot, so it runs Automatic Repair; the repair can’t fix the problem, so the PC reboots; the boot fails again… and around you go. I’ve seen people stuck in this for days because they keep clicking “Restart” hoping for a different result.
The way out is to stop letting it repair and start fixing the actual problem. That means getting into the recovery environment’s Command Prompt and working the real causes: boot files, disk errors, bad updates, broken drivers. Here’s the full sequence.
A quick warning about what NOT to do: don’t keep clicking “Restart” hoping it’ll fix itself — every loop iteration is another failed boot attempt that changes nothing. And don’t jump to “Reset this PC” as step one; it’s effective but wipes your applications, and most loops are fixed by the far less destructive steps below. Work the list in order and you’ll keep everything. If your loop specifically references the SrtTrail.txt log, our SrtTrail.txt quick-fix guide targets that exact variant.
Why this happens
- Corrupted boot files (BCD): Windows can’t assemble the boot, and Startup Repair can’t rebuild what it can’t parse.
- Disk errors: Bad sectors or file system damage on the boot partition that repair can’t work around.
- Failed Windows update: A half-applied update with inconsistent boot components.
- Incompatible driver: A newly installed driver (often storage or display) that crashes the boot.
- Corrupted registry hives: Damaged SYSTEM hive blocking boot.
- Recently installed software with boot drivers: Disk encryption or backup tools whose drivers crash the boot.
- Failing drive hardware: Physical degradation that makes every repair attempt fail the same way.
How to fix it
Work through these in order.
Fix 1: Break the loop
First, stop the merry-go-round. Disabling the automatic repair trigger doesn’t fix anything by itself — but it converts an infinite loop into a visible error you can actually diagnose, which is the prerequisite for every real fix.
- On the Automatic Repair screen, click Advanced options (not Restart).
- Go to Troubleshoot > Advanced options > Command Prompt.
- Type
bcdedit /set {default} recoveryenabled Noand press Enter. - Type
exitand choose Continue. Windows will now attempt a normal boot and show you the real error instead of looping. Note the stop code or message — it tells you which fix to prioritize.
Fix 2: Boot into Safe Mode
If normal boot shows a blue screen but Safe Mode works, it’s a driver or startup software issue.
- Interrupt boot three times to return to WinRE, then Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 for Safe Mode.
- In Safe Mode, open Device Manager and roll back any recently updated driver, then uninstall recently installed programs.
- Restart normally and test.
Fix 3: Rebuild the BCD and MBR
The core fix for boot-file corruption. These commands rewrite the master boot record, the boot sector, and the boot configuration database — the three structures Windows needs to find and start itself. Run them in order; each builds on the last.
- In WinRE Command Prompt, run
bootrec /fixmbr. - Run
bootrec /fixboot. On “Access is denied”:diskpart>list vol> find the FAT32 EFI partition >sel vol N>assign letter=S:>exit>bcdboot C:\Windows /s S: /f UEFI(verify the Windows drive letter first withdir C:— in WinRE it’s often D:). - Run
bootrec /scanosthenbootrec /rebuildbcd, answering Y. - Restart and test.
Fix 4: Run chkdsk on the system drive
Disk corruption underlies many loops.
- In WinRE Command Prompt, confirm the Windows drive letter (
diskpart>list vol). - Run
chkdsk X: /r(your letter). Let the full scan finish — it can take a long time on big drives. - If it repairs errors, restart and test. If it finds unrecoverable sectors, back up your files now (use
robocopy X:\Users\<you> E:\backup /Eto a USB drive) — the drive may be failing.
Fix 5: Uninstall the latest Windows updates
If the loop started right after an update:
- In WinRE: Troubleshoot > Advanced options > Uninstall Updates.
- Remove the latest quality update first, restart, test.
- If still looping, remove the latest feature update.
- Once booting, pause updates for a couple of weeks to avoid immediate reinstallation of the bad one.
Fix 6: Run offline SFC and DISM
When boot files look fine but Windows still won’t start, the system files themselves are damaged. These commands repair them against the offline Windows image.
- In WinRE Command Prompt:
sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows(your drive letter). - Then
DISM /Image:X:\ /Cleanup-Image /RestoreHealth. - If a stuck update is suspected:
DISM /Image:X:\ /Cleanup-Image /RevertPendingActions. - Restart and test.
Fix 7: System Restore
- In WinRE: Troubleshoot > Advanced options > System Restore.
- Choose a restore point from before the loop began.
- Complete and restart. Files untouched; drivers, updates, and registry roll back.
For background on restore points and when they save you, see using System Restore on Windows 11 .
Fix 8: Reset Windows (keep files), then clean install if needed
The final software option before suspecting hardware. A reset reinstalls Windows fresh while keeping your personal files — you’ll reinstall apps, but the loop will be gone.
- In WinRE: Troubleshoot > Reset this PC > Keep my files > Local reinstall.
- If the reset fails (damaged recovery image), create USB media with the Windows 11 Media Creation Tool on another PC, back up your files from WinRE Command Prompt, and clean-install.
- After any reinstall, install chipset/storage drivers from your manufacturer’s site before letting Windows Update run wild.
Closing
The Automatic Repair loop ends when you stop repairing and start fixing: disable the auto-repair trigger, rebuild the boot data, check the disk, and undo the last change (update or driver). That sequence resolves the large majority of loops without data loss. If the loop returns after a fix, suspect the drive — run the manufacturer’s full diagnostics, because hardware that keeps corrupting boot files will keep producing the same loop no matter how many times you rebuild them. One more tip: after you escape the loop, immediately create a restore point and a recovery USB. Loops are much less scary the second time when you have both ready — and the restore point gives you a one-click undo for whatever caused it.
