Your Windows 11 PC restarts, you see the spinning dots, and then — "Automatic Repair". It spins for a few minutes, then either reboots and does it all over again, or flashes "Startup Repair couldn't repair your PC." You're stuck in the Windows 11 startup repair loop, and it's one of the most frustrating boot failures a user can face.
This 2026 guide walks you through every proven fix — from simple Advanced Startup tricks to BCD rebuilds, CHKDSK, SFC, DISM, System Restore, and a final-resort Windows Reset — all without losing your personal files.
What Causes the Windows 11 Startup Repair Loop?
Windows 11 enters an automatic repair loop when it detects a problem at boot but cannot fix it. The loop happens because Windows keeps trying the same repair routine, failing, and restarting — over and over. Common root causes include:
- Corrupted Boot Configuration Data (BCD): The BCD tells Windows where to find its boot loader. If it's damaged or has missing entries, Windows cannot start and falls back to Automatic Repair every time.
- Failed Windows Update: Feature updates and cumulative patches sometimes corrupt system files mid-installation, leaving Windows in a broken half-updated state.
- Damaged system files: Critical Windows files like winload.exe, ntoskrnl.exe, or HAL.dll can become corrupted by a sudden power loss, disk error, or malware.
- Bad sectors on the hard drive: Physical or logical disk errors prevent Windows from reading the files it needs to boot.
- Incompatible driver or software: A freshly installed driver (especially third-party antivirus or GPU drivers) can crash the boot process before Windows fully loads.
- Secure Boot or UEFI misconfiguration: Changes to BIOS/UEFI settings — or a firmware update — can break the Secure Boot chain and block Windows from loading.
Understanding the cause helps you pick the right fix. Work through the methods below in order — most users resolve the loop by Method 3 or 4.
Method 1 – Force Boot into Advanced Startup Options
Before you can run any repairs, you need to reach the Windows Recovery Environment (WinRE). If Windows keeps looping before you can do anything, force it to open Advanced Startup Options:
- While your PC is attempting to boot (during the spinning dots or the "Automatic Repair" screen), press and hold the power button for 10 seconds to force a hard shutdown.
- Power the PC back on. Let it start to boot, then force-shut it down again during startup.
- Repeat this three times. On the fourth boot attempt, Windows will automatically open the Recovery Environment with the message "Preparing Automatic Repair" followed by the blue recovery screen.
- Click Advanced options when the blue screen appears.
- Navigate to: Troubleshoot > Advanced options
From here you can access Command Prompt, System Restore, Startup Settings, and more. Keep this Advanced options screen open — every method below starts here.
Alternative: If you have a Windows 11 installation USB drive, boot from it and choose Repair your computer instead of Install Now.
Method 2 – Rebuild the BCD (Boot Configuration Data)
A corrupted BCD is the single most common cause of the startup repair loop. Rebuilding it replaces the broken boot configuration with a fresh, correct one.
- From Advanced options, click Command Prompt.
- Run the following commands one at a time, pressing Enter after each:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcdWhat each command does:
bootrec /fixmbr— Rewrites the Master Boot Record. Fixes corruption in the very first sector of the disk that Windows needs to start.bootrec /fixboot— Writes a new boot sector to the system partition. Fixes "BOOTMGR is missing" and similar errors.bootrec /scanos— Scans all drives for Windows installations and lists them. If it finds your Windows installation, the next step can rebuild the BCD for it.bootrec /rebuildbcd— Scans for Windows installations and adds them to a fresh BCD. Type Y and press Enter when prompted to add the installation.
After all four commands complete successfully, type exit, close Command Prompt, and restart your PC. Many users find the loop is resolved at this point.
If bootrec /fixboot returns "Access is denied": Run diskpart, then list vol to find the EFI partition (usually a small FAT32 partition, ~100 MB). Note its volume number, then run sel vol # (replace # with the volume number), then assign letter=V:. Exit diskpart, then run bcdboot C:\Windows /s V: /f UEFI and try again.
Method 3 – Run CHKDSK and SFC from Recovery Console
If rebuilding the BCD didn't fix the loop, the underlying problem may be bad disk sectors or corrupted system files. CHKDSK scans the drive for physical and logical errors; SFC repairs corrupted Windows system files.
From Command Prompt in WinRE:
Step 1 — Check and repair disk errors:
chkdsk C: /f /r /x/f— Fixes errors found on the disk/r— Locates bad sectors and recovers readable data from them/x— Forces the volume to dismount before the scan (required when running from WinRE)
CHKDSK can take anywhere from 10 minutes to over an hour on a large hard drive. Let it run to completion. If it reports fixing errors, that's a good sign this was the root cause.
Step 2 — Repair system files offline:
sfc /scannow /offbootdir=C:\ /offwindir=C:\WindowsThe /offbootdir and /offwindir flags are required because you're running SFC from the recovery environment rather than a live Windows session. SFC will scan and replace any corrupted protected system files.
After both commands complete, type exit and restart. If SFC found and fixed corrupted files, the startup loop should be gone.
Method 4 – Disable Automatic Repair Temporarily
Sometimes the Automatic Repair loop itself is the problem — Windows detects a minor issue, tries to repair it, fails, and loops. Disabling Automatic Repair lets Windows attempt a normal boot so you can log in and fix the underlying issue from within a running Windows session.
From Command Prompt in WinRE:
bcdedit /set {default} recoveryenabled NoThis command tells Windows not to launch Automatic Repair when a boot failure is detected. Restart your PC. Windows will now attempt to boot normally. If it succeeds, log in and:
- Uninstall any recently installed drivers or software that may have caused the issue
- Run Windows Update and install any pending updates
- Run sfc /scannow from an elevated Command Prompt inside Windows
Important: Re-enable Automatic Repair after you've resolved the issue by running:
bcdedit /set {default} recoveryenabled YesLeaving Automatic Repair disabled permanently means Windows won't try to self-heal in future boot failures, which is a security and reliability risk.
Method 5 – Use System Restore from Recovery Environment
If the startup repair loop started after a Windows Update, driver install, or software change, System Restore can roll your PC back to a point before the problem occurred — without touching your personal files.
- From Advanced options, click System Restore.
- Sign in with your Windows account password when prompted.
- The System Restore wizard opens. Click Next.
- Select a restore point dated before the startup loop began. Look for restore points labelled "Windows Update" or "Before [software name] install" if you know the trigger.
- Click Scan for affected programs to see which apps and drivers will be removed.
- Click Next, then Finish, then confirm with Yes.
System Restore will take 15–30 minutes and will restart your PC automatically. Your personal files (documents, photos, videos) are preserved. Installed programs and drivers added after the restore point may be removed.
No restore points available? System Restore was likely disabled. Skip to Method 6 or 7.
Method 6 – Repair Windows 11 Installation with DISM
DISM (Deployment Image Servicing and Management) repairs the Windows component store — the underlying repository from which SFC pulls replacement files. If SFC kept failing or saying it couldn't fix corrupted files, the component store itself is damaged. DISM fixes that.
From Command Prompt in WinRE, run these commands in order:
DISM /Image:C:\ /Cleanup-Image /CheckHealthThis quickly checks whether the offline Windows image is flagged as corrupted. If it reports corruption, proceed:
DISM /Image:C:\ /Cleanup-Image /ScanHealthA deeper scan that confirms corruption (takes 5–10 minutes).
DISM /Image:C:\ /Cleanup-Image /RestoreHealthThis repairs the Windows component store. Without a Windows installation media, DISM pulls repair files from Windows Update. From WinRE without internet, you may need to supply a source:
DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim(Replace D: with the drive letter of your Windows 11 USB installation media.)
After DISM completes, run SFC again to replace any remaining corrupted files:
sfc /scannow /offbootdir=C:\ /offwindir=C:\WindowsRestart when done. DISM + SFC together is a powerful combination that fixes many deeply corrupted Windows installations without requiring a full reinstall.
Method 7 – Reset Windows 11 While Keeping Your Files
If none of the above methods resolved the startup repair loop, it's time to reset Windows 11. The "Keep my files" option reinstalls Windows from scratch while preserving your documents, photos, downloads, and desktop files. Installed applications and drivers will be removed.
- From the blue Advanced options screen, go to Troubleshoot.
- Click Reset this PC.
- Choose Keep my files. (Do NOT choose "Remove everything" unless you intend to wipe the drive.)
- Choose how to reinstall Windows:
- Cloud download — Downloads a fresh Windows 11 image from Microsoft's servers (requires internet; ~4 GB download). Most reliable option for fixing deep corruption.
- Local reinstall — Uses existing Windows files on the drive. Faster but may still carry over corrupted components.
- Review what will be removed, then click Reset.
The reset process takes 30–90 minutes and will restart several times. When complete, you'll land on the Windows 11 setup screen. Your personal files will be in their original locations. A folder called Windows.old on C: will contain your old Windows installation (automatically deleted after 10 days).
After the reset, reinstall your applications, restore any drivers from manufacturer websites, and run Windows Update to get fully current.
Still stuck? If even Reset fails — with errors like "There was a problem resetting your PC" — the storage hardware itself may be failing, or the partition table is too damaged for in-place repair. At that point, a clean Windows 11 installation from USB (erasing the drive) or professional data recovery is the path forward. CloudHouse expert Windows support can diagnose and recover your system remotely, even in severe cases.
FAQ
Why is Windows 11 stuck in a startup repair loop?
Windows 11 enters a startup repair loop when the Boot Configuration Data (BCD) is corrupted, system files are damaged, the hard drive has bad sectors, or a recent update or driver change broke critical boot files. Windows tries to repair itself automatically but fails if the damage is too severe for its built-in tools.
How do I get out of the Windows 11 automatic repair loop?
Force your PC into Advanced Startup Options by interrupting the boot 3 times (press the power button during startup each time). From there, go to Troubleshoot > Advanced options > Command Prompt and run: bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd. Then restart. This resolves the loop for the majority of users.
Will fixing the startup repair loop delete my files?
Methods 1–6 (BCD rebuild, CHKDSK, SFC, DISM, System Restore) do not delete personal files. Only Method 7 (Reset Windows) might affect files — even then, choosing "Keep my files" during reset preserves documents, photos, and desktop files while reinstalling Windows.
What is BCD and how does rebuilding it fix the startup loop?
BCD (Boot Configuration Data) tells Windows where to find and how to load the operating system. If BCD is corrupted or missing entries, Windows can't boot and falls into a repair loop. Running bootrec /rebuildbcd scans all drives for Windows installations and recreates the BCD with the correct boot entries.
Can a failed Windows Update cause the startup repair loop?
Yes. Failed Windows Updates are one of the most common causes of the startup repair loop, especially after feature updates or cumulative updates that modify system files. If this happened after an update, use System Restore to revert to the pre-update state, or use DISM offline repair to fix the corrupted update files.