Windows starts, shows the logo, then restarts. Over and over. No error code, no recovery screen, just a loop. We see this in remote support sessions almost every day, and the good news is that Windows boot loop recovery is possible in the vast majority of cases without reinstalling Windows from scratch. This guide walks you through every fix in order, from the fastest two-minute trick to low-level command-line repair.

TL;DR

Windows boot loop recovery starts with forcing WinRE open by power-cycling the machine 3 times at the logo. From there, try Startup Repair, System Restore, or Uninstall Updates. If WinRE is inaccessible, boot from a Windows USB installer and choose Repair. For stubborn cases, run chkdsk C: /r, SFC, DISM and bootrec /rebuildbcd from Command Prompt. Reset this PC (Keep my files) is the last software option before suspecting hardware.

⏳️ 13 min read ✅ Up to 90% success rate 📅 Updated June 2026

Key Takeaways

Power-cycling the startup 3 times forces Windows into Automatic Repair, giving you access to WinRE recovery tools.
Startup Repair and Uninstall Updates fix the majority of boot loops caused by bad updates or driver changes.
If WinRE is broken, a Windows USB installer gives you the same tools without touching the internal drive.
CHKDSK, SFC and DISM repair disk errors and corrupted system files at a low level.
bootrec /rebuildbcd reconstructs damaged boot configuration, including on UEFI systems.
If the PC loops even when booting from USB, suspect RAM or a failing drive, not software.

At a Glance

Difficulty: Medium to Advanced
Time Required: 15 to 90 mins depending on tier
Success Rate: Around 85 to 90% for software-only causes

What Causes a Windows Boot Loop?

The short answer: something broke between the firmware handing control to Windows and Windows finishing its startup sequence. That window is surprisingly fragile. Here are the most common culprits we see.

Failed or incompatible updates. A Windows Update or driver update that didn't complete cleanly is the number one cause. The update modifies system files, the machine reboots partway through, and now the OS is in a half-updated state that can't start properly. If your loop started the morning after Patch Tuesday, this is almost certainly why. A bad Realtek audio driver Windows Update is a classic example of how a single driver package can destabilise a boot.

Corrupted system files. Power cuts during writes, sudden shutdowns, or even aggressive third-party optimisation tools can corrupt the core Windows files that the boot process depends on. SFC and DISM (covered in Tier 3) are specifically designed to detect and fix this.

Damaged boot configuration (BCD/EFI). The Boot Configuration Database tells the bootloader where to find Windows. If it gets corrupted or wiped, the system has no idea what to load. This can happen after disk cloning, partition resizing, or even some antivirus tools that touch the MBR. On modern UEFI machines the EFI System Partition can also get corrupted, which looks identical from the outside.

Disk problems. Bad sectors on an HDD or a failing SSD can prevent critical boot files from being read. CHKDSK will surface this. If CHKDSK reports uncorrectable errors, the drive itself may need replacing before any OS repair will stick. Worth noting: if you've had any recent backup corruption issues on this machine, that's often an early sign the storage is struggling.

Hardware faults. Faulty or unseated RAM is a surprisingly common cause of boot loops that look like software problems. If the machine loops even when booting from a USB installer, start pulling RAM sticks before you spend hours on command-line repairs that won't help.

Windows Boot Loop Recovery: Quick Fix (Tier 1)

Start here. These take under ten minutes and fix a large chunk of cases.

Force WinRE via Power Cycling Easy

Turn the PC on.
Wait for the Windows logo or spinning dots to appear.
Force it off.
Hold the power button for 5 seconds until the machine cuts out completely.
Repeat twice more.
Turn on, wait for the logo, force off. Do this a total of 3 times.
Let it boot on the 4th attempt.
Windows detects the failed starts and automatically launches Automatic Repair. You should see a blue screen saying "Preparing Automatic Repair" followed by Advanced options.
Choose Troubleshoot, then Advanced options.
From here you can access Startup Repair, System Restore, Uninstall Updates, and Command Prompt.

If you see the Advanced options screen, you're in WinRE. Proceed to Tier 2 tools below.

If the power-cycling trick doesn't trigger Automatic Repair after 4 or 5 attempts, WinRE may be disabled or the partition may be corrupted. Skip to the USB installer method in Tier 2.

Check BIOS/UEFI Settings Easy

