Rightek Rescue · Guides · Automatic Repair loop
Windows stuck in an Automatic Repair loop? Here's how to fix it — without losing your files
First, breathe: your files are almost certainly fine. An Automatic Repair loop is a boot problem, not a data problem — Windows just can't get far enough to show you your desktop. This guide covers why it happens and how to fix it, from the manual steps to the one-click way.
What you're seeing
Your PC keeps landing on one of these, over and over:
- “Preparing Automatic Repair” → black screen → restart → repeat
- “Automatic Repair couldn't repair your PC”
- “Your PC did not start correctly”
- A blue Recovery screen with Restart / Advanced options that never actually fixes it
You may also see a stop code like 0xc000021a, 0xc000000f, or 0xc0000034.
Why it happens
Windows runs Automatic Repair after it fails to boot twice in a row. The loop happens when Automatic Repair itself can't fix the underlying cause. The usual culprits:
- A corrupt system registry hive (often after a power loss) —
0xc000021a - A missing or damaged boot file (
winload.efi,ntoskrnl.exe) —0xc000000f - A broken boot configuration (BCD) —
0xc0000034 - A half-finished Windows Update stuck mid-install
- Disk or filesystem corruption that trips the boot process
Fix it yourself — the manual steps
If you're comfortable with a few steps, here's the honest walkthrough:
- Force-stop the loop: hold the power button ~10s to shut down. Do this 2–3 times at the boot logo to trigger the Advanced Startup menu.
- Try Startup Repair: Advanced options → Troubleshoot → Advanced options → Startup Repair. Sometimes it works — but if you're here, it probably already failed.
- Disable automatic restart (Startup Settings) so you can read the actual stop code.
- Command Prompt (from Advanced options), then, depending on the cause:
- Rebuild the boot files:
bootrec /rebuildbcd,bootrec /fixmbr,bootrec /fixboot - Check the disk:
chkdsk C: /f /r - Restore the registry from backup (advanced — a wrong path here can brick the install)
- Rebuild the boot files:
- Last resort: Reset this PC → Keep my files. Sometimes this too gets stuck.
This works — if you know which cause you have and get every command right. Most people don't, which is why the next option exists.
Read the actual error before you fix anything
"Automatic Repair couldn't repair your PC" is not a diagnosis, and the loop hides the real message. Two things are worth reading before you touch anything:
- The repair log. On the failure screen choose Advanced options → View
problem details, or open
C:\Windows\System32\LogFiles\Srt\SrtTrail.txtfrom a Command Prompt. It names the file or component that failed, which turns guesswork into a decision. - The underlying stop code. From Startup Settings, disable automatic restart. The machine will then hold on the blue screen long enough to read it, and the code tells you which of the causes below you actually have.
Which cause do you have?
The loop is a symptom of four quite different faults, and the right repair depends on which:
- 0xc000021a — a corrupt registry hive. Boot repairs will not help; see the 0xc000021a guide.
- 0xc000000f or 0xc0000034 — missing boot files or a damaged BCD. This
is the one
bootrecactually fixes; see "Your PC needs to be repaired". - 0x7B — Windows cannot reach the disk. A storage controller problem, not a boot-file one; see INACCESSIBLE_BOOT_DEVICE.
- No stop code, just the loop — usually a pending update that cannot complete or roll back. Try Uninstall Updates before anything more drastic.
The step most people skip
Advanced options → System Restore. If a restore point exists from before the problem, it reverses the system-side change that caused this without touching your files, and it takes about ten minutes. It is offered in the same menu as everything else and gets overlooked because it sounds too easy.
When the loop is really a failing disk
Automatic Repair runs after two failed boots. A drive that is starting to fail produces exactly that: reads that succeed sometimes and not others. If the machine had been freezing for seconds at a time in the weeks before, or is making any clicking or grinding noise, stop and read the hard-disk guide first. Repair passes on a dying drive are how recoverable data becomes unrecoverable.
Breaking the loop so you can work
If the machine reboots into repair faster than you can use it, you can switch the automatic
attempt off from a Command Prompt with
bcdedit /set {default} recoveryenabled No. That does not fix anything — it
stops Windows retrying, so you get to see the real error and work on the machine. Turn it back on
with Yes once you are done.
⚡ The one-click way: let Rightek Rescue do it
Rescue works through these causes automatically, in the right order, from a rescue USB — no commands, no guesswork. On any working PC: download it, put it on a USB (one click makes it bootable), boot the stuck PC from it, and choose Fix My PC. It finds the cause of the loop and repairs Windows in place. Your files, accounts and programs stay where they are. Not sure what's wrong? It tells you free before it fixes anything.
FAQ
Will I lose my files?
Very unlikely. In an Automatic Repair loop your data is almost always intact — the PC just can't reach it. Rescue repairs the boot/system side and leaves your personal files where they are. Any repair on a damaged drive carries some risk, so copy irreplaceable files off first if you can.
How long does it take?
Making the USB takes a couple of minutes; the repair itself is usually 5–20 minutes depending on the cause.
What if it's actually a hardware problem?
Rescue reads the drive's health data and flags warning signs; if it sees them, it tells you to back up and service the hardware — it won't pretend a dying disk is a software fix.
Do I need a second computer?
Yes — any working PC to download Rescue and make the USB. Since your main PC is stuck, that's expected. Any USB stick 8GB+ works.
Which Windows versions?
Windows 10 and 11. Rescue runs from the USB, outside your broken Windows, so it works even when Windows won't start at all.
How long should I let Automatic Repair run before deciding it is stuck?
Give it up to an hour on a first attempt, particularly on a mechanical drive. Beyond that, if there is no drive activity light flickering, it is not making progress. A genuine repair is doing disk work and it shows.
Where can I see what Automatic Repair actually tried?
In SrtTrail.txt, at C:\Windows\System32\LogFiles\Srt\. You can open it from the Command Prompt in the Recovery Environment. It names the component that failed, which is considerably more useful than the on-screen message.
Does the loop mean my hard drive is dying?
Not usually, but it is one of the possibilities and worth ruling out early. Automatic Repair triggers after two failed boots, and intermittent read failures from a drive that is beginning to fail produce exactly that pattern. Noise, or freezes in the preceding weeks, point that way.