How to Fix a Computer Stuck in a Startup Repair Loop
A Startup Repair loop is one of the most frustrating Windows problems. Your computer fails to boot, Windows launches Automatic Repair, the repair process runs for a while, reports that it could not fix the problem, then restarts — and the whole cycle repeats. You are trapped: Windows cannot start normally, and the automatic repair tool that is supposed to fix it is not actually fixing anything. The good news is that the repair loop itself is not the real problem — something else broke the boot process, and Startup Repair simply cannot fix that particular issue automatically. Fixing the actual cause breaks the loop.
Get to the Advanced Startup Options menu
You need to reach the Windows Recovery Environment (WinRE) menu where you have more repair tools than just Automatic Repair. There are several ways to get there depending on how far your computer gets in the boot process:
- From the "Startup Repair couldn't repair your PC" screen: Click Advanced options. This takes you directly to the recovery menu
- If the loop restarts before showing that screen: Force-interrupt the boot process three times in a row. Power on, wait for the Windows loading dots to appear, then hold the power button for 10 seconds to force shutdown. Repeat two more times. On the third restart, Windows enters the Recovery Environment automatically and shows the Choose an option screen
- From a Windows installation USB: If neither method above works, create a Windows installation USB on another computer (use the Media Creation Tool from Microsoft). Boot from the USB, select your language, then click Repair your computer in the bottom left instead of Install now
Try Safe Mode first
Safe Mode loads Windows with only the minimum drivers and services. If a recently installed driver, update, or program broke the boot process, Safe Mode bypasses it and lets you undo the change.
- From the Advanced options menu, select Troubleshoot, then Advanced options, then Startup Settings, then Restart
- After the restart, press 4 (or F4) for Safe Mode, or 5 (or F5) for Safe Mode with Networking (choose this if you might need internet access to download drivers)
- If Windows boots into Safe Mode successfully, the problem is likely a driver, update, or program that loads during normal startup but not in Safe Mode
What to do in Safe Mode
- Uninstall recent updates: Go to Settings, Windows Update, Update history, Uninstall updates. Remove the most recent quality or feature update. Windows updates are the most common trigger for startup repair loops
- Uninstall recently added software: If you installed a program (especially security software, disk utilities, or driver-updating tools) before the loop started, uninstall it
- Roll back a driver: Open Device Manager, expand the category of the driver you suspect (Display adapters for GPU drivers is the most common culprit), right-click the device, Properties, Driver tab, Roll Back Driver
- Disable startup programs: Open Task Manager (Ctrl + Shift + Esc), Startup tab, and disable everything. Then restart normally. If it boots, re-enable items one at a time to find the one that causes the loop
Run system file repair
Corrupted Windows system files are a common cause of startup repair loops. Two built-in tools can repair them from the command line.
From the Advanced options menu, select Troubleshoot, Advanced options, Command Prompt. A command prompt window opens. Run these commands:
sfc /scannow— System File Checker scans all protected system files and replaces corrupted ones from a cached copy. This takes 10 to 20 minutes. If it finds and repairs files, restart and check if the loop is broken- If SFC reports that it could not repair some files, or if the loop continues, run DISM:
DISM /Online /Cleanup-Image /RestoreHealth. DISM repairs the Windows image itself, which SFC then uses as its source for file replacement. This requires an internet connection or a Windows installation USB as a source. After DISM completes, runsfc /scannowagain
Rebuild the Boot Configuration Data
The Boot Configuration Data (BCD) tells Windows how to start. If the BCD is corrupted or missing, Windows cannot find its own boot files and the startup repair loop is the result.
From the Command Prompt in WinRE, run these commands one at a time:
bootrec /fixmbr— writes a new Master Boot Record (for legacy BIOS boot systems)bootrec /fixboot— writes a new boot sector. If this returns "Access is denied," runbootsect /nt60 sysfirst, then retrybootrec /rebuildbcd— scans for Windows installations and rebuilds the BCD. When it finds your installation and asks "Add installation to boot list?" type Y and press Enter
After running all three, type exit and restart. If the BCD was the problem, Windows should now boot normally.
Disable Automatic Repair
If the loop is caused by Automatic Repair itself interfering with the boot process (rare but possible), you can disable it to let Windows attempt a normal boot without the repair tool intercepting.
From the Command Prompt in WinRE, run: bcdedit /set {default} recoveryenabled No
Restart and see if Windows boots normally. If it does, the actual boot problem may have been intermittent and resolved itself, while Automatic Repair kept triggering because it was set to run. If Windows still does not boot normally after disabling Automatic Repair, re-enable it with: bcdedit /set {default} recoveryenabled Yes
Use System Restore
If you have System Restore points available, restoring to a point before the problem started is one of the most reliable fixes. System Restore rolls back system files, drivers, and registry to a previous working state without affecting your personal files.
- From the Advanced options menu, select System Restore
- Select your Windows account and enter your password
- Choose a restore point dated before the startup problems began. If you are not sure which one to pick, select the oldest available point
- Confirm and let the restoration process complete. The computer will restart
If no restore points are available, System Restore was either disabled or the restore points were deleted by a disk cleanup operation.
Check the disk for errors
A failing hard drive or SSD with bad sectors can corrupt the system files that Windows needs to boot, causing the repair loop.
From the Command Prompt in WinRE:
- Run
chkdsk C: /r(replace C: with your Windows drive letter if different). The /r flag locates bad sectors and recovers readable information. This can take an hour or more depending on drive size - If chkdsk finds and fixes errors, restart and check if the loop is resolved
- If chkdsk reports that the drive has unrecoverable sectors, the drive is failing. Back up your data as soon as possible (you can access files from the WinRE command prompt or by booting from a Linux USB) and replace the drive
Reset Windows as a last resort
If nothing above works, resetting Windows reinstalls the operating system while optionally keeping your personal files.
- From the Advanced options menu, select Troubleshoot, then Reset this PC
- Choose Keep my files (reinstalls Windows but preserves your documents, photos, and other personal files in your user folders) or Remove everything (complete clean start)
- Follow the prompts to complete the reset
Keep my files preserves your data but removes all installed programs — you will need to reinstall them. If the Reset option fails (which can happen if the recovery partition is also corrupted), a clean install from a Windows USB is the final fallback.
Startup repair loop help in Marion
If your computer is stuck in a startup repair loop and the steps above have not resolved it, Marion Remote Fix can assist with remote diagnosis and repair once we can establish a connection, or guide you through the recovery process step by step to get your system booting again.