How to Fix a Windows Boot Loop on Windows 10 and 11
PC stuck in a restart loop, cycling through "Preparing Automatic Repair," or rebooting after a blue screen? This guide walks you through every common boot loop cause — corrupted BCD, failed updates, driver conflicts, and failing drives — with step-by-step recovery solutions.
- ✓Detects corrupted boot configuration data (BCD) and rebuilds it automatically
- ✓Identifies failed Windows updates causing restart loops and rolls them back
- ✓Runs system file integrity checks from recovery to repair corrupted OS components
Best for restart loops, Automatic Repair cycles, post-update boot failures, and blue screen reboot loops on Windows 10 and 11.
Main Troubleshooting Guide
How to Fix Blue Screen of Death (BSOD) →Complete symptoms, causes, and step-by-step solutions
Symptoms
You might be experiencing this problem if you notice:
- •PC restarts before reaching the desktop — you see the Windows logo and then it reboots
- •"Preparing Automatic Repair" appears on every boot but never finishes or leads to another restart
- •Blue screen (BSOD) flashes briefly and the computer immediately restarts
- •Windows starts loading, shows spinning dots, then reboots — over and over
- •"Your PC did not start correctly" message with no option that fixes it
- •Boot loop started immediately after a Windows update was installed
- •PC gets to the login screen but restarts before you can type your password
- •"Diagnosing your PC" screen appears and then the computer restarts without any result
- •Boot loop after installing a new driver or software
Common types of boot loop problems on Windows
Post-Update Boot Loop
Windows restarts repeatedly after installing a quality or feature update. The update corrupted boot files or installed an incompatible driver. Uninstalling the update from Safe Mode or Recovery usually resolves it.
Automatic Repair Loop
"Preparing Automatic Repair" runs on every boot but never fixes anything. The repair tool itself may be broken. Disabling it and running manual BCD/SFC repair is more effective.
BSOD Restart Loop
A blue screen appears briefly and the PC restarts before you can read the error code. A driver or kernel component is crashing. Disabling auto-restart reveals the actual BSOD error.
Hardware-Related Boot Failure
The PC never reaches the Windows logo — it powers on, tries to boot, and restarts. This often indicates a failing drive, bad RAM, or BIOS misconfiguration rather than a Windows problem.
What RescuePC checks when your PC is stuck in a boot loop
A boot loop means Windows starts loading but crashes or restarts before reaching the desktop. The cause could be a corrupted boot file, a failed update, a bad driver, or a dying storage drive. RescuePC scans the critical boot components to identify the specific failure point.
- →Checks BCD (Boot Configuration Data) integrity — detects corrupted or missing boot entries
- →Scans system file health using SFC and DISM to find corrupted Windows components
- →Identifies recently installed updates or drivers that may have triggered the boot loop
- →Checks storage drive health for bad sectors and firmware failures that prevent boot
- →Detects registry corruption that causes Windows to crash during startup
Most useful when you can still reach Safe Mode or Recovery Environment, or when the boot loop started after a specific event like a Windows update or driver installation.
Manual troubleshooting vs RescuePC
On your own
- •Force-restarting 3 times to trigger Recovery, then navigating nested menus to reach Safe Mode or Command Prompt
- •Guessing whether the cause is a failed update, corrupted BCD, bad driver, or dying storage drive
- •Running bootrec commands manually and hoping the correct one fixes it
- •Trying SFC and DISM offline from Command Prompt with drive letter guessing
- •Doing a System Restore and discovering there are no restore points available
With RescuePC
- →Scans boot configuration, system files, and driver state in one automated diagnostic pass
- →Identifies the specific failure layer — boot files, drivers, system files, or storage health
- →Repairs corrupted system components that cause startup crashes
- →Detects failing storage drives that make boot loops recur even after software repairs
Boot loops are stressful because you can't access your desktop to troubleshoot. RescuePC identifies the root cause so you can apply the right fix on the first attempt instead of cycling through trial-and-error from Recovery.
When this page is most likely to help
- ✓Your PC started boot-looping after a Windows update was installed
- ✓You see "Preparing Automatic Repair" on every boot but it never succeeds
- ✓Windows shows the logo and spinning dots but restarts before reaching the desktop
- ✓A blue screen flashes briefly and then the PC restarts automatically
- ✓The boot loop started after you installed a new driver or software
Most boot loops are caused by corrupted boot files, failed updates, or driver conflicts — all of which are repairable without reinstalling Windows using the recovery methods above.
When boot loop repair may not be enough
Some boot loops are caused by hardware failures that software recovery can't fix.
- ⚠The storage drive is physically failing — chkdsk reports unrepairable bad sectors, or S.M.A.R.T. shows "Pred Fail"
- ⚠The PC never reaches the BIOS/UEFI screen — it powers on and off without any display (this is a hardware POST failure)
- ⚠RAM is faulty — the boot loop happens even in Safe Mode and with a fresh Windows installation
- ⚠The boot loop persists after a full Windows reset or clean install (pointing to hardware, not software)
- ⚠The PC only boot-loops when a specific piece of hardware is connected (GPU, NVMe drive, USB device)
Common Causes
- ⚠A Windows update failed mid-installation and left boot files in a corrupted state
- ⚠Corrupted BCD (Boot Configuration Data) — Windows can't find or load the OS partition
- ⚠Incompatible or corrupted driver (especially GPU, storage, or chipset drivers) crashing during startup
- ⚠Critical system files (ntoskrnl.exe, winload.efi, hal.dll) are damaged or missing
- ⚠Failing hard drive or SSD — bad sectors or firmware failure preventing boot file reads
- ⚠Registry hive corruption — Windows can't load core configuration data during startup
- ⚠Secure Boot or UEFI configuration conflict after a BIOS update or hardware change
- ⚠Malware or rootkit that modified the boot sector or Master Boot Record
- ⚠Automatic Repair itself is broken — the repair tool crashes or corrupts files further during each attempt
Solutions
Solution 1: Boot into Safe Mode and Uninstall the Problem
- 1Force power off 3 times during boot (hold the power button as soon as the Windows logo appears) to trigger Windows Recovery Environment
- 2Go to Troubleshoot > Advanced options > Startup Settings > Restart
- 3Press 4 or F4 for Safe Mode (or 5/F5 for Safe Mode with Networking)
- 4In Safe Mode, open Settings > Windows Update > Update History > Uninstall Updates
- 5Uninstall the most recent quality or feature update
- 6If a driver caused it, open Device Manager > find the device > right-click > Uninstall device
- 7Restart normally — if it boots, the uninstalled update or driver was the cause
Solution 2: Rebuild the Boot Configuration Data (BCD)
- 1Boot from Windows installation media (USB or DVD) — change boot order in BIOS if needed
- 2Click "Repair your computer" (not "Install now")
- 3Go to Troubleshoot > Advanced options > Command Prompt
- 4Run: bootrec /fixmbr — repairs the Master Boot Record
- 5Run: bootrec /fixboot — writes a new boot sector to the system partition
- 6Run: bootrec /scanos — scans for Windows installations the BCD doesn't know about
- 7Run: bootrec /rebuildbcd — rebuilds the entire Boot Configuration Data store
- 8Type exit, then restart — this fixes most boot loops caused by corrupted boot files
Solution 3: Run SFC and DISM from Recovery
- 1Boot into Recovery Environment (force-restart 3 times, or use installation media)
- 2Go to Troubleshoot > Advanced options > Command Prompt
- 3Find your Windows drive letter — run: dir C:\ and dir D:\ to see which has the Windows folder
- 4Run: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows (replace C: with your drive letter)
- 5Run: DISM /Image:C:\ /Cleanup-Image /RestoreHealth
- 6Wait for both to complete — they repair corrupted system files that prevent boot
- 7Type exit and restart
Solution 4: Disable Automatic Repair (If Automatic Repair Is the Problem)
- 1Boot into Recovery Environment > Command Prompt
- 2Run: bcdedit /set {default} recoveryenabled No
- 3Restart — this prevents Automatic Repair from running and may let Windows boot normally
- 4If Windows boots, run SFC /scannow and DISM from inside Windows to repair underlying damage
- 5Re-enable Automatic Repair later with: bcdedit /set {default} recoveryenabled Yes
Solution 5: System Restore to a Working State
- 1Boot into Recovery Environment (force-restart 3 times, or use installation media)
- 2Go to Troubleshoot > Advanced options > System Restore
- 3Select a restore point created before the boot loop started
- 4Follow the prompts to restore — this rolls back system files, drivers, and registry entries
- 5Restart and verify the boot loop is resolved
- 6If no restore points exist, this option won't be available — move to BCD repair or SFC/DISM instead
Solution 6: Check the Storage Drive Health
- 1Boot into Recovery Environment > Command Prompt
- 2Run: chkdsk C: /r — this scans for and repairs bad sectors on the drive (replace C: with your Windows drive)
- 3This can take 30–60+ minutes depending on drive size
- 4If chkdsk reports unrepairable bad sectors, the drive may be failing and needs replacement
- 5Run: wmic diskdrive get status — check if any drives report "Pred Fail" (predicted failure)
- 6If the drive is an SSD, check the manufacturer's health tool for remaining lifespan
Solution 7: Reset Windows While Keeping Your Files
- 1Boot into Recovery Environment > Troubleshoot > "Reset this PC"
- 2Choose "Keep my files" — this reinstalls Windows but preserves your documents, photos, and personal files
- 3Note: installed programs and drivers will be removed and need to be reinstalled
- 4Follow the prompts and let the reset complete (can take 30–60 minutes)
- 5This is a last resort before a full clean install — use it only if BCD repair, SFC/DISM, and System Restore all failed
Break a boot loop — the exact commands (from Recovery)
After 2–3 failed boots Windows opens Recovery automatically (or force it: power off during the spinner 3 times). From Advanced options > Command Prompt, rebuild the boot path in this order.
bootrec /fixmbrWrites a clean Master Boot Record — repairs MBR corruption from failed updates or dual-boot leftovers.
bootrec /fixbootWrites a new boot sector to the system partition.
bootrec /rebuildbcdScans for Windows installations and rebuilds the boot configuration database — the fix for "operating system not found" loops.
chkdsk C: /fRepairs file-system errors that corrupt boot files on every write.
sfc /scannow /offbootdir=C:\ /offwindir=C:\WindowsRepairs system files OFFLINE — required syntax when Windows itself cannot boot.
If bootrec /fixboot returns "Access is denied" on UEFI systems, the EFI partition needs remounting first — that is the point to use guided recovery. RescuePC’s USB workflow scripts this whole sequence.
What kind of boot loop are you experiencing?
Windows logo appears, spinning dots, then the PC restarts — repeating forever
Likely cause: A critical system file or driver is crashing during boot. The OS gets past the bootloader but fails during kernel initialization. Booting into Safe Mode and uninstalling recent updates/drivers usually fixes this.
"Preparing Automatic Repair" on every boot — never finishes or leads to restart
Likely cause: Automatic Repair itself may be broken, or the repair tool is failing to fix a deeper issue (corrupted BCD, registry, or system files). Disabling Automatic Repair and manually running bootrec + SFC is more reliable.
Blue screen flashes briefly and then the PC restarts immediately
Likely cause: A driver or kernel component is crashing with a BSOD. Windows is set to auto-restart on crash, so you can't read the error. Boot into Safe Mode and check Event Viewer, or disable auto-restart via Recovery > Command Prompt: bcdedit /set {default} bootstatuspolicy displayallfailures.
Boot loop started right after a Windows update
Likely cause: The update corrupted boot files or installed an incompatible driver. Boot into Safe Mode and uninstall the update, or use Recovery Environment > Uninstall Updates. If neither works, run bootrec /rebuildbcd.
PC powers on but never shows the Windows logo — no BIOS screen, just restarts
Likely cause: This is likely a hardware issue, not a Windows issue. The system is failing POST (Power-On Self-Test). Check RAM seating, try removing recently added hardware, and reset BIOS to defaults by removing the CMOS battery for 30 seconds.
Best next step
Good fit for boot loops after Windows updates, "Preparing Automatic Repair" loops, BSOD restart cycles, and startup failures caused by corrupted boot files or driver conflicts on Windows 10 and 11.
Why RescuePC handles boot loop problems well
Boot loops trap you in a cycle where you can't access the desktop to run diagnostics. The cause could be a corrupted boot sector, a failed update, a crashing driver, or a dying drive — and they all present the same symptom: restart, restart, restart.
- →Scans boot configuration, system files, and storage health to identify the specific failure layer
- →Detects corrupted BCD entries that prevent Windows from locating the OS partition
- →Identifies recently installed updates and drivers that triggered the boot failure
- →Repairs system file corruption that causes kernel crashes during startup
Browse More Crashes & Blue Screens Guides
Frequently asked questions
Why does my PC keep restarting before reaching the desktop?▼
Can a Windows update cause a boot loop?▼
What do I do if Automatic Repair keeps running but doesn't fix anything?▼
Will I lose my files if I fix a boot loop?▼
My PC boot-loops but I can't access Recovery Environment — what do I do?▼
Related Troubleshooting Guides
These specific guides cover common variations of this problem: