Fix Windows 11 Not Booting

Windows 11 refusing to boot is genuinely scary — all your files and settings feel out of reach. But most boot failures are recoverable without losing any data, and the fix is usually faster than people expect. The key is identifying which type of failure you’re dealing with, because “won’t boot” covers very different problems with very different solutions. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.

You see the spinning dots/logo but it never finishes loading — Windows is stuck during startup. Likely a corrupted system file, a failed driver, or a stuck update.

“Automatic Repair” screen appears — Windows detected a boot problem and is trying to fix it. Let it try once. If it loops, proceed to the fixes below.

Blue screen with an error code — The error code is your roadmap. Look it up — it usually points directly at the cause.

Blank screen, no logo — Usually a display output issue or a very early hardware failure. Check physical connections first.

Most fixes require the Windows Recovery Environment (WinRE). If the machine won’t boot normally, you can access WinRE by: turning the machine on and off 3 times during the startup animation (the machine will go into recovery), or booting from a Windows 11 USB drive and clicking “Repair your computer.”

Fix 1: Startup Repair

Startup Repair is the right first move when Windows fails to boot — it automatically scans and fixes the most common boot problems including corrupted BCD (Boot Configuration Data), missing boot files, and certain driver issues. It’s non-destructive and preserves all your data.

From WinRE: Troubleshoot → Advanced options → Startup Repair → select your Windows installation and wait. The repair runs automatically — it takes 5–15 minutes and may restart the machine multiple times. If it reports success, try booting normally. If it reports failure or can’t fix the problem, continue to the next fix.

Fix 2: Rebuild the Boot Configuration

The Boot Configuration Data (BCD) tells Windows how to find and load itself. When it becomes corrupted — which happens after interrupted updates, disk errors, or improper shutdowns — Windows can’t start even though the installation itself is fine. Rebuilding it from WinRE Command Prompt takes about two minutes:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Run these four commands in order from WinRE → Troubleshoot → Advanced options → Command Prompt. The last command (/rebuildbcd) will ask whether to add found Windows installations to the boot list — type Y and press Enter. Restart and test booting normally.

If bootrec /fixboot returns “Access is denied”: run diskpart → list vol → identify the EFI partition (usually a small FAT32 partition) → sel vol [number] → assign letter=v: → exit → then run bcdboot C:Windows /s v: /f UEFI. This assigns the boot manager to the EFI partition correctly.

Fix 3: Safe Mode to Isolate the Cause

Safe Mode loads Windows with minimal drivers and no third-party services. If Windows boots successfully in Safe Mode but not normally, the cause is a driver, service, or startup program rather than a fundamental system problem — which narrows down the fix considerably.

From WinRE: Troubleshoot → Advanced options → Startup Settings → Restart → press 4 (Safe Mode) or 5 (Safe Mode with Networking).

Once in Safe Mode:

• Roll back the most recently updated driver (Device Manager → find any recently updated device → Properties → Driver → Roll Back)
• Disable startup programs (Task Manager → Startup apps → disable High impact items)
• Run SFC: sfc /scannow in admin Command Prompt
• Uninstall any recently installed software that appeared around when booting stopped working

Fix 4: Run SFC and DISM Offline

Corrupted system files prevent Windows from completing startup. Running SFC and DISM from the recovery environment (rather than within Windows) can fix files that are locked during normal operation and therefore can’t be repaired while Windows is running.

From WinRE Command Prompt, first identify your Windows drive letter:

diskpart
list vol
exit

Look for the volume with a Windows folder — it might be C:, D:, or another letter in the recovery environment. Then run:

sfc /scannow /offbootdir=C: /offwindir=C:Windows
DISM /Image:C: /Cleanup-Image /RestoreHealth

Replace C: with whatever drive letter Windows is on. Let both commands complete — they take 15–30 minutes. Restart and test.

Fix 5: Roll Back a Windows Update

If boot failure started immediately after a Windows Update — and many do — uninstalling the problematic update often resolves it without any other intervention.

From WinRE: Troubleshoot → Advanced options → Uninstall Updates → Uninstall latest quality update (try this first) or Uninstall latest feature update. After uninstalling, the machine restarts and loads the previous update state. Check whether it now boots normally.

Fix 6: System Restore

System Restore returns Windows to a previous state including registry settings, driver configurations, and system files — without touching personal files. It’s the right fix when a software change (update, new application, driver) caused the boot failure and you know approximately when it started working.

WinRE → Troubleshoot → Advanced options → System Restore → follow the wizard → choose a restore point dated before the boot problems started. The restore takes 10–20 minutes and may restart multiple times.

Fix 7: Reset This PC (Keeps Your Files)

When the above fixes don’t resolve the boot failure, resetting Windows reinstalls the operating system while keeping personal files. It removes installed applications and settings, but your documents, photos, and files in user folders are preserved.

WinRE → Troubleshoot → Reset this PC → Keep my files → choose either Cloud download (downloads a fresh Windows copy) or Local reinstall (uses recovery files on the drive). Cloud download is more thorough but requires a recovery network connection during WinRE (safe mode with networking or Ethernet).

Hardware Causes to Check

Some boot failures aren’t software problems at all. Before spending time in WinRE, verify these hardware factors:

