Common causes
- Corrupted system files left behind by a failed cumulative or feature update that broke the normal startup sequence.
- Broken startup entries, a damaged Boot Configuration Database, or a missing bootloader file on the EFI partition.
- A recently installed or updated device driver, especially storage, display, or antivirus drivers, that crashes during early boot.
- Physical or logical disk errors on the system partition that prevent Windows from loading critical files.
- A power failure, forced shutdown, or battery disconnect that interrupted a system write and left the boot chain incomplete.
- Registry corruption caused by aggressive cleanup utilities, manual edits, or malware that deleted startup keys.
- BitLocker or device-encryption conflicts that prevent Windows from reading the encrypted system partition during recovery.
Advertisement
Who this guide is for
- You are troubleshooting a windows issue, not choosing new software yet.
- The main problem matches this cluster: windows startup errors.
- You want the fastest reliable fixes first before trying a reset or reinstall.
Step-by-step fixes
Step 1
Run Startup Repair once then stop if it does not work
From the Automatic Repair screen, click Advanced options, then Startup Repair. Let Windows complete one full repair cycle without interrupting it. If the system boots normally after one run, the issue is resolved. If the repair loop returns after one clean attempt, do not repeat Startup Repair. It is designed for a narrow range of boot issues, and repeating it does not increase its effectiveness. Move to the next step instead of wasting time on repeated Startup Repair attempts.
Step 2
Boot into Safe Mode and uninstall the most recent driver or update
From Advanced options, go to Startup Settings and restart. Press F4 for Safe Mode or F5 for Safe Mode with Networking. Once in Safe Mode, open Settings, go to Update and Security, and view your update history. Uninstall the most recent quality update or feature update. Then open Device Manager and check for recently updated drivers, especially display, storage, chipset, and antivirus drivers. Roll back or uninstall any driver that was updated immediately before the loop started. Restart normally after removing the suspected cause.
Step 3
Run SFC and CHKDSK from the recovery Command Prompt
From Advanced options, open Command Prompt. First identify your Windows drive letter, which may not be C in recovery mode. Run dir C: and dir D: to find the partition containing the Windows folder. Then run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows, replacing the drive letter as needed. After SFC finishes, run chkdsk C: /f /r to scan for and repair disk errors. Both commands can take 30 minutes or more on a mechanical drive. Do not interrupt them. If either command reports that it found and repaired errors, restart and test whether the loop is resolved.
Step 4
Run DISM from recovery to repair the component store
If SFC reported unfixable corruption, the component store itself may be damaged. From the recovery Command Prompt, run DISM /Image:C:\ /Cleanup-Image /RestoreHealth. If DISM cannot connect to Windows Update for repair sources, mount a matching Windows ISO and add the source flag: /Source:wim:E:\sources\install.wim:1. After DISM finishes, run SFC again to confirm that all system files pass validation. This two-step approach resolves deeper corruption that SFC alone cannot repair.
Step 5
Rebuild the boot record and BCD store if Windows still cannot start
If the loop started after a power failure, drive clone, or partition resize, the boot configuration may be damaged independently of system files. From the recovery Command Prompt, run bootrec /fixmbr, bootrec /fixboot, and bootrec /rebuildbcd in that order. If bootrec /fixboot returns an access-denied error, run bootsect /nt60 sys first. Verify that rebuildbcd detects the correct Windows installation and add it. Restart and check whether the system reaches the login screen.
Step 6
Reset Windows with the keep-files option as a last resort
If every previous step failed and the system still loops, go to Advanced options and select Reset this PC with the Keep my files option. This reinstalls Windows while preserving personal documents and photos but removes all installed desktop applications. After the reset, check Windows Update for the latest cumulative patches, reinstall your applications, and verify that the system is stable before restoring any backup data. A reset is faster and less disruptive than a clean install and resolves the vast majority of persistent repair loops.
What to do next if this fails
- Move to the next fix instead of repeating the same step multiple times.
- Check the related guides in this cluster before attempting a full reset.
- If startup, update, and corruption symptoms overlap, widen the diagnosis instead of treating one error in isolation.
Advertisement
FAQ
Will I lose my personal files when fixing the Automatic Repair loop?
Usually no. The first several steps in this guide, including Startup Repair, Safe Mode rollback, SFC, and CHKDSK, do not remove personal files. A Reset with the keep-files option preserves user data but removes installed applications. A clean install is the only step that wipes everything, and it is the last resort.
Can a bad Windows update cause the Automatic Repair loop?
Yes. Interrupted or corrupted Windows updates are one of the most common triggers. The update breaks a boot-critical system file or driver, and Windows enters the repair loop instead of loading normally. Booting into Safe Mode and uninstalling the most recent quality update often resolves it immediately.
Why does Startup Repair keep running but never fix anything?
Startup Repair only addresses a narrow set of boot problems. If the root cause is a corrupted system file, a bad driver, or a disk error, Startup Repair cannot fix it and simply loops. You need to move past Startup Repair and use targeted commands like SFC, DISM, CHKDSK, or driver rollback from Safe Mode or the recovery Command Prompt.
How do I get to Advanced Options when stuck in the repair loop?
When the Automatic Repair screen appears, click Advanced options instead of clicking Restart. From there you can access Safe Mode, Command Prompt, Startup Settings, and System Restore. If the screen does not appear, force-power-off the PC three times during boot to trigger the Windows Recovery Environment.
Should I use System Restore to fix the Automatic Repair loop?
System Restore can work if a restore point exists from before the problem started. Choose a restore point dated before the last update or driver install. However, System Restore does not fix disk errors or deep file corruption, so if the loop returns after restoring, continue with the manual SFC and CHKDSK steps below.
Does resetting the PC fix the Automatic Repair loop permanently?
Usually yes, but a Reset removes all installed applications and is harder to reverse than targeted command-line repairs. It is best used after the less destructive fixes have failed. Choose the keep-files option to preserve documents, photos, and other user data during the reset.