Why is my PC stuck in an Automatic Repair loop?
Preparing Automatic Repair, then a blue screen saying it could not repair your PC, then round again. What the loop actually means, why the repair keeps failing, and the order to try things in so you do not lose the files.
- Difficulty
- intermediate
- Time
- 45 min
- Read
- 6 min
- Safety
- caution
Short answer
The loop is not the fault — it is Windows reacting to a fault it cannot name, usually a corrupted boot record, a bad update, or a drive that is starting to fail. From the blue screen choose Advanced options, then Troubleshoot, then Startup Settings, and boot into safe mode. If safe mode works, the hardware is fine and you are looking for a recent change. If safe mode also loops, suspect the drive, and get your files off before doing anything else.
Automatic Repair runs when Windows fails to start twice in a row. It is meant to be a safety net, and when it works nobody ever sees it. What people see is the failure case: the repair runs, finds something it cannot fix, restarts, fails to start again, and triggers itself once more. The loop is therefore a symptom of an underlying fault that has not been identified, and hammering the power button will not identify it either. What breaks the loop is getting into the recovery menu behind that screen, which is available the whole time and which most people never click into because the screen looks like a dead end.
Safety
Step by step
- Get into the recovery menu rather than restarting again.On the blue "Automatic Repair could not repair your PC" screen, choose Advanced options. That is the recovery environment, and everything useful lives behind it. If the machine is looping before that screen appears, hold the power button to force it off during the manufacturer logo, three times in a row — Windows treats three failed starts as a request for recovery.
- Unplug everything except the power and the screen.External drives, USB sticks, docks, card readers, printers, phones. A machine that tries to boot from an attached USB stick, or that is held up by a device that has failed, produces exactly this loop. This test costs nothing and resolves a meaningful share of cases.
- Try safe mode, and treat the answer as the fork in the road.Troubleshoot, Advanced options, Startup Settings, Restart, then press 4 or 5. Safe mode loads a minimal driver set. Working safe mode means the drive, the boot record and the core system are all intact, and something loaded afterwards is the problem. A machine that cannot reach safe mode either has a hardware or a boot-record fault, and that is a different guide.
- If safe mode works, undo the most recent change.System Restore, from the same Advanced options menu, rolls system files and drivers back to a point before the problem without touching your documents. Failing that, Uninstall Updates offers to remove the most recent quality or feature update. Both are reversible and neither deletes personal files.
- Check the drive's health before repairing anything on it.From Advanced options open Command Prompt and run a disk check on the Windows volume. Repeated boot corruption on a machine that has not been dropped or interrupted usually means the drive itself is going. Repairing the boot record on a dying drive buys days, not months.
- Repair the boot record only once you have ruled out the drive.The recovery Command Prompt has the tools to rebuild the boot configuration. This is the correct fix after a failed update, a botched partition change, or a second operating system being removed. It does not touch your documents, but it will not survive a failing drive.
- Get the files off before considering a reset.If you have reached the point where reset or reinstall is on the table, stop and copy your documents out first. The recovery Command Prompt can copy files to a USB stick, and pulling the drive out and reading it in another machine is the more reliable route. The catalogue's guide on recovering files from a dead computer covers both.
- Reset last, and read which reset you are choosing.Reset this PC with Keep my files reinstalls Windows and removes installed programs while leaving documents. Remove everything does what it says. Neither is a repair in any meaningful sense — they are a rebuild, and they cost you a day of reinstalling software.
Common mistakes
- Repeatedly restarting in the hope it clears — Each failed start is another unclean shutdown, and unclean shutdowns are one of the things that corrupt a boot record in the first place. The loop does not wear itself out.
- Choosing Reset this PC as the first thing on the menu — It is the top option and the most destructive one that people actually click. System Restore and Uninstall Updates sit two menus deeper, are reversible, and fix the common causes.
- Searching for a tool that promises to fix boot problems automatically — This is one of the most heavily targeted search terms for junkware and outright malware. Everything a home user needs is already inside the recovery menu on the screen in front of them.
If it doesn't work
The loop started immediately after a Windows update
Cause: A failed or partially applied update — Fix: Uninstall the latest quality update from Advanced options. This is the single most common trigger and the fix is built into the recovery menu specifically because Microsoft expects it.
It loops even with a bootable USB stick attached and selected
Cause: Firmware boot order, or a drive the firmware can no longer see — Fix: Go into the firmware setup screen and check whether the internal drive is listed at all. A drive that has vanished from the firmware list is a hardware fault, not a Windows one.
Safe mode works perfectly, normal mode loops
Cause: A driver or a startup program — Fix: In safe mode, disable non-Microsoft startup services and drivers a group at a time, restarting between each. Graphics and storage drivers are the usual culprits.
It began after adding or removing a second drive
Cause: The boot configuration points at a drive that has moved or gone — Fix: Put the drive back if you can, boot successfully, and then remove it properly. If not, rebuild the boot configuration from the recovery Command Prompt.
Clicking or grinding from the machine as it tries
Cause: A mechanical drive failing — Fix: Stop trying to repair it. Every additional attempt is time the drive may not have. The catalogue's guide on drive failure warning signs covers what to do next, and the answer is recovery, not repair.
It only loops on battery, or only when plugged in
Cause: Power, not software — Fix: A machine that starts reliably on one power source and not the other has a charging or battery fault. Automatic Repair is reacting to interrupted starts rather than causing them.
Questions people ask
Will I lose my files?
Not from the loop itself, and not from safe mode, System Restore, Uninstall Updates or a boot record rebuild — none of those touch documents. You lose files by choosing a reset or a reinstall, or by the drive itself failing. That is why the order in this guide puts the reversible options first and getting your files off before the destructive ones.
How long should I let Automatic Repair run before deciding it is stuck?
Give it an hour on a mechanical drive and half that on an SSD before assuming it has hung. Disk checking on a large, slow, nearly-full drive genuinely takes a long time and looks identical to a freeze. If the drive activity light is still flickering, it is doing something.
Can I stop Windows trying Automatic Repair at all?
There is a command in the recovery environment that disables the automatic recovery attempt, which is occasionally useful because it lets the real error message appear instead. It is a diagnostic step rather than a fix — turning off the smoke alarm does not put out the fire.
The recovery screen asks for a BitLocker key I have never seen
The drive is encrypted, and you cannot get past this without the key. It lives in the Microsoft account the machine was set up with, or with your workplace IT if it is a work laptop. The catalogue has a dedicated guide on finding a BitLocker recovery key, and there is no way around it — that is the point of encryption.