Windows 11 Stuck on Boot Logo? Here's How to Fix It (2026)
—
If Windows 11 is stuck on the spinning-dots logo or the four-color loading animation and won't move past it, the fastest fix is usually a forced restart followed by Windows' own Automatic Repair or Quick Machine Recovery tools — and if those don't clear it, booting from installation media into Advanced Startup Options to run Startup Repair or System Restore. This isn't one bug with one cause; it's what several different problems look like from the outside, so the right next step depends on what changed on your PC right before it happened and what kind of error, if any, you're actually seeing.
Start here: the safe first steps
Give it a genuine chance first. Some boot hangs resolve themselves after several minutes, especially right after a Windows update, since the system may be finishing installation work in the background. If the disk activity light is flickering, wait at least 10-15 minutes before assuming it's stuck.
If there's truly no activity and no progress:
- Hold the power button for about 10 seconds to force a shutdown.
- Power on again. If it hangs at the logo a second time, force shutdown once more, then power on a third time — after two failed boots in a row, Windows 11 normally drops into Automatic Repair on its own.
- If Automatic Repair appears, let it run. It may fix the issue directly, or it may fail and offer you Advanced Options — that's expected, and it's your entry point to the tools below.
If Automatic Repair never triggers
You'll need Windows 11 installation media — a USB drive made with Microsoft's Media Creation Tool on another PC. Boot from it (you may need to change the boot order in your PC's firmware/BIOS setup, usually by pressing a key like F2, F10, F12, Del, or Esc right after powering on — it varies by manufacturer). Choose your language, then click Repair your computer in the bottom-left corner of the setup screen, rather than Install. That takes you to the same Advanced Startup Options menu.
⚠️ What this actually breaks
System Restore and "Reset this PC" are not equally safe. Restore rolls back system files and settings to an earlier point without touching your personal files. Reset this PC's "Remove everything" option deletes your files. Always try the least destructive option first, and back up anything irreplaceable to another drive before you start if you can still access the machine at all.
Let Quick Machine Recovery try first, if you have it
On Windows 11 24H2 and later, repeated boot failures can trigger Quick Machine Recovery automatically before you do anything manual. It's available for consumers on Home or Pro starting with the August 2025 security update for 24H2 and higher, and comes enabled by default as long as the PC isn't managed by a network administrator. When your PC fails to start up multiple times, it boots into the recovery environment, connects to a network, and checks Windows Update for a fix. If a fix is found and applied successfully, the device reboots directly into Windows; if not, it drops you back into the recovery environment with the manual tools below.
If you don't see this happen automatically, you can also reach it manually: Advanced Startup Options > Troubleshoot > Advanced options > Quick machine recovery. It needs a working network connection to do anything, so it won't help if your PC can't reach Wi-Fi or Ethernet from the recovery environment.
Working through Advanced Startup Options
From Troubleshoot > Advanced options, work through these roughly in order:
1. Startup Repair
Microsoft's own diagnostic tool. It checks for missing or corrupted system files needed to boot and tries to fix them automatically. Worth running even if Automatic Repair already tried and failed once.
2. System Restore
If the hang started right after installing an update, a driver, or new software, System Restore rolls the system back to a restore point from before that change. This only works if System Protection was turned on and a restore point exists — it isn't guaranteed on every PC.
3. Uninstall the most recent update
Under Troubleshoot > Advanced options > Uninstall Updates, you can remove the latest quality update or the latest feature update separately. If the boot hang started right after Patch Tuesday, this is often faster than a full restore.
4. Command Prompt repairs
From Advanced options > Command Prompt, two commands catch a lot of boot-blocking corruption:
sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth
These need to run against the offline Windows install, so from the recovery Command Prompt you may need to check which drive letter Windows is actually on first (it's sometimes D: instead of C: in the recovery environment) — run diskpart then list volume to check, then exit diskpart before running the repair commands with the right prefix if needed.
5. Safe Mode
If you can get into Safe Mode (Advanced options > Startup Settings > Restart, then press 4), it loads Windows with only essential drivers. If it boots fine in Safe Mode, the problem is very likely a third-party driver or startup program, not core Windows — you can then uninstall a recently added driver or app from there.
If you see a BCD or "boot manager" error specifically
A black screen with a blinking cursor, or one of these specific errors, points at the boot files themselves rather than Windows generally: "Boot Configuration Data (BCD) missing or corrupted," "Boot file or MBR corrupted," "Operating system Missing," "Boot sector missing or corrupted," "Bootmgr missing or corrupted," or "Unable to boot due to system hive missing or corrupted." Microsoft's own recovery documentation gives a specific order for these — work through it in this sequence rather than jumping to the last step first.
Step 1: repair the boot codes
From Command Prompt in the recovery environment (Advanced options > Command Prompt, or Shift+F10 from the install-media Windows setup screen), run:
bootrec /fixmbr bootrec /fixboot
Neither command touches personal files. Note that fixmbr only rewrites the master boot code — if the corruption also affects the partition table, this step alone won't fully fix it.
Step 2: if you're still seeing a BCD-specific error
bootrec /scanos
This scans all disks for Windows installations not currently listed in the BCD store, then restart and check if it's fixed. If it isn't, rebuild the BCD store from scratch:
bcdedit /export c:\bcdbackup attrib c:\boot\bcd -r -s -h ren c:\boot\bcd bcd.old bootrec /rebuildbcd
The first line backs up the existing BCD before touching anything. Restart once this completes.
🕐 If bootrec still won't fix it on a UEFI PC
On some UEFI/GPT systems (the layout most modern PCs use), bootrec can fail to find the right boot path even after a rebuild, because the boot files live on the EFI System Partition rather than a classic boot sector. If that happens, a fix people commonly report working is assigning the EFI System Partition a drive letter with diskpart, then running bcdboot C:\Windows /s <that letter>: /f UEFI to recreate the boot files directly from your Windows installation. This isn't in Microsoft's own troubleshooting article as a first-line step, but it's a well-documented workaround for exactly this UEFI case.
If none of the above resolves it, Microsoft's article covers two further steps for advanced cases: replacing a corrupted Bootmgr file, and restoring the system registry hive from a restore point — both are more involved and worth attempting only after the steps above.
Stuck looping on the recovery screen itself
If the PC keeps dropping back into the recovery-options screen and won't proceed past it at all, Microsoft documents a specific command for that loop: Bcdedit /set {default} recoveryenabled no, run from Command Prompt in the recovery environment. If pressing F8 for boot options doesn't respond, follow it with Bcdedit /set {default} bootmenupolicy legacy.
If your drive is BitLocker-encrypted
⚠️ Don't skip this
You'll need your BitLocker recovery key to run Startup Repair and most other recovery steps on an encrypted device — locate it before you start. It's usually saved to your Microsoft account and reachable at aka.ms/myrecoverykey from another device, or it may be printed out or saved to a USB drive from when BitLocker was first set up.
When it's not software
If none of the repair options above even load — the recovery environment itself hangs or won't appear — treat it as a possible hardware issue rather than a Windows issue:
- Disconnect peripherals. Unplug everything except keyboard, mouse, and monitor — a failing USB device or external drive can stall boot.
- Check the drive itself. If you can access another working PC, connect the drive externally and check if it's recognized at all. A drive that isn't detected suggests failing hardware rather than a fixable software issue.
- Reseat RAM and cables on desktops, especially after any recent hardware change.
- Listen and watch. Repeated beep codes or an error before the Windows logo even appears points to a firmware/hardware fault, not a Windows boot problem — that's a different troubleshooting path (motherboard manual/manufacturer support).
Common questions
Will I lose my files?
Startup Repair, System Restore, and uninstalling an update do not delete personal files. "Reset this PC" only deletes files if you choose "Remove everything" instead of "Keep my files" — and even "Keep my files" carries some risk if the drive itself is failing, so back up first if you can.
I don't have a Windows 11 USB installer. Now what?
You'll need to create one on another working computer using Microsoft's Media Creation Tool, downloaded from Microsoft's official site, with a USB drive of at least 8 GB (it will be erased in the process).
How long should I wait before assuming it's actually stuck?
10-15 minutes with visible disk activity is reasonable, especially right after an update. No activity at all for more than a few minutes is a stronger sign something's wrong.
What is Quick Machine Recovery and do I have it?
It's a newer Windows 11 recovery feature that tries to fix boot failures automatically by checking Windows Update for a known fix, without you touching a command line. It's on by default on Home and Pro editions running 24H2 or later with the required updates, as long as the PC isn't centrally managed. If it's not kicking in, you can trigger it manually from Advanced options, but it needs a network connection to do anything.
My drive is encrypted with BitLocker — does that change anything?
Yes. You'll need your BitLocker recovery key on hand before most recovery tools will proceed. Find it ahead of time at aka.ms/myrecoverykey from another device if you don't already have it written down.
None of this worked. What's left?
If Startup Repair, System Restore, update rollback, Safe Mode, Quick Machine Recovery, and the boot-record repairs all fail, and the drive checks out on another PC, a clean reinstall (or "Reset this PC" with Remove everything) is usually the realistic next step. At that point, back up whatever files you can access first.
Revised: We have updated this guide for August 2026. This guide now covers general Windows 11 boot-hang troubleshooting, including the newer Quick Machine Recovery feature and the UEFI-specific boot-record fixes that older guides often get wrong and our earlier version pointed for specific windows insider build. If a specific error code or message appears on screen, search for that exact code — it will point you to a more targeted fix than the general steps here.