• New hardware recently installed — Remove any newly added RAM, storage drives, or expansion cards and try booting. New components are a common trigger for boot failures that look like software problems.
• Loose connections — On desktops, open the case and press firmly on RAM sticks and storage cables. Vibration over time loosens these.
• BIOS boot order — Ensure the correct drive is first in the BIOS boot order. BIOS updates sometimes reset this to boot from USB or network first.
• Failing storage drive — If the drive is failing, boot problems will recur no matter what software fixes are applied. Test drive health with manufacturer diagnostic tools (Seagate SeaTools, WD Dashboard, Samsung Magician) from a USB boot environment.

BitLocker Recovery Screen

If the machine shows a blue screen asking for a BitLocker recovery key — this isn’t a system failure. BitLocker detected that the boot environment changed (often after a BIOS update or hardware change) and is requiring the recovery key as a security measure before unlocking the drive.

Find the recovery key: for personal Microsoft accounts, visit account.microsoft.com/devices/recoverykey. For corporate accounts, IT has the key in Active Directory. Enter the key and Windows boots normally. After recovering, go to Settings → Privacy and security → Device encryption and confirm the encryption status is correct.

Rescuing Data Before a Clean Install

If all recovery options fail and a clean install becomes necessary, data can often still be recovered from the drive. From WinRE Command Prompt, type notepad.exe — Notepad’s File → Open dialog lets you browse and copy files from the Windows partition to a USB drive. This works even when Windows itself won’t load. Copy Documents, Pictures, Downloads, and Desktop before wiping and reinstalling.

Our guide on Windows 11 black screen covers the display-related failures that look like boot problems but are actually display driver issues — they share several WinRE fixes. For the update-specific failures where Windows installed an update and then stopped booting, our Windows Update troubleshooting guide covers the update installation issues that precede these failures. Microsoft’s Windows 11 recovery documentation covers the full WinRE toolset including the advanced driver recovery options not covered here.

Stop Codes and What They Mean

When Windows shows a blue screen with a stop code before or during boot, the code is the most direct diagnostic clue available. Common boot-related stop codes:

For INACCESSIBLE_BOOT_DEVICE specifically: this code often appears after a BIOS update that changed the storage mode from AHCI to RAID (or vice versa). Check BIOS → Storage Configuration → confirm the mode matches what Windows was installed with. Changing it back usually resolves this particular stop code immediately.

Automatic Repair Loop

The Automatic Repair loop — where Windows attempts repair, restarts, and attempts repair again indefinitely — is one of the more frustrating boot scenarios because it appears to be doing something while actually making no progress. The loop typically means either the repair can’t fix the underlying problem (needs manual intervention) or the repair itself has an issue.

Break the loop by interrupting the startup process deliberately three times in a row (hold the power button during the spinning dots animation). On the third failed boot, Windows presents the “Choose an option” menu with access to Troubleshoot and Advanced options. From here, access Command Prompt and run the BCD rebuild (Fix 2) or SFC offline (Fix 4), which often fixes the problem that the automatic repair couldn’t.

If the loop persists even after BCD rebuild and SFC: check the System event log from WinRE Command Prompt by running wevtutil qe System /c:20 /rd:true /f:text. This shows the last 20 system events and often reveals the specific service or driver that’s failing during startup, which points directly at the fix that automated tools missed.

UEFI and Secure Boot Considerations

Windows 11 requires UEFI firmware with Secure Boot enabled. If Secure Boot gets disabled — through a BIOS update that resets settings, through manual BIOS changes, or through a hardware replacement that changes the measured boot environment — Windows may refuse to boot.

Check Secure Boot status in BIOS (usually in the Boot or Security section). If it’s disabled, re-enabling it and restarting often resolves the boot failure immediately, provided the Windows installation was originally configured for Secure Boot. If Secure Boot was always disabled and Windows was installed that way, enabling it may cause a different boot failure — don’t change it on a working system, only re-enable it if it was recently disabled.

Also check the BIOS Boot Mode setting — it should be set to UEFI (not Legacy/CSM). Windows 11 requires UEFI mode, and switching from Legacy to UEFI in BIOS on a machine that was using Legacy boot will cause an immediate boot failure that the BCD rebuild alone can’t fix.

Third-Party Antivirus and Boot Drivers

Antivirus products that install boot-level drivers — products like Kaspersky, Bitdefender, and some endpoint protection suites — load very early in the boot process, before the Windows desktop appears. When these drivers conflict with a Windows update or become corrupted, they can block Windows from completing startup.

From Safe Mode, uninstall the antivirus using its own uninstaller (not just Add/Remove Programs — antivirus products usually have a dedicated removal tool available on their support site). If Safe Mode access is also blocked, boot from WinRE and use the System Restore option to return to a point before the antivirus was installed or last updated. After resolving the boot problem, reinstall the antivirus fresh from the vendor’s current release.

When the Drive Is the Real Problem

Recurring boot failures that resolve temporarily then return — or boot failures accompanied by unusual clicking sounds, very slow file access, or SMART errors in disk diagnostic tools — point to a failing storage drive rather than a software problem. In these cases, fixing the boot configuration provides temporary relief but the underlying drive failure will cause the problem to recur.

If drive failure is suspected: back up data immediately using the WinRE notepad trick described earlier, or boot from a Linux USB drive (Ubuntu live USB) which can access Windows drives and copy files to external storage. Run the drive manufacturer’s diagnostic tool to confirm health status — most drives show SMART indicators of failure well before they completely stop working, and a failing drive’s data is still accessible and copyable until the very end stages of failure. Related: Chrome Bookmark Bar Disappeared.