The Automatic Repair loop is uniquely frustrating: your laptop shows “Preparing Automatic Repair,” thinks for a while, announces it couldn’t repair your PC, restarts — and does it all again. Forever. The loop itself isn’t the problem; it’s a symptom. Something is preventing Windows from booting, and the automatic tool isn’t equipped to fix it. The manual fixes below are.
Before diving in: your files are almost certainly fine. This is a boot problem, not a data problem. Work through the fixes in order — they go from the quickest wins to the deeper repairs. If your loop shows a specific stop code on the blue screen first, our blue screen troubleshooting guide helps identify it; the loop-breaking steps here apply regardless.
Why this happens
- Corrupt Boot Configuration Data (BCD): The most common cause. The BCD tells Windows how to start; when it’s damaged, every boot attempt fails and triggers the repair loop.
- A failed Windows update: Updates modify boot files. An interrupted or buggy update leaves the boot chain broken — the repair tool can’t fix what the update broke.
- BIOS storage mode changed: A BIOS update or reset flipping between RAID and AHCI makes Windows unable to find its drive, failing every boot identically.
- Failing drive: Bad sectors on boot-critical files cause consistent boot failure. Automatic Repair can’t repair physically damaged storage.
- Corrupted system files: Damage to core Windows files that load early in boot.
- Recently installed drivers: A bad storage or chipset driver installed just before the loop started.
- Fast Startup state corruption: The hybrid-shutdown hibernation file can become corrupt, breaking every “fast” boot in an identical way.
How to fix it
Work through these in order — start inside the recovery environment you’re already landing in.
Fix 1: Break the loop and boot into Safe Mode
First, escape the cycle so you can work.
- On the “Automatic Repair couldn’t repair your PC” screen, click Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 for Safe Mode. If Windows boots in Safe Mode, the problem is a driver or startup program — skip to Fix 6.
- If Safe Mode also fails, return to Advanced options > Command Prompt and continue with Fix 2.
Fix 2: Rebuild the BCD
The core fix for most repair loops.
- From Advanced options, open Command Prompt.
- Run these commands one at a time:
bootrec /fixmbrbootrec /fixbootbootrec /scanosbootrec /rebuildbcd
- If
rebuildbcdreports zero Windows installations found, do the manual rebuild:diskpart→list vol→ find the FAT32 EFI partition,select vol N,assign letter=Z:,exitbcdboot C:\Windows /s Z: /f UEFI(verify your Windows drive letter first withdir C:— in recovery it may be D:)
- Type
exit, choose Continue, and boot.
Fix 3: Disable automatic restart and early-launch anti-malware
Sometimes the loop is sustained by settings rather than corruption.
- From Advanced options > Startup Settings > Restart, press 9 to Disable automatic restart after failure — this at least shows you the real stop code instead of looping.
- Separately, try 8 to Disable driver signature enforcement — if a recent driver is the problem, this can get you booted.
- If either gets you into Windows, immediately update or roll back the suspect driver.
Fix 4: Uninstall the latest update from recovery
If the loop started within a day of an update, this is likely your fix.
- Go to Troubleshoot > Advanced options > Uninstall Updates.
- Try Uninstall the latest quality update first, then restart.
- If still looping, go back and try Uninstall the latest feature update.
- Once booted, pause updates (Settings > Windows Update > Pause updates) and check Microsoft’s support site for known issues with that update.
Fix 5: Run offline SFC and chkdsk
Repair system files and check the disk without needing Windows to boot.
- Open Command Prompt from Advanced options.
- Run
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows(adjust the drive letter to your Windows drive). - Run
chkdsk C: /f /r(same letter adjustment) and let the full scan complete. - Type
exitand choose Continue.
If chkdsk finds many bad sectors, suspect the drive — continue to Fix 7 before celebrating.
Fix 6: Disable Fast Startup and clean-boot
If you can boot into Safe Mode (Fix 1), these steps address the common software causes.
- In Safe Mode, open Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable and untick Turn on fast startup.
- Press Windows + R, type
msconfig, go to the Services tab, tick Hide all Microsoft services, and click Disable all. - In Task Manager > Startup apps, disable everything non-Microsoft.
- Restart normally. If it boots, re-enable services in groups to find the culprit.
Fix 7: Check the drive health
A loop that survives BCD rebuilds and update rollbacks points at hardware.
- Boot your laptop manufacturer’s diagnostics (usually F12 > Diagnostics, or F2 for HP’s hardware diagnostics) and run the full drive test.
- Alternatively, from the recovery Command Prompt, the chkdsk results from Fix 5 tell the story — growing bad-sector counts mean a dying drive.
- If the drive is failing: back up immediately (connect the drive to another PC or boot a live Linux USB), replace the drive, and reinstall Windows. Your files are recoverable as long as you act before total failure.
Fix 8: Reset Windows (keep your files)
The last resort that preserves your data.
- From Advanced options, go to Troubleshoot > Reset this PC.
- Choose Keep my files. This reinstalls Windows, removes apps and settings, but preserves personal files.
- If even this fails, the drive is almost certainly the problem — replace it and do a clean install from USB media created with Microsoft’s Media Creation Tool .
Closing
The Automatic Repair loop feels like a dead end, but it’s really just Windows admitting its automatic tool isn’t enough — the manual BCD rebuild in Fix 2 alone breaks the loop in most cases. The important discipline is fixing the root cause afterward, not just the boot: a loop caused by a bad update will recur when the update reinstalls, and a loop caused by a dying drive will recur until the drive is replaced. Break the loop, then make sure it stays broken. For the related case where Windows boots but immediately blue-screens, our Safe Mode troubleshooting guide picks up where this one leaves off.
