Windows Automatic Repair Loop: Causes and How to Fix It

A Windows Automatic Repair loop usually means Windows can’t boot because of a failed update, corrupted system files, broken boot data, disk errors, or hardware trouble. The safest first fixes are to force Windows Recovery Environment, run Startup Repair, and uninstall the last update before you try anything more invasive. If the loop keeps coming back, the next step is to decide whether you’re dealing with software damage or a failing drive or memory, because boot repairs won’t hold if the hardware is unstable.

What the Automatic Repair loop usually looks like

Symptom

Preparing Automatic Repair
Diagnosing your PC

The exact message varies, but the pattern is the same: Windows starts repair, restarts, and drops you back into the same screen again. You may also see the repair screen after an update, a power loss, or an unexpected shutdown, and Windows never gets as far as the desktop.

Sometimes the machine flashes a blue recovery screen, reboots, and returns to the same place. Other times it reaches Automatic Repair, fails, and offers options like Startup Repair, Advanced options, or Restart. The key sign is repetition: the system keeps trying to fix itself, but never finishes booting.

If you can get to the recovery menus, that is a good sign. It usually means the data on the drive is still reachable, and you can try fixes before you think about reinstalling Windows.

Why Windows gets stuck here

Windows usually falls into this loop because something changed between a working boot and the current failed boot. A bad Windows update can break a driver or a system file. A corrupted boot file can stop Windows from finding the operating system. An interrupted shutdown or power cut can leave the file system in an inconsistent state.

A failing SSD or hard drive can cause the same behavior, especially if Windows keeps repairing the same problem over and over and never stabilizes. Bad RAM can also make repairs fail because files get read or written incorrectly during startup. In plain terms, the loop happens when Windows sees a boot problem, tries to repair it, and then hits the same problem again on the next restart.

The most common software causes are:

• a failed Windows update
• a bad driver update
• corrupted system files
• damaged boot records or boot configuration data
• disk errors after an improper shutdown

The most common hardware causes are:

• a failing SSD or hard drive
• loose or failing storage cables on a desktop
• unstable memory
• power-related damage after an outage or sudden shutdown

Before you start

This applies to Windows 10 and Windows 11 on home and office PCs. You do not need Administrator access to enter the recovery menus, but you do need it once you get into Windows again to undo drivers, updates, or settings changes.

If you can still reach your files, back up anything important before you try deeper repairs. The first safe checks are simple: note whether the problem started after an update, a new driver, a new device, a power cut, or a sudden shutdown, and disconnect any recently added hardware.

If you can reach the blue recovery menu, choose the options under Troubleshoot and Advanced options. You do not need to sign in first.

Try the safest fixes first

Start with the built-in recovery tools. They change the least, they do not wipe personal files, and they often fix the problem if Windows only had a bad update or a startup file issue.

1. Open Startup Repair.

Troubleshoot > Advanced options > Startup Repair

Let Windows run the repair and restart on its own. If it boots normally afterward, the issue was likely a startup file or boot configuration problem. If Startup Repair says it could not repair your PC, move on to the next step instead of repeating it over and over.

2. If Startup Repair fails, remove the last update.

Troubleshoot > Advanced options > Uninstall Updates

Choose the most recent quality update first. If the problem started right after a feature update, remove that instead. This is one of the safest next steps because it rolls back a recent change instead of touching your files. If uninstalling the update does not change the loop, the problem is probably not just the update itself.

3. If the loop began after a new driver or device change, disconnect the new hardware and try again.

If you can get back into Windows later, remove that driver from Device Manager. If nothing new was added before the loop started, skip this step and move on.

If none of these choices changes anything, the problem is probably deeper than a simple bad update, and Command Prompt repairs are the next step.

Use Command Prompt when Startup Repair doesn’t help

Use Command Prompt from the recovery menu when you need to check the disk, repair Windows files, or rebuild boot data. These commands are still conservative compared with a reset, but they can take time and you should type them carefully.

Run these only from Windows Recovery Environment, not from a normal desktop window if Windows is already unstable. If you have an SSD that may be failing, start by copying important files off the drive if you can reach them.

1. Check the disk for file system errors.

chkdsk C: /f /r

This looks for damaged sectors and file system problems on the Windows drive. If Windows is installed on a different letter in recovery mode, use that letter instead. If chkdsk reports and fixes errors, restart and test the boot again. If it finds repeated errors every time, that points more toward storage trouble than a one-time software issue.

2. Repair system files offline.

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

