Windows 11 boot loop or automatic repair: the WinRE order that works
A calm recovery sequence for a Windows 11 boot loop: firmware, BitLocker, WinRE startup repair, uninstall updates, restore point, command prompt and reinstall.
- Build
- 26300.9457
- Edition
- Pro (26H2)
- Architecture
- x64
- Support
- Documentation (E1)
- Evidence
- E1Official documentation
- Verified
- 2026-10-28
- Page type
- Troubleshoot
The short answer
Section titled “The short answer”A boot loop is not one problem. Separate:
- Firmware/boot device — does the firmware see the disk?
- BitLocker — is it asking for a recovery key?
- Windows boot manager — does WinRE load?
- Recent change — update, driver, partition, overclock?
- Hardware — disk errors, RAM, overheating?
Work in that order. Do not reinstall before you know which layer failed.
Before WinRE
Section titled “Before WinRE”- Disconnect unnecessary USB devices, docks and external drives.
- Check the firmware boot order and whether the internal disk is detected.
- If BitLocker prompts, enter the recovery key; do not “fix” it by clearing the TPM.
- If you overclocked/undervolted, load defaults.
- If the case was opened, check RAM/GPU seating.
Enter WinRE
Section titled “Enter WinRE”Boot the Windows USB or use Settings → System → Recovery → Advanced startup → Restart now. Then:
Troubleshoot → Advanced options
| Order | Tool | Use when |
|---|---|---|
| 1 | Startup Repair | Boot files/driver change suspected |
| 2 | Uninstall Updates | Loop started after an update |
| 3 | System Restore | A restore point exists before the change |
| 4 | Command Prompt | You need logs/BCD/disk checks |
| 5 | Reset this PC | Windows is unrecoverable, files backed up |
| 6 | Reinstall | Disk/partition/OS is beyond repair |
Symptom → first move
Section titled “Symptom → first move”| Symptom | First move | Do not |
|---|---|---|
| Firmware does not list the disk | Check cable/BIOS/NVMe seating | Reinstall Windows first |
| BitLocker recovery prompt | Enter the recovery key | Clear the TPM |
| “Preparing automatic repair” loop | Startup Repair / uninstall latest update | Run every bootrec switch |
| Boots after several tries | Check disk/RAM and recent driver | Ignore it as “random” |
| Blue screen with a stop code | Note the code, boot safe mode, remove the change | Reset before reading the code |
| No display but fans spin | Check GPU/output/cable, try iGPU | Assume Windows is corrupt |
Data rescue before repair
Section titled “Data rescue before repair”If the disk is healthy but Windows will not boot, copy important files before resetting:
- Boot a Linux live USB or WinRE command prompt.
- Mount the volume read-only if possible.
- Copy to an external disk; verify one file opens.
- Only then try reset/reinstall.
If BitLocker is active, unlock the volume first; a live Linux environment cannot read it without the key.
Command Prompt checks
Section titled “Command Prompt checks”diskpartlist disklist volumeexitchkdsk C: /scansfc /scannow /offbootdir=C:\ /offwindir=C:\Windowsbootrec /scanosbootrec /fixmbr and /fixboot are legacy/BIOS tools; on UEFI, prefer Startup Repair and bcdboot only when you know the ESP layout. Do not run bootrec /rebuildbcd blindly on a multi-boot disk.
If Windows starts
Section titled “If Windows starts”- Read Event Viewer → System around the first failure.
- Check Reliability Monitor for the driver/app installed before the loop.
- Uninstall the recent update/driver from Settings if it boots in safe mode.
- Run
DISM /Online /Cleanup-Image /RestoreHealthandsfc /scannow. - Make a restore point and a backup before the next change.
If it is hardware
Section titled “If it is hardware”A disk that disappears from firmware, clicks, or throws disk errors in Event Viewer is not a Windows bug. Back up immediately, replace the disk, and reinstall. A RAM instability can also cause random boot loops; run a memory test if the loop is intermittent.