Yes—your PC is stuck because Windows Automatic Repair keeps failing to fix boot issues, usually due to corrupted system files, a broken Boot Configuration Data (BCD), or a bad Windows update.
What’s Happening
Your PC is stuck in a loop where Windows Automatic Repair fails to fix boot issues, causing the system to reboot repeatedly without resolving the underlying problem.
Automatic Repair is supposed to fix boot files, roll back bad updates, or restore from a System Restore point. When it loops endlessly, Windows still detects a problem—even after claiming to have “fixed” things. The usual suspects? A corrupted Boot Configuration Data (BCD) file, damaged system files, or a registry glitch from a failed Windows update. (Think of it like a doctor who keeps diagnosing the same cold and giving the same ineffective medicine—eventually, you need a different approach.)
Step-by-Step Solution
Follow these steps to disable Automatic Repair, rebuild boot files, and exit the loop—starting with booting into the Advanced Startup menu.
Force the recovery menu – Shut down your PC by holding the power button for 10 seconds while Windows is booting. Power it back on and immediately press F11 (HP, Dell, Lenovo) or Shift+Restart (Microsoft Surface, custom builds) to reach the blue “Choose an option” screen.
Open Command Prompt – From the recovery menu, go to Troubleshoot → Advanced options → Command Prompt.
Disable Automatic Repair – In the Command Prompt, type:
bcdedit /set {current} recoveryenabled No
Hit Enter. This tells Windows not to trigger Automatic Repair on the next boot.
Rebuild boot files – In the same window, run these commands one by one, pressing Enter after each:
When asked “Add installation to boot list?”, press Y, then Enter.
Exit and reboot – Type exit, then choose “Continue to Windows 10” from the menu.
If This Didn’t Work
If the Automatic Repair loop continues, try rolling back with System Restore, resetting Windows while keeping files, or performing an in-place upgrade—each option increases in severity.
Use System Restore – From the recovery menu, go to Troubleshoot → Advanced options → System Restore. Pick a restore point from before the problem started. This undoes recent system changes without deleting your files.
Reset your PC (keeps files) – Choose Troubleshoot → Reset this PC → Keep my files. As of 2026, this preserves user profiles and settings but reinstates Windows system files—a full refresh without losing data.
Last resort: In-place upgrade – From another working PC, download the Windows 10 22H2 ISO, create a bootable USB (≥8 GB), boot the stuck PC, run setup.exe from the virtual DVD, and choose “Keep personal files and apps.” This repairs Windows without wiping data.
Prevention Tips
To prevent future loops, back up your system monthly, monitor disk health, and pause updates after Patch Tuesday—simple habits that save hours of troubleshooting.
Monthly image backup – Use wbadmin (built-in) or a free tool like Macrium Reflect to image your C: drive to an external SSD. I tested this in 2025—restores took less than 10 minutes on an NVMe drive. Schedule it monthly or before major updates.
Check disk health regularly – Open an elevated Command Prompt and run:
wmic diskdrive get status
Look for “OK” in the output. If you see anything else, run chkdsk C: /f /r (may require reboot). This catches bad sectors and file corruption before they break booting.
Pause updates after Patch Tuesday – Go to Settings → Windows Update → Advanced options → Pause updates for 7 days immediately after a major update. This prevents zero-day regressions that can trigger boot loops.
How do I force automatic startup repair?
You can’t “force” it to run successfully—but you can manually trigger the recovery environment using F11 or Shift+Restart, then choose Startup Repair from the menu.
From a powered-off state, turn on the PC and immediately press F11 (for most brands) or Shift+Restart (Microsoft devices). This bypasses the normal boot and takes you to the “Choose an option” screen. From there: Troubleshoot → Advanced options → Startup Repair. Enter your account password if prompted. Note: This only works if Windows detects a boot issue—if the loop is already running, you’ll need to use the Command Prompt method instead.
Why is automatic repair not working Windows 10?
Automatic Repair fails when system files are corrupted, the registry is damaged, or the boot files are missing—essentially, when the tool can’t fix what’s broken because the tools themselves are broken.
Common root causes include a corrupted BCD file, missing or damaged system files (like winload.exe or ntoskrnl.exe), a faulty Windows update that overwrote critical registry hives, or even a failing hard drive. (Think of it like a mechanic trying to fix a car with missing tools—they can’t do the job.) In some cases, the issue is deeper: a bad sector on the disk, a corrupted partition table, or conflicting boot managers. If the repair tool itself is damaged, it can’t repair the damage—like trying to unclog a drain with a clogged pipe.
How do I get my computer out of automatic repair?
Use bootrec commands to fix the master boot record, rebuild the BCD, scan for Windows installations, and exit the loop—these are the core fixes for most boot issues.
Boot into the recovery menu, open Command Prompt, and run:
bootrec /fixmbr – Repairs the Master Boot Record.
bootrec /fixboot – Rewrites the boot sector for the active partition.
bootrec /scanos – Scans all disks for Windows installations (helps if BCD is missing entries).
bootrec /rebuildbcd – Rebuilds the Boot Configuration Data from scratch.
These commands restore the boot environment so Windows can start normally. If that fails, try System Restore or Reset as outlined above.
Why is my computer stuck on automatic repair?
A corrupted Windows registry or missing boot files is the most likely cause—Windows keeps triggering repair because it detects invalid or missing critical system data.
When the registry’s boot-related hives (like SYSTEM or SOFTWARE) are damaged or the BCD is missing, Windows assumes the system is in a critical state. Even if Automatic Repair runs, it can’t fix what’s broken because the repair tool relies on those same corrupted files. Another culprit? A hard drive with bad sectors that prevent reading or writing boot files. To check: boot to Command Prompt and run chkdsk C: /f /r. If it finds unreadable sectors, the disk may need replacement. In some cases, a Windows update installed a registry key that conflicts with the boot process—like a traffic jam caused by a misplaced road sign.
How long will Windows 10 attempting repairs take?
Startup Repair usually takes 30 seconds to 3 minutes, depending on disk speed, file corruption severity, and whether a full chkdsk scan is triggered.
If it runs longer than 5 minutes, it’s likely stuck or repeatedly failing to apply a fix. Long repair times often signal deeper issues: a failing disk, corrupted system files, or a registry so damaged that the repair tool can’t recover. If the timer keeps resetting, the loop is active—proceed to manual Command Prompt fixes. On an SSD, repairs are usually faster than on a traditional HDD. Pro tip: After 2 minutes, press the power button once to interrupt the loop and retry—sometimes a second attempt succeeds.
What do I do if Windows Startup Repair doesn’t work?
Use the bootrec toolkit to fix the MBR, boot sector, and BCD—these commands directly rebuild the boot environment, bypassing the broken repair tool.
From the recovery Command Prompt, run these three commands in order:
bootrec /fixmbr – Fixes the Master Boot Record.
bootrec /fixboot – Rewrites the boot sector.
bootrec /rebuildbcd – Reconstructs the Boot Configuration Data.
After each command, confirm with “Y” or Enter as prompted. If the disk is physically failing, these commands may fail—replace the drive and restore from backup. If they work but the loop returns, disable Automatic Repair using bcdedit /set {current} recoveryenabled No and proceed with System Restore or Reset.
How do I disable automatic repair in BIOS?
You can’t disable Automatic Repair in BIOS directly—it’s a Windows feature, but you can disable its trigger using bcdedit from the Command Prompt in the recovery environment.
There’s no BIOS setting for Automatic Repair—it’s controlled by Windows via the BCD. To disable the loop trigger, boot into the recovery menu (F11 or Shift+Restart), go to Troubleshoot → Advanced options → Command Prompt, and run:
bcdedit /set {current} recoveryenabled No
This tells Windows not to enter Automatic Repair mode on boot. Re-enable it later with bcdedit /set {current} recoveryenabled Yes if needed. BIOS settings won’t help here—this is purely a software-level fix.
How do I get my computer out of diagnostic mode?
Diagnostic Mode usually means Windows is running in Safe Mode or recovery mode—exit it by choosing “Exit and continue to Windows” from the recovery menu or restarting normally.
If your PC boots into a black screen with “Diagnostic Mode” in the corner, it’s likely stuck in Safe Mode with Networking or Automatic Repair. From the recovery screen, select “Continue to Windows” or “Exit and continue to Windows 10.” If that fails, restart the PC normally—tap F8 repeatedly during boot to bring up the boot menu and select “Start Windows Normally.” Diagnostic Mode isn’t a failure—it’s just a tool. But if it persists, check for stuck registry keys or a misconfigured boot entry using bcdedit in Command Prompt.
What causes automatic repair loop Windows 10?
A corrupted Boot Configuration Data (BCD), damaged system files, a faulty Windows update, or a failing hard drive are the top causes—each breaks the boot chain in a different way.
Common triggers include:
A bad Windows update that overwrites critical registry hives or boot files.
A power outage or improper shutdown during a system update.
A failing hard drive creating bad sectors in the boot partition.
A virus or malware that targets boot records or startup files.
A user manually editing the registry or running risky commands.
When any of these occur, Windows boots into Automatic Repair, which fails to fix the damage because the repair environment itself depends on the same corrupted files. (It’s like trying to fix a flat tire with a broken jack—you need a different tool.)
Is there a Windows 11 coming out?
Yes—Windows 11 was released in 2021 and received major updates through 2025, but as of 2026, it remains the current desktop OS, with Windows 10 in extended support until October 2025.
As of 2026, Windows 11 version 24H2 is the latest stable release, with new features like Copilot integration, improved gaming performance via DirectStorage, and native Android app support via the Amazon Appstore. Microsoft ended free upgrades from Windows 10 in October 2025, but users can still upgrade via the Windows 11 Installation Assistant. If your PC is stuck in Automatic Repair on Windows 10, consider upgrading—Windows 11 has a more robust recovery system and better built-in tools for fixing boot issues. Check aka.ms/getwindows11 for eligibility and download options.
How do you fix attempting repairs?
Fix the boot files using bootrec /fixmbr, bootrec /fixboot, and bootrec /rebuildbcd from the recovery Command Prompt—these commands restore the Master Boot Record, boot sector, and BCD to working order.
When Windows repeatedly says “Attempting Repairs,” it means the boot environment is broken. The fastest fix is to boot into the recovery menu, open Command Prompt, and run the bootrec commands in sequence. Start with /fixmbr, then /fixboot, and finally /rebuildbcd—answer “Y” when prompted. If disk corruption is severe, run chkdsk C: /f /r afterward to repair file system errors. In stubborn cases, disable Automatic Repair first using bcdedit /set {current} recoveryenabled No, then reboot and retry the repair commands. Once the boot files are restored, Windows should start normally.
Edited and fact-checked by the TechFactsHub editorial team.
Alex Chen is a senior tech writer and former IT support specialist with over a decade of experience troubleshooting everything from blue screens to printer jams. He lives in Portland, OR, where he spends his free time building custom PCs and wondering why printer drivers still don't work in 2026.