This checks protected Windows files in the offline installation. If it finds corruption and repairs it, reboot and try again. If it says it could not repair some files, that usually means the damage is heavier or the drive is having trouble staying readable.

3. Repair boot records only when the problem looks like boot data damage.

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

These commands help when boot data is corrupted or missing. They are most useful if Windows was working before and then started failing after a crash, failed clone, or partition change. If these commands error out repeatedly, stop and look harder at the disk itself rather than running them in a loop.

If you are not sure which drive letter is Windows in recovery mode, check first.

dir C:\Windows

If that folder is not found, try another letter until you find the Windows folder. Using the wrong drive letter is a common reason these fixes appear to do nothing.

When Safe Mode or System Restore can save the day

If Windows can reach Safe Mode, that usually means the core operating system is still there and a startup driver, service, or app may be the real problem. Safe Mode loads only the basics, which makes it a good place to undo the last change.

To enter Safe Mode from recovery, use the startup settings path.

Troubleshoot > Advanced options > Startup Settings > Restart

After the restart, choose the Safe Mode option that appears on screen. Once you are in Safe Mode, remove the most recent driver, update, or security tool you installed before the loop started. If the issue began right after a printer driver, graphics driver, or antivirus change, that is a strong clue.

System Restore is another low-risk option if restore points are available. It rolls Windows settings and system files back to an earlier state, but usually keeps your personal files.

Troubleshoot > Advanced options > System Restore

Pick a restore point from before the problem began. If System Restore completes and Windows boots again, the bad change was likely software-related. If there are no restore points or it fails partway through, move on to hardware checks or a deeper recovery path.

How to tell if the drive or memory is the real problem

At some point, you need to stop treating the loop like a Windows-only problem. If Startup Repair, update removal, chkdsk, and sfc all fail, the drive or memory starts looking more likely.

Signs that point to storage trouble include:

• the same repair failure every time, even after updates are removed
• very slow access before the loop starts
• clicking or grinding noises from a hard drive
• repeated disk errors in recovery tools
• Windows losing the installation or saying it can’t find files that were there before

Signs that point to RAM trouble include:

• random repair failures that change from one boot to the next
• blue-screen style crashes before the loop started
• errors that move around instead of staying tied to one file or update

The reason this changes the plan is simple: software repairs cannot hold if the device that stores or reads the files is failing. If you suspect a bad SSD or hard drive, the next priority is backing up files, not more boot fixes. If you suspect RAM, the cleanest next step is testing the memory after you regain access or using known-good hardware in a desktop if that is realistic.

If nothing works, what your recovery options really are

If the loop continues after repair tools, Safe Mode, and System Restore, your options narrow to recovery or reinstalling Windows. The order matters because some choices preserve more of your data than others.

1. Try Reset this PC with file retention if the menu offers it.

Troubleshoot > Reset this PC > Keep my files

This reinstalls Windows while trying to keep personal files. It can remove apps and some settings, so treat it as a recovery step, not a full fix for everything. If Keep my files is unavailable or fails, the installation may be too damaged for this route.

2. Back up files from recovery tools if you can still reach the disk.

If Command Prompt or another recovery tool can see your files, copy the most important folders to an external drive before doing anything more aggressive. That may be the only chance to preserve data if the drive is unstable.

A clean install is the point where you should assume apps and many settings will be lost, and you may need to erase the Windows partition during setup. Only choose this after you have backed up what matters.

3. Use a clean install if the repair path keeps failing.

A clean install is the realistic last resort when Windows repair keeps failing, the boot data is too damaged to trust, or the drive has already shown signs of serious corruption. If the disk itself is bad, replacing it first and then installing Windows on the new drive is often the better long-term fix.

Conclusion

If you can still reach the recovery menu, start with Startup Repair, then uninstall the latest update, then move to `chkdsk`, `sfc`, and boot record repair if needed. If those steps keep failing, switch your attention to Safe Mode, System Restore, and your files first, then decide whether the drive or memory needs testing. If the hardware looks healthy and the loop still won’t stop, a reset or clean install is the next step.

Frequently Asked Questions

Will Automatic Repair delete my files?

Usually no. The repair loop itself does not erase personal files, but some recovery actions, like Reset this PC or a clean install, can affect apps and data. Back up important files first if you can reach them.

Should I keep restarting when Automatic Repair fails?

No. Repeated restarts rarely fix the underlying problem and can waste time or stress a failing drive. Move to recovery tools instead.

What if I cannot get into Windows Recovery Environment?

Use a Windows installation USB or recovery media to boot into the same repair environment. From there, you can try the same startup and recovery steps.