How to Fix a Computer Stuck in the Startup Repair Loop

Published 2026-10-16 · LuxuriousComputers Repair

Your computer turns on, shows the manufacturer logo, then displays Preparing Automatic Repair followed by Diagnosing your PC — and either loops back to the same screen, shows Startup Repair could not repair your PC, or just restarts and repeats the cycle. The Windows Startup Repair loop is one of the most frustrating boot problems because the tool designed to fix startup issues is itself failing, and the computer never reaches the desktop where you could troubleshoot normally.

Why the loop happens

Windows triggers Automatic Repair when it detects that the previous boot attempt failed. After two consecutive failed boots, Windows enters the Recovery Environment and tries to repair itself. The loop occurs when:

• The repair process cannot identify or fix the actual problem
• The repair itself fails (corrupted repair tools, insufficient disk space for repair operations)
• The underlying cause is not something Startup Repair can fix (hardware failure, severely corrupted system files, bad drivers)
• The boot configuration data (BCD) is corrupted and the repair tool cannot rebuild it

The key to escaping the loop is getting to the Advanced Options menu, which gives you access to tools that are more capable than Automatic Repair.

Getting to Advanced Options

When Startup Repair fails and shows the blue screen with Startup Repair could not repair your PC, you should see an Advanced options button. Click it. If the computer restarts before you can click anything:

1. Turn on the computer
2. As soon as you see the manufacturer logo or the spinning dots, hold the power button for 10 seconds to force it off
3. Turn it on again and force it off again at the same point
4. On the third attempt, let it run. Windows should enter the Recovery Environment and show Choose an option with Troubleshoot as one of the options
5. Select Troubleshoot, then Advanced options

Fix 1: Disable Automatic Repair

The simplest way to break the loop is to prevent Windows from entering Automatic Repair in the first place. This does not fix the underlying problem, but it lets Windows attempt a normal boot — and surprisingly often, Windows boots successfully once the repair tool stops interfering:

1. From Advanced options, select Command Prompt
2. Type: bcdedit /set {default} recoveryenabled No
3. Press Enter. You should see The operation completed successfully
4. Type exit and restart the computer

If Windows boots normally after this, the Startup Repair tool itself was causing the loop — the actual boot process was fine. You can re-enable Automatic Repair later from an elevated Command Prompt in Windows: bcdedit /set {default} recoveryenabled Yes

Fix 2: Boot into Safe Mode

Safe Mode loads Windows with minimal drivers and no startup programs. If a driver or startup application is causing the boot failure, Safe Mode bypasses it:

1. From Advanced options, select Startup Settings, then Restart
2. When the Startup Settings screen appears, press 5 for Safe Mode with Networking (networking lets you download drivers or updates if needed)
3. If Windows boots into Safe Mode successfully, the problem is a driver or startup program, not a core Windows issue

What to do in Safe Mode

• Uninstall recent updates: if the loop started after a Windows update, go to Settings, Windows Update, Update history, Uninstall updates. Remove the most recent update
• Uninstall recent drivers: if you installed a new driver (especially graphics, audio, or network) before the loop started, open Device Manager, find the device, right-click, Properties, Driver tab, Roll Back Driver
• Disable startup programs: open Task Manager (Ctrl + Shift + Esc), Startup tab, and disable everything. Restart normally. If it boots, re-enable startup items one at a time to find the culprit
• Run SFC and DISM: open Command Prompt as administrator and run sfc /scannow. If it finds and fixes errors, restart. If SFC reports it could not fix some files, run DISM /Online /Cleanup-Image /RestoreHealth first, then run SFC again

Fix 3: Rebuild the BCD

The Boot Configuration Data (BCD) tells Windows how to start. A corrupted BCD is one of the most common causes of boot loops that Startup Repair cannot fix:

1. From Advanced options, select Command Prompt
2. Run these commands in order:

bootrec /fixmbr

bootrec /fixboot

bootrec /scanos

bootrec /rebuildbcd

The last command scans for Windows installations and asks if you want to add them to the boot configuration. Type Y and press Enter. Then type exit and restart.

Note: bootrec /fixboot may return Access is denied on some UEFI systems. If it does, try: bootrec /rebuildbcd alone, or use bcdboot C:\Windows /s S: /f UEFI (where S: is the EFI system partition — use diskpart then list volume to find it).

Fix 4: System Restore

If you have System Restore enabled and restore points available, rolling back to a point before the problem started is often the fastest fix:

1. From Advanced options, select System Restore
2. Choose a restore point from before the loop started. If you are unsure which one, pick the most recent one that predates the problem
3. Click Next and Finish. The restore process takes 10 to 30 minutes

System Restore reverts system files, drivers, registry, and installed programs to their state at the restore point. Your personal files (documents, photos, videos) are not affected. Programs installed after the restore point will need to be reinstalled.

Fix 5: Check the hard drive

A failing hard drive or SSD can cause boot loops because Windows cannot read critical system files consistently. From Command Prompt in the Recovery Environment:

chkdsk C: /r

This scans the drive for file system errors and bad sectors. The /r flag attempts to recover data from bad sectors. On an HDD, this can take 30 minutes to several hours depending on drive size and condition. If chkdsk finds and fixes errors, restart and see if Windows boots normally.

If chkdsk reports the drive has bad sectors, the drive is physically failing. Back up your data immediately (you can access files from the Recovery Environment Command Prompt or by booting from a USB Linux drive) and replace the drive.

Fix 6: Reset Windows (keep files)

If none of the above fixes work, resetting Windows reinstalls the operating system while preserving your personal files:

1. From Advanced options, select Reset this PC (or go back to Troubleshoot and select Reset this PC)
2. Choose Keep my files
3. Follow the prompts to reset

This removes all installed programs and resets all settings but keeps your documents, photos, and other personal files in place. You will need to reinstall all your applications afterward. This is a less drastic step than a full clean install but more thorough than any repair tool.

When hardware is the cause

If the boot loop persists through all software fixes, hardware failure may be preventing Windows from loading:

• RAM. A failing RAM stick causes random boot failures. From Command Prompt in Recovery, run mdsched to schedule Windows Memory Diagnostic, or boot from a USB drive with MemTest86
• Hard drive or SSD. If chkdsk found bad sectors or the drive makes clicking sounds, the drive needs replacement
• Motherboard or power supply. Unstable power delivery can corrupt the boot process. If the computer also has other intermittent problems (USB devices disconnecting, random shutdowns), the power supply or motherboard may be involved

Startup repair in Marion

LuxuriousComputers Repair fixes boot loops, Startup Repair failures, and Windows boot problems. We diagnose whether the cause is software (corrupted BCD, bad driver, failed update) or hardware (failing drive, RAM, motherboard), fix it, and verify the system boots cleanly and repeatedly. Same-day turnaround for most boot repair jobs.