How to Fix a Windows Startup Repair Loop
Published 2026-10-16 · Marion Remote Fix
Your computer is stuck in a loop where Windows attempts Startup Repair, fails, restarts, and tries again without ever reaching the desktop. The screen shows Attempting Repairs, Diagnosing Your PC, or Preparing Automatic Repair repeatedly. Each attempt takes several minutes and ends with the message Startup Repair Could Not Repair Your PC or Automatic Repair Could Not Repair Your PC. This loop means Windows detected a boot problem but the automatic fix cannot resolve it, so it keeps trying the same failed repair endlessly.
Access the Advanced Options menu
- To break out of the loop, you need to reach the Advanced Options screen. When you see the Automatic Repair screen that says Your PC Did Not Start Correctly or Startup Repair Could Not Repair Your PC, click Advanced Options instead of Restart. This takes you to the recovery menu where manual repair tools are available
- If the computer restarts before you can click Advanced Options, try interrupting the boot differently. When the computer powers on and shows the manufacturer logo, press and hold the power button to force a shutdown. Repeat this three times — power on, wait for the logo, hold power off. After three forced shutdowns, Windows enters the recovery environment directly on the fourth boot attempt
- If neither method works and you have Windows installation media (USB or DVD), boot from it instead. Change the boot order in BIOS to prioritize the USB or DVD drive. When the Windows Setup screen appears, click Repair Your Computer in the bottom left to access the recovery tools
Try Safe Mode
- Safe Mode loads Windows with only essential drivers, bypassing the component that may be causing the boot failure. From the Advanced Options menu, select Troubleshoot, Advanced Options, Startup Settings, Restart. After the restart, press 4 for Safe Mode or 5 for Safe Mode with Networking
- If Windows boots successfully into Safe Mode, the problem is caused by a driver, startup program, or recently installed software. While in Safe Mode, uninstall any software or driver updates installed shortly before the boot loop started. Check Device Manager for any devices with error icons and update or roll back their drivers
- If Safe Mode also fails to boot, the problem is with a core Windows component rather than a third-party driver. Proceed with the system repair tools below
Run Startup Repair manually
- The automatic Startup Repair that runs in the loop sometimes fails because it runs with limited scope. Running it manually from the Advanced Options menu can produce different results. Select Troubleshoot, Advanced Options, Startup Repair. Let it complete fully without interrupting
- If manual Startup Repair also fails, check the log file it creates. From the Advanced Options menu, open Command Prompt and navigate to the log: type C: then type cd Windows System32 LogFiles Srt then type SrtTrail.txt. This log file identifies the specific component that Startup Repair could not fix, giving you a targeted starting point for manual repair
Repair the boot configuration
- Corrupted boot configuration data (BCD) is a common cause of startup repair loops. From the Advanced Options menu, open Command Prompt and run the following commands in order: bootrec /fixmbr then bootrec /fixboot then bootrec /scanos then bootrec /rebuildbcd
- The scanos command shows detected Windows installations. If it finds your installation, rebuildbcd adds it to the boot configuration. If scanos finds zero installations, the system partition may have a different drive letter in the recovery environment — try dir D: or dir E: to find which letter has the Windows folder
- If bootrec /fixboot returns Access Denied, the EFI system partition may be locked. Run these commands: diskpart then list vol to identify the EFI partition (usually a small FAT32 partition around 100 MB), then select vol (number) then assign letter=S then exit. Then run: cd /d S:\EFI\Microsoft\Boot then bootrec /fixboot
Run system file repairs
- Corrupted system files prevent Windows from booting. From the Command Prompt in the recovery environment, run: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows. This runs System File Checker against the offline Windows installation. The offline switches are necessary because Windows is not running normally
- If SFC reports it cannot repair files, run DISM first: DISM /Image:C:\ /Cleanup-Image /RestoreHealth. In the recovery environment, DISM may need a source for repair files — if it fails without a source, use Windows installation media: DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim (where D is the installation media drive letter)
- After both tools complete, close Command Prompt and restart. If corrupted system files were causing the boot loop, the repair should break the cycle
Check the disk for errors
- Disk errors on the system drive can corrupt boot files and system components. From the Command Prompt in the recovery environment, run: chkdsk C: /f /r. The /f flag fixes file system errors and /r locates bad sectors and recovers readable data. This scan can take a long time on large drives
- If chkdsk finds and fixes errors, restart and see if the boot loop is resolved. Disk errors that damage boot-critical files are a common cause of startup repair loops, especially after sudden power loss or system crashes
- If chkdsk reports the drive has too many bad sectors, the drive may be physically failing. In this case, the priority shifts from fixing the boot to backing up data. Use the recovery environment Command Prompt to copy important files to an external drive before the drive fails completely
Use System Restore
- System Restore can revert Windows to a state from before the boot loop started. From the Advanced Options menu, select System Restore. Choose a restore point dated before the first occurrence of the boot problem
- System Restore reverts system files, installed programs, drivers, and registry settings without affecting personal files. If the boot loop was caused by a driver update, software installation, or Windows Update, System Restore undoes those changes
- If no restore points are available, System Restore was either disabled or the restore points were consumed by disk space pressure. Proceed with other repair methods
Disable automatic repair
- If you need to temporarily stop the loop while troubleshooting, you can disable automatic repair. From the Command Prompt in the recovery environment, run: bcdedit /set {default} recoveryenabled No. This prevents Windows from automatically entering the repair cycle and instead shows the error screen where you can choose your next action
- After disabling automatic repair, the computer may boot to a blue screen or error screen instead of the repair loop. This error screen provides more specific information about the boot failure than the generic Startup Repair Could Not Repair message
- Remember to re-enable automatic repair after fixing the problem: bcdedit /set {default} recoveryenabled Yes. Leaving it disabled means Windows will not attempt automatic recovery from future boot failures
Reset Windows as a last resort
- If no repair method resolves the boot loop, resetting Windows reinstalls the operating system while preserving personal files. From the Advanced Options menu, select Troubleshoot, Reset This PC, Keep My Files. This rebuilds all Windows components from scratch
- The reset process reinstalls Windows and removes all installed applications but preserves files in your user folders (Documents, Pictures, Desktop, and others). After the reset, you need to reinstall your applications. The reset creates a list of removed apps on the desktop for reference
- If even the Keep My Files reset fails, try the Remove Everything option but back up your data first. From the Command Prompt in the recovery environment, connect an external drive and copy your user folders: xcopy C:\Users\YourName E:\Backup\ /E /H /C /I where E is the external drive
Need help with a boot loop?
If your computer is stuck in a Startup Repair loop and the troubleshooting steps above have not resolved the issue, Marion Remote Fix can guide you through advanced boot repair procedures, including BCD reconstruction, system file repair, and driver rollback to get your Windows computer booting normally again.