Enter firmware setup.
Press Del, F2, Esc or F10 immediately at power-on. The exact key varies by manufacturer, it's usually shown briefly on screen.
Load defaults.
Find the option to Load Optimised Defaults or Load Setup Defaults (often F9) and confirm. This clears any dodgy firmware settings.
Check boot order.
Make sure your Windows drive (SSD or HDD) is listed first, not a USB stick or network boot option you may have set previously.
Check date and time.
An incorrect date, especially a date in the past, can indicate a dead CMOS battery and can cause certificate or Secure Boot validation failures.
Save and exit.
Press F10 (or the Save and Exit option) and let the machine restart.

If a firmware misconfiguration was the cause, Windows will now boot normally.

More Windows Boot Loop Recovery Options (Tier 2)

These tools are available from within WinRE or from a Windows USB installer. If you can reach WinRE from the power-cycling trick above, you're already there. If not, you'll need to create installation media on another PC first (instructions in Solution 5 below).

Run Startup Repair Easy

From WinRE:
Go to Troubleshoot, then Advanced options, then Startup Repair.
Select your Windows installation when prompted and let it run. It may take 5 to 15 minutes.
Restart when complete and test whether Windows boots. If Startup Repair says it couldn't fix the problem, move on to System Restore or Uninstall Updates.

Startup Repair automatically fixes many BCD and boot-sector problems without any manual input.

System Restore or Uninstall Recent Updates Easy

For System Restore:
In WinRE go to Troubleshoot, Advanced options, System Restore. Pick a restore point dated before the loop started. Windows often creates restore points automatically before updates and driver installs.
For Uninstall Updates:
In WinRE go to Troubleshoot, Advanced options, Uninstall Updates. Try Uninstall latest quality update first. If that doesn't fix it, try Uninstall latest feature update.
Restart and test after each attempt. Don't try both at once or you'll lose track of what worked.

These two options fix the majority of boot loops that started right after a Windows Update or driver change.

Boot from Windows USB Installer Medium

On another PC, download the Windows Media Creation Tool from Microsoft. Run it and choose Create installation media, then USB flash drive. You'll need an 8 GB or larger USB drive.
Plug the USB into the broken PC. Enter BIOS/UEFI (Del or F2 at startup) and set the USB drive as the first boot device. Save and exit.
At the Windows Setup screen, choose Repair your computer, NOT Install now. This gives you access to all the same WinRE tools (Startup Repair, System Restore, Command Prompt) even if the internal WinRE partition is broken.
Work through Solutions 3 and 4 from this screen before moving to Tier 3.

Make sure you download the correct Windows edition (Home vs Pro, 32-bit vs 64-bit) to match the installed OS. Mismatches won't cause data loss here but some repair tools may behave oddly.

Advanced Windows Boot Loop Recovery Fixes (Tier 3)

These steps require Command Prompt from WinRE or the USB installer. Go to Troubleshoot, Advanced options, Command Prompt. They're not as scary as they look, but do follow the commands exactly.

Before running anything, it's worth knowing why these tools exist. Microsoft's own documentation on bootrec.exe explains how the boot record and BCD interact. And Microsoft's SFC guide covers exactly when and how to run it offline. Worth a skim if you want to understand what's happening under the hood.

CHKDSK, SFC and DISM Advanced

Open Command Prompt from WinRE.
Troubleshoot, Advanced options, Command Prompt.
Run CHKDSK first:
chkdsk C: /r
This scans for bad sectors and attempts to recover readable data. It can take 20 to 60 minutes on a large HDD. An SSD is much faster. If CHKDSK reports uncorrectable errors, the drive is likely failing and needs replacing before software repairs will hold.
Run DISM to repair the component store:
dism.exe /image:C:\ /cleanup-image /restorehealth
This repairs the Windows image that SFC relies on. If the image itself is corrupt, SFC won't be able to fix anything.
Run SFC to repair system files:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
This checks and replaces corrupted core OS files using the repaired image.
Restart and test. Took three reboots before this one stuck on a recent client machine, so give it a couple of tries.

If CHKDSK reports a large number of bad sectors or says it cannot fix errors, stop here and back up your data before doing anything else. A failing drive will undo any repairs you make.

Rebuild Boot Configuration (BCD/EFI) Advanced

