How to Fix Windows Stuck in the Automatic Repair Loop
Published 2026-10-16 · Marion Remote Fix
Your Windows computer is stuck in an endless loop of attempting Automatic Repair and failing. The screen shows Preparing Automatic Repair, followed by Diagnosing Your PC, and then a blue screen stating Automatic Repair could not repair your PC. When you click Restart, the entire cycle repeats — boot attempt, Preparing Automatic Repair, diagnosis, failure, restart. The computer never reaches the Windows desktop. This loop can continue indefinitely, making the computer unusable. The Automatic Repair loop is caused by corrupted system files, a failed Windows update, boot configuration data (BCD) corruption, a damaged Windows registry, a failing hard drive or SSD, or recently installed software or drivers that prevent normal startup.
Access Advanced Options
To fix the repair loop, you need to reach the Advanced Options menu instead of letting the loop continue:
- When the blue Automatic Repair screen appears (the one that says Automatic Repair could not repair your PC), click Advanced Options instead of Restart
- This opens the Windows Recovery Environment with several repair tools. If the screen cycles too fast and you cannot click Advanced Options, try this: during the boot process, press and hold the power button to force shut down. Do this three times in a row — on the fourth attempt, Windows should enter the Recovery Environment automatically
- If you cannot access Advanced Options at all, you need a Windows installation USB. Create one on another working computer using the Microsoft Media Creation Tool, boot the stuck computer from the USB, select Repair Your Computer, and you will reach the same Advanced Options menu
Startup Repair
- From Advanced Options, select Troubleshoot, then Advanced Options, then Startup Repair
- Windows attempts to diagnose and fix startup problems automatically. This process checks the boot configuration, system files, and registry for issues it can repair
- If Startup Repair succeeds, the computer will restart normally. If it fails (which is common when the Automatic Repair loop has already tried this), continue to the next methods
Boot into Safe Mode
Safe Mode loads Windows with minimal drivers and services, which can bypass the problem causing the repair loop:
- From Advanced Options, select Troubleshoot, Advanced Options, Startup Settings, then Restart
- After restart, press F5 to select Safe Mode with Networking (or F4 for basic Safe Mode)
- If Windows boots into Safe Mode successfully, the problem is likely a recently installed driver, application, or update. In Safe Mode:
- Uninstall recent updates: Settings, Windows Update, Update History, Uninstall Updates. Remove the most recent update that was installed before the loop started
- Uninstall recent software: Settings, Apps, Installed Apps. Sort by install date and remove anything installed just before the problem began
- Roll back a driver: Open Device Manager, find any device with a recently updated driver (display adapter is the most common culprit), right-click it, Properties, Driver tab, Roll Back Driver
- Disable fast startup: Control Panel, Power Options, Choose What the Power Buttons Do, Change Settings That Are Currently Unavailable, uncheck Turn on Fast Startup. Fast startup saves a partial system state at shutdown, and if that saved state is corrupted, it causes the repair loop on every boot
Command Prompt repairs
From Advanced Options, select Command Prompt for manual repair tools:
Fix boot configuration
- Run these commands to rebuild the boot configuration data:
- bootrec /fixmbr — writes a new master boot record
- bootrec /fixboot — writes a new boot sector. If this returns "Access is denied," run: bcdedit /set {default} bootmenupolicy legacy — first, then retry
- bootrec /rebuildbcd — scans for Windows installations and rebuilds the boot configuration. If it finds a Windows installation and asks to add it, type Y and press Enter
System File Checker
- Run: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows — this scans and repairs corrupted Windows system files. The /offbootdir and /offwindir flags tell SFC to scan the offline Windows installation rather than the recovery environment
- If SFC finds corruption it cannot fix, run DISM first: dism /image:C:\ /cleanup-image /restorehealth — then run SFC again
- Note: in the recovery command prompt, your Windows drive may not be C: — it could be D: or another letter. Run dir C:\ to check if Windows is on that drive. If not, try dir D:\, dir E:\, etc. until you find the drive containing the Windows folder
Check disk integrity
- Run: chkdsk C: /r — this checks the file system for errors and scans for bad sectors. If the hard drive or SSD has file system corruption or bad sectors causing the repair loop, chkdsk can repair the file system damage. This scan can take 30 minutes to several hours depending on drive size
- If chkdsk reports a large number of bad sectors, the drive is physically failing and needs replacement. Data recovery should be the priority before the drive fails completely
Disable Automatic Repair
If nothing else works and you need to stop the loop to try other approaches, you can disable Automatic Repair itself:
- From the Command Prompt in the Recovery Environment, run: bcdedit /set {current} recoveryenabled No
- This prevents Windows from entering the Automatic Repair loop on the next boot. Instead, Windows will either boot normally (if the underlying problem resolves itself) or show a different error that provides more specific information about what is failing
- After diagnosing and fixing the problem, re-enable Automatic Repair with: bcdedit /set {current} recoveryenabled Yes
System Restore
- From Advanced Options, select System Restore
- Windows shows available restore points — snapshots of the system taken before major changes (updates, software installs, driver changes). Select a restore point from before the problem started
- System Restore reverts system files, registry, and installed programs to the state at that restore point. It does not delete personal files (documents, photos, etc.)
- If no restore points are available (or if System Restore was disabled), this option will not work. Some systems have System Restore disabled by default, especially on computers with small SSDs where the restore point storage space was not allocated
Reset Windows (keep files)
If none of the above fixes work:
- From Advanced Options, select Troubleshoot, then Reset This PC, then Keep My Files
- This reinstalls Windows while preserving your personal files (Desktop, Documents, Photos, etc.). However, all installed applications are removed and Windows settings are reset to defaults. You will need to reinstall your programs after the reset
- The Reset process can use either local recovery files (already on the drive) or Cloud Download (downloads a fresh Windows image from Microsoft, which requires network access). Cloud Download is more reliable because it uses a known-good Windows image rather than potentially corrupted local recovery files
Hardware causes
- Failing hard drive or SSD: If the repair loop started without any software changes (no updates, no new software, no driver changes), the storage drive may be failing. Bad sectors or a degrading SSD can corrupt system files randomly, causing boot failures that repair tools cannot permanently fix because the drive continues to corrupt data
- RAM problems: Faulty RAM can corrupt data during Windows startup, causing random file corruption that triggers the repair loop. From Advanced Options, Command Prompt, run: mdsched.exe to schedule a memory diagnostic on the next boot. Or test RAM with a bootable USB running MemTest86
- Recent hardware changes: If you recently added or changed hardware (new RAM, new drive, new GPU), remove the new hardware and test. Incompatible hardware can cause boot failures that Windows interprets as needing repair
Automatic Repair loop fix in Marion
If your Windows computer is stuck in the Automatic Repair loop and the steps above did not resolve it, Marion Remote Fix can boot your computer into the recovery environment remotely, diagnose the specific cause of the boot failure, repair corrupted system files and boot configuration, and get your computer starting normally again without data loss.