How to Fix the Windows 11 Automatic Repair Loop

Your PC tries to start, flashes “Preparing Automatic Repair,” sits on a black screen for a while, then either lands on “Automatic Repair couldn’t repair your PC” or reboots and does the whole thing again. That’s the automatic repair loop, and it means Windows knows it can’t boot normally but its built-in repair can’t fix the cause either.

The loop itself isn’t the problem — it’s a symptom. Something underneath is broken: the boot configuration, system files, a driver, a recent update, or the disk. The fix is to get into the Windows Recovery Environment (WinRE) and work through the causes in order, from the safe and quick to the more involved. Most loops clear well before you reach the last resort.

What actually causes the loop#

Knowing the likely cause saves you time, because each cause has a different fix.

Get into the Windows Recovery Environment#

Everything starts in WinRE. Windows normally drops you there on its own after the loop, but if it doesn’t, force it.

• Interrupt the boot three times. Power on, and as soon as you see the Windows logo or spinning dots, hold the power button to force off. Do this three times and the fourth boot opens WinRE.
• Shift + Restart, if you can still reach a login or Start menu.
• Boot from Windows 11 install media (a USB you make on another PC with the Media Creation Tool), then choose Repair your computer at the bottom-left.

Once in WinRE, the path you’ll use most is Troubleshoot → Advanced options.

Step 1: Run Startup Repair#

It’s the obvious first move and it does fix a fair share of loops on its own. Go to Advanced options → Startup Repair and let it run. It diagnoses boot files, the BCD, and a few common faults, then either fixes them or tells you it couldn’t.

If it works, great — you’re done. If you get “Automatic Repair couldn’t repair your PC,” don’t read too much into it. Startup Repair only handles a narrow set of problems automatically. The message is just telling you to move to the manual tools.

Step 2: Rebuild the boot files with bootrec#

A broken or missing BCD is one of the most common reasons for the loop, and bootrec is the tool for it. Open Advanced options → Command Prompt and run these in order:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

/fixmbr and /fixboot repair the master boot record and boot sector. /scanos looks for Windows installations, and /rebuildbcd rebuilds the boot configuration store. When /rebuildbcd finds an installation, it asks to add it to the boot list — type Y and press Enter.

If the BCD is stubborn, fully rebuilding it sometimes works where a plain /rebuildbcd doesn’t:

bcdedit /export C:\bcd_backup
attrib C:\boot\bcd -h -r -s
ren C:\boot\bcd bcd.old
bootrec /rebuildbcd

Step 3: Run SFC and DISM offline#

If the boot files are fine but Windows still won’t start, corrupted system files are the next suspect. You can run System File Checker and DISM from the recovery command prompt, but pointed at the offline installation rather than the recovery environment.

First, confirm the drive letter. WinRE frequently mounts your Windows install as D: or another letter, not C:. Check before you run anything:

diskpart
list vol
exit

Look for the volume that holds \Windows — its size and label usually give it away. Use that letter below (this example assumes Windows is on C:):

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

DISM /Image:C:\ /Cleanup-Image /RestoreHealth

sfc checks and repairs protected system files. DISM /RestoreHealth repairs the component store that SFC pulls its known-good files from, so if SFC can’t fix everything, run DISM and then SFC again. Offline DISM needs a source for clean files — if it can’t find one, point it at a mounted install image with /Source:wim:D:\sources\install.wim:1 /LimitAccess.

While you’re here, a quick disk check rules out file-system damage:

chkdsk C: /f /r

Step 4: Disable automatic repair to see the real error#

This step doesn’t fix anything by itself, but it’s the one that breaks you out of the loop so you can actually read what’s wrong. When you disable Automatic Repair, Windows stops silently rebooting into it and instead shows the real boot failure — often a stop code that points straight at the cause, like a specific driver.

From the recovery command prompt:

bcdedit /set {default} recoveryenabled No

Reboot. Instead of looping, you’ll either boot through or hit a blue screen with a named error. Note the stop code or failing file — that’s your lead. Once you’ve fixed the underlying issue, turn the feature back on:

bcdedit /set {default} recoveryenabled Yes

If the error names a specific driver, you can often rename or disable that driver file from the recovery command prompt to get a one-time boot, then fix it properly from inside Windows.

Step 5: Roll back with System Restore#

If the loop started right after an update, a driver install, or new software, System Restore is the cleanest fix — it rewinds system files and settings to a restore point without touching your documents.

Go to Advanced options → System Restore (or run rstrui from the command prompt), pick a restore point from before the trouble started, and let it run.

If a single update is the culprit and you’d rather target it directly, you can remove the most recent quality or feature update from Advanced options → Uninstall Updates.

Last resort: Reset this PC#

When the boot files are rebuilt, system files check out, there’s no restore point, and it still loops, the install is too damaged to repair in place. Reset this PC reinstalls Windows while letting you keep personal files.

Go to Troubleshoot → Reset this PC → Keep my files. You’ll choose between a cloud download (pulls a fresh copy of Windows from Microsoft) and a local reinstall (rebuilds from the files already on the device). If the loop was caused by corrupted system files, pick cloud download — a local reinstall may just put the same damaged files back.

Keep my files removes your installed apps and resets settings, but keeps documents, photos, and the like. If even Reset fails to start, back up from WinRE and do a clean install from your Windows 11 USB. For a deeper look at what Reset keeps versus removes, see how to reset Windows 11 without losing files.

A sensible order to work in#

You don’t need every step — you stop at the one that works. But the order matters, because the early steps are quick and safe and the later ones are slower or more disruptive.

1. Startup Repair — let Windows try the automatic fix.
2. bootrec — rebuild the BCD and boot files (most loops end here).
3. SFC / DISM offline — repair corrupted system files; add chkdsk if you suspect the disk.
4. Disable auto-repair — surface the real error if you’re still stuck.
5. System Restore — roll back a bad update or driver.
6. Reset this PC (Keep my files) — last resort before a clean install.

A lot of these problems trace back to a botched update, so if your trouble began mid-update it’s worth knowing how to fix Windows Update when it’s stuck too. And if SFC and DISM are doing the heavy lifting, the full DISM and SFC repair walkthrough covers the source-file and component-store details in more depth.

Wrapping up#

The automatic repair loop looks alarming but it’s usually a boot or system-file problem with a known fix. Get into WinRE, try Startup Repair, then rebuild the boot files with bootrec — that combination clears the majority of cases. If it persists, repair system files offline with SFC and DISM, disable auto-repair to read the real error, and roll back with System Restore. Reset this PC is the safety net, and Keep my files means it doesn’t have to cost you your data.