Open Command Prompt from WinRE.
Run these four commands in order:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
These repair the master boot record, fix the boot sector, scan for Windows installations, and rebuild the BCD store. When bootrec /rebuildbcd finds your Windows installation, type Y to add it.
On UEFI systems (most PCs made after 2012), you may also need to recreate the EFI boot files. First identify your EFI partition letter using Diskpart, then run:
bcdboot C:\Windows /l en-us /s X: /f UEFI
Replace X: with the actual EFI partition letter.
Restart and check whether Windows loads. If it does, brilliant. If not, move to the reset option below.

If bootrec /fixboot returns an "Access is denied" error on a UEFI system, you need to assign a drive letter to the EFI partition first using Diskpart before running bcdboot. Search "assign EFI partition letter diskpart" for the exact steps.

Test RAM and Hardware Medium

If the PC loops even when booting from the USB installer, this is almost certainly hardware, not software. Stop running OS repairs and check the hardware first.
Remove non-essential peripherals. Unplug all USB devices, external drives, and extra monitors. Try booting with just keyboard and monitor.
Test RAM one stick at a time. If you have two RAM sticks, remove one and try booting. Then swap them. A faulty module will cause loops that look identical to OS corruption.
Run firmware diagnostics. Many PCs (HP, Dell, Lenovo) have built-in hardware tests accessible by pressing F2 or F12 at startup. These will flag failing drives or RAM definitively.

Hardware faults won't be fixed by any OS repair tool. If diagnostics confirm a failing drive or bad RAM, the component needs replacing. We can advise remotely on what to buy and how to reinstall Windows afterwards.

Reset This PC or Repair Install (Last Resort) Medium

From WinRE: Troubleshoot, Reset this PC, Keep my files. This removes apps and settings but keeps your documents and personal data. Allow 30 to 60 minutes.
If Reset fails, boot from the Windows USB installer, choose Install now, select the same Windows edition, and pick the option to keep personal files. This is an in-place repair install and it preserves your data while replacing all system files.
After completion, Windows will need to reinstall your applications but your files will be intact. Check Device Manager for any driver issues once you're back in Windows.

A repair install has a very high success rate for software-only boot loops. It's not effective if the drive itself is failing.

Preventing Windows Boot Loop Recovery Situations

Most boot loops are preventable. Here's what actually makes a difference, in order of importance.

1. Keep backups and restore points active. This is the single biggest thing. If you have a restore point from before the loop started, recovery takes five minutes. Without one, you're looking at command-line repair or a full reset. Enable System Restore in Windows (search for "Create a restore point" in the Start menu) and set it to monitor your C: drive. For files, use File History or a proper cloud backup. A bad update can corrupt things fast, as anyone who's dealt with Windows Security Centre service failures after an update will know.

2. Be careful with driver updates. Only install drivers from your PC manufacturer's support page or directly from the hardware vendor. Third-party driver updater tools are a common cause of incompatible driver installs that trigger boot loops. If Windows Update is pushing a driver you don't want, you can hide it using the "Show or hide updates" troubleshooter from Microsoft.

3. Never cut power during an update. If the update screen says "Do not turn off your PC", take that seriously. Even a brief power cut at the wrong moment can leave the OS in a broken half-updated state. If you're on a desktop, a cheap UPS is worth the investment. Laptops are safer here since they have battery backup built in.

4. Monitor disk health. Run chkdsk C: /f occasionally (you can schedule it to run at next startup from an elevated Command Prompt). Tools like CrystalDiskInfo give you SMART data that can warn you a drive is deteriorating before it causes problems. Catching a failing drive early means you can replace it on your terms rather than in a panic.

5. Avoid boot-level tools you don't understand. Registry cleaners, boot optimisers, and partition managers can all damage the BCD or EFI partition if they go wrong. The same applies to certain security tools that hook into the boot process. If something went wrong after installing one of these, that's your likely culprit. Problems like a File Explorer crash on Windows 11 can sometimes be traced back to the same dodgy optimisation tools that later cause boot issues.

Windows Boot Loop Recovery: Summary

A Windows boot loop recovery follows a clear sequence. Start with the power-cycling trick to force WinRE open. From there, Startup Repair and Uninstall Updates fix the majority of cases in under 20 minutes. If WinRE is broken, a Windows USB installer gives you the same tools. For stubborn cases, CHKDSK catches disk errors, SFC and DISM repair corrupted system files, and bootrec /rebuildbcd fixes damaged boot configuration. If the machine loops even on USB boot, suspect hardware, particularly RAM. And if all software options fail, Reset this PC with Keep my files is a reliable last resort that preserves your data. The whole process is methodical, not magic. Work through the tiers in order and you'll find the fix.