When your PC boots into a black screen with the spinning dots and the dreaded "Preparing Automatic Repair" or "Automatic Repair couldn't repair your PC" message, panic usually sets in. You're locked out of your desktop, your files feel trapped, and standard reboots just cycle you back to the exact same diagnostic loop.
Automatic Repair is built-in Windows diagnostic software designed to fix corrupted boot files, missing registry keys, or damaged system drivers. When it fails, the issue typically stems from a corrupted Boot Configuration Data store, damaged system files, a bad driver installation, or failing storage hardware. Fixing this loop doesn't require an expensive trip to a repair shop or a total data wipe. With a few targeted command-line tools and safe mode interventions, you can bypass the loop and restore normal system boot.
Diagnose the Automatic Repair Failure
Before throwing random fixes at your machine, you need to understand why the repair tool failed. When Automatic Repair reaches its diagnostic screen, clicking "Restart" rarely works because the underlying corruption remains untouched. Instead, you need to access the Windows Recovery Environment.
Click on Advanced options when the Automatic Repair blue screen appears. This opens the gateway to system recovery tools, command prompts, and startup settings. If your PC fails to even reach the Automatic Repair screen and simply reboots infinitely, you will need to create a bootable Windows USB installer using the Microsoft Media Creation Tool on a working computer to access these same recovery options.
Once inside Advanced Options, navigate to Troubleshoot > Advanced options. Here lies your toolkit: Command Prompt, Startup Repair, System Restore, and Startup Settings. Most users make the mistake of clicking Startup Repair again. If the automatic tool already failed, running it a second time yields the same result. You need manual control.
Repair the Boot Configuration Data
Corrupted or missing Boot Configuration Data (BCD) is the single most common trigger for the automatic repair loop. Windows relies on this file to locate the operating system files during startup. If the BCD points to the wrong sector or gets overwritten by a faulty update, your PC gets stuck.
- Open the recovery menu and select Troubleshoot > Advanced options > Command Prompt.
- Type
bootrec /scanosand press Enter. This scans your drives for any installed Windows operating systems. - Type
bootrec /fixmbrand press Enter to write a fresh Master Boot Record to your system partition without overwriting your partition table. - Type
bootrec /fixbootand press Enter to write a new boot sector to the system partition. - Type
bootrec /rebuildbcdand press Enter to scan for operating systems and rebuild the boot configuration store.
If the rebuild command asks you to add the installation to the boot list, type Y or Yes and hit Enter. Once these commands execute successfully, close the command prompt and restart your computer. In many cases, your desktop will load normally.
Check and Repair System Files
If fixing the boot records doesn't work, core system files might be damaged due to an improper shutdown, power outage, or failing sector. Windows includes two powerful utilities designed to scan, verify, and replace damaged operating system files: DISM and SFC.
Open the Command Prompt from the advanced recovery options again and run these tools sequentially.
First, run the Deployment Image Servicing and Management tool to repair the local Windows system image. Type dism /online /cleanup-image /restorehealth and press Enter. Note that if you are running this from the recovery environment offline rather than a live booted desktop, you may need to specify the source image path, but running dism /image:C:\ /cleanup-image /restorehealth (assuming C: is your Windows drive) works for offline repairs.
Second, run the System File Checker. Type sfc /scannow and press Enter. The utility will scan every protected system file and replace corrupted versions with cached copies located in a compressed folder at %WinDir%\System32\dllcache. Let the scan run until it reaches 100 percent. If it finds and repairs corrupted files, restart your PC.
Revert Recent Changes with System Restore or Uninstall Updates
Did the automatic repair loop start right after you installed a new graphics driver, a Windows cumulative update, or sketchy software? If so, the fix is rolling back the offending change.
From the Advanced options menu, select System Restore. Choose an active restore point created before your PC started misbehaving. Follow the prompts to let Windows revert system files, registry keys, and installed programs to that stable timestamp. Your personal documents and media files remain untouched, but recently installed apps or drivers will be uninstalled.
If System Restore isn't available or fails, try removing recent updates. Go back to Advanced options and select Uninstall Updates. You can choose to uninstall the latest quality update or the latest feature update. Feature updates are notorious for triggering boot loops on specific hardware configurations. Removing the latest update often restores instant stability.
Boot Into Safe Mode and Remove Faulty Drivers
If your PC still refuses to boot normally, you need to isolate the problem by starting Windows with a minimal set of drivers and services.
- Navigate to Troubleshoot > Advanced options > Startup Settings and click Restart.
- When your PC reboots and displays a numbered list of options, press
4orF4to Enable Safe Mode. - Once you reach the desktop (it will look sparse and low-resolution), right-click the Start button and open Device Manager.
- Look for yellow exclamation marks next to hardware components, or think about the last device driver you installed.
- Right-click the problematic device—often a GPU driver, network adapter, or external controller—and select Uninstall device.
Reboot your computer normally after removing the bad driver. Windows will load generic drivers, allowing you to download a stable version from the official manufacturer website, such as NVIDIA Drivers or AMD.
Disable Automatic Repair Permanently (As a Last Resort)
If your system runs fine once you bypass the loop, but Windows insists on triggering the diagnostic tool due to a stubborn non-critical error, you can disable the automatic recovery prompt entirely using the command prompt.
Open Command Prompt from recovery or run it as an administrator from inside Windows, then type the following command and press Enter:
bcdedit /set {default} recoveryenabled no
This command turns off the automatic repair trigger. If your PC encounters a legitimate boot failure in the future, it will display a standard Blue Screen of Death with an error code rather than looping through the repair diagnostic screens. Use this option cautiously, as it hides underlying boot warnings.
Frequently Asked Questions
Will fixing the automatic repair loop delete my personal files?
No. Standard troubleshooting methods like rebuilding the BCD, running SFC scans, or using System Restore target system files and boot records. Your personal documents, photos, and apps remain safe. However, always back up critical data when dealing with system instability.
Why does my PC keep looping back to the automatic repair screen?
Windows triggers this loop when it detects three consecutive failed boot attempts. If the underlying cause—such as a corrupted system file, bad sector, or failing drive—isn't resolved, Windows assumes it needs to keep trying to fix itself, trapping you in an infinite cycle.
What should I do if none of the command-line fixes work?
If DISM, SFC, and BCD rebuilds all fail, your partition table might be severely damaged or your storage drive could be failing. You can use the Reset this PC option in the recovery menu, choosing to keep your files, or reinstall Windows fresh using a bootable USB drive.
Can bad RAM cause an automatic repair loop?
Yes. Faulty memory sticks corrupt data as it moves from storage to the CPU, frequently damaging system files during runtime. If you experience random blue screens leading into boot loops, run the Windows Memory Diagnostic tool from the recovery menu.
