Windows 11 Stuck in an "Automatic Repair" Loop? Here's How to Break It

You turn on your PC and instead of your desktop you get a blue screen that says "Automatic Repair couldn't repair your PC," or it sits forever on "Preparing Automatic Repair" and "Diagnosing your PC," restarts itself, and lands right back on the same message. It feels like the computer is dead. In almost every case it isn't, and neither are your files — Windows just tried to start, hit a problem, and handed control to its own built-in repair tool, which then got stuck. The job now is to reach the recovery menu behind that screen and work through the fixes from safest to last resort.

First, know what this is and isn't, because it changes what you do. A repair loop means the computer powers on, lights up, and reaches Windows' recovery layer — that's different from a laptop that won't turn on or show anything at all (that's a power/display problem — see our triage post) and different from a blue screen with a stop code that flashes by and reboots (that's a crash — we cover those separately). Here, Windows is awake; it just can't finish starting. That's a good sign, and usually a fixable one.

Before you touch anything: give it one chance, then unplug the extras

Two quick things rule out the easy causes. First, if it's sitting on "Preparing Automatic Repair," let it actually run once — a real repair or a pending update can take a while, so give it a good 20 to 30 minutes before you decide it's truly stuck. If the same screen keeps cycling back after several restarts, then it's a genuine loop.

Second, shut the PC fully off (hold the power button about 10 seconds), then unplug everything that isn't essential — USB flash drives, an external hard drive, a printer, a memory card still in the reader, a second monitor, a phone you left charging. A stray device or a leftover USB stick is one of the most common reasons a computer won't finish booting, because it tries to start from the wrong drive. Leave only the power cable, and on a desktop the keyboard, mouse, and one monitor. Turn it back on and see if it boots normally.

How to reach the recovery menu

Most of the time the repair screen offers an "Advanced options" button — that's your way in. If it doesn't, or you only get the spinning loop, you can force the recovery environment: turn the PC on, and the moment you see the Windows logo or spinning dots, press and hold the power button until it switches off. Do that two or three times in a row, and on the next start Windows gives up trying to boot normally and opens the recovery menu itself. (Some laptops have a shortcut instead — many ASUS models, for example, hold F9 while pressing power; HP, Dell, and Lenovo each have their own key — but the interrupt-the-boot method works on virtually any PC.)

One important warning before you run any repair: if your drive is encrypted with BitLocker — common on newer laptops and most work machines — the recovery tools will ask for your 48-digit BitLocker recovery key before they'll do anything. Find it first. It's saved to your Microsoft account at account.microsoft.com/devices (sign in from your phone or another computer and look under the device for "BitLocker recovery keys"), or it may be on a printout or in a work IT system. Without it you can be locked out even though nothing is really broken — we explain that trap in our BitLocker article.

Work through the menu in order — stop the moment you're back in

From the recovery menu, choose Troubleshoot > Advanced options. You'll see a row of tools; try them roughly in this order, and stop as soon as one gets you back to your desktop. Start with Startup Repair. It scans for the usual startup culprits — missing or damaged system files, a corrupted boot configuration (BCD), a damaged master boot record, a bad driver — and tries to fix them automatically. It's the safest option, it touches none of your files, and on a classic repair loop it's often all you need. If it says it couldn't fix the problem, that's not the end; just move to the next tool.

Next try Safe Mode. Choose Startup Settings > Restart, then press 4 (or 5 for Safe Mode with Networking). Safe Mode loads Windows with only the bare-minimum drivers, and very often a machine that loops on a normal boot will start fine here — which both tells you the hardware is OK and gives you a working desktop to fix things from (uninstall a driver or program you just added, create a backup of your files, run a virus scan). If you can reach Safe Mode but not a normal boot, the cause is software, not a dying computer.

If those don't do it, try System Restore (Advanced options > System Restore). If your PC had restore points turned on, this rolls Windows' system files and settings back to a date when it worked — before the bad update, driver, or program — without deleting your personal documents and photos. And if the trouble started right after a Windows update, use Uninstall Updates (Advanced options > Uninstall Updates) and remove the most recent quality update; a botched update is a classic cause of a sudden repair loop, and pulling it often fixes it cleanly.

For the technically comfortable: the Command Prompt fixes

If Startup Repair didn't work and you're comfortable typing commands, the Command Prompt (Advanced options > Command Prompt) can rebuild the boot files by hand. The main one is bootrec /rebuildbcd, which scans for Windows installations and rebuilds the boot menu; the full set Microsoft documents is bootrec /fixmbr, then bootrec /fixboot, then bootrec /scanos, then bootrec /rebuildbcd. On many modern UEFI laptops bootrec /fixboot returns "Access is denied" — that's a known quirk of how those drives are set up, not something to force past, and it's a fair point to hand the machine to someone who does this often.

You can also check the disk and system files from here, but with one catch that trips people up: in the recovery environment the drive Windows actually lives on is frequently labeled D: (or another letter), not C:. Type bcdedit and look at the "osdevice" line to see the real letter, then run, for that letter, chkdsk /f D: (checks the disk for errors), sfc /scannow /offbootdir=D:\ /offwindir=D:\windows (repairs system files offline), and dism /image:D:\ /cleanup-image /restorehealth (repairs the underlying Windows image). Honestly, for most people this is the point to stop and get help rather than guess at drive letters — a wrong command here wastes time, and Startup Repair, Safe Mode, and System Restore already cover the great majority of repair loops.

The last resort — and why a backup matters here

If nothing above works, the final option in the menu is Reset this PC (Troubleshoot > Reset this PC). It reinstalls Windows fresh. "Keep my files" preserves your personal documents and photos but removes your installed programs and most settings (so you'll reinstall your apps afterward); "Remove everything" wipes the drive completely — that's the choice for selling or giving the computer away, not for fixing your own. A reset almost always ends a repair loop because it lays down a clean copy of Windows, but it's a bigger step than the targeted fixes, which is exactly why you try those first.

This is also the moment a backup proves its worth. If your files are backed up, a reset or even a full wipe is no big deal — you restore and move on. If they're not and the drive itself is failing, the data may still be recoverable, but that's a careful job best not attempted by repeatedly forcing a struggling drive to boot. If irreplaceable files are on a machine that won't start, the safest move is to stop power-cycling it and have the drive pulled and read on healthy hardware. (Our backup guide explains how to avoid ever being in this spot again.)

Stuck in the loop and not sure which step is safe?

A repair loop is one of those problems where the right fix is usually quick and the wrong move can make things worse — forcing a failing drive to boot over and over, or running command-line repairs on the wrong drive letter, can turn a recoverable situation into a data-recovery job. If you've worked through Startup Repair, Safe Mode, and System Restore and you're still stuck, or you hit the BitLocker key wall, or there are files on there you can't lose, that's the time to stop guessing. We diagnose boot failures and repair loops every week — we'll get you back into Windows if it can be fixed in place, recover your files first if the drive is the problem, and tell you honestly which it is. We're local across Southern California and the Coachella Valley, onsite or by remote support once the machine is back on its feet.