Windows 11 Stuck on the Boot Logo? Fixes in Order (Spinning Dots, Dell/HP Logo, Boot Loop)

Logeshwaran
—

If Windows 11 is stuck on the boot logo, the spinning dots under the Windows logo or your PC maker's logo, first wait 20 to 30 minutes if an update was installing, then unplug every USB device except keyboard and mouse and restart. If it still hangs, force the PC off three times during startup (hold the power button about 10 seconds each time); on the next start Windows opens Automatic Repair, and on recent Windows 11 PCs Quick Machine Recovery may fix it by itself. From there, choose Advanced options and try, in order, Startup Repair, Uninstall Updates, System Restore and Safe Mode. If the PC stops on the maker's logo (Dell, HP, Lenovo and so on) before Windows starts, the problem is firmware or hardware, not Windows. Boot-record repair commands come last, and on modern UEFI PCs the right one is bcdboot, not bootrec /fixboot.

Ethan's laptop restarted for a Windows update on a Tuesday night and was still on the logo with spinning dots the next morning. He held the power button, it came back to the same logo, and he called Jake before trying anything else, which was the right call. Jake unplugged the USB dock, which on its own got the laptop as far as a blue Automatic Repair screen, then used Uninstall Updates to remove the update that had been installing. The laptop started normally ten minutes later, files intact. The dock's firmware turned out to be the trigger, and a dock update the next day fixed it for good. This page goes through every cause of a PC stuck on the boot logo, in the order that fixes most PCs fastest, for Windows 11 and Windows 10.

⚡ Quick Answer

• First → wait if updating, unplug USB devices, restart. First steps.

• Get to recovery → force off three times, then Advanced options. Recovery.

• Fix order → Startup Repair, Uninstall Updates, System Restore, Safe Mode. The ladder.

• Maker's logo only? → firmware or hardware, not Windows. Maker's logo.

Boot record errors on UEFI PCs need bcdboot, not bootrec /fixboot. Boot record.

🧭 NEW HERE? READ THESE FIRST

New here? These five pages pair with this one:

📌 Read one now, or bookmark this page and come back to it.

Which logo are you stuck on? It decides the fix

"Stuck on the boot logo" describes two very different problems, and telling them apart takes one look at the screen.

The PC maker's logo, such as Dell, HP, Lenovo, ASUS, Acer or the motherboard maker's logo on a self-built PC, often with no spinning dots, belongs to the firmware, the BIOS or UEFI. At that moment Windows has not started yet. If the PC stops there, the problem is in the firmware settings, the hardware, or a connected device, and Windows repair tools cannot help until it gets past that point. On many modern PCs the maker's logo stays on screen while Windows starts, with Windows' spinning dots appearing beneath it, so look for the dots.

The spinning dots, below the Windows logo or below the maker's logo, mean Windows itself is loading. If the dots keep spinning, Windows has started but cannot finish, usually because of an update, a driver, a damaged system file, a disk problem or a device that is not responding. These are the cases the Windows recovery tools are built for, and most of this page.

A third look is the black screen with a cursor after the logo, or a restart loop where the logo appears again and again. Restart loops after updates have their own guide, update stuck at 100% or restart loop, and a PC that turns off by itself right after starting is covered in PC turns on then shuts down. If your screen matches neither, keep reading.

What you seeWhat it meansWhere to start
Maker's logo, no dots, nothing happensFirmware stage; Windows not startedUnplug devices, firmware checks, hardware
Logo with spinning dots for a few minutes after an updateWindows finishing an updateWait up to 30 minutes
Logo with spinning dots for hoursWindows cannot finish startingUnplug devices, then recovery
Logo, then restart, logo againBoot loopRecovery: Uninstall Updates, Startup Repair
Logo, then black screen with cursorWindows started, desktop did not loadSafe Mode, display driver
Blue screen with a stop codeA crash during startupNote the code, then recovery

First steps: wait, unplug, restart

Before any repair tool, three simple steps fix a surprising share of stuck PCs. Wait, if the PC was installing an update. Windows can show the logo and spinning dots for 10 to 30 minutes while it completes a large update, and on slow hard drives longer. If the drive activity light is flickering, Windows is working. Interrupting it mid-update is the most common way a slow boot becomes a broken one, so give it half an hour before you act.

Unplug everything except the keyboard and mouse: USB drives, external hard drives, phones, card readers, printers, docks, game controllers and USB hubs. Some devices, especially external drives and docks, can make Windows wait at startup, or make the firmware try to start from the wrong drive. Remove any disc from an optical drive and any memory card from a card slot. This was the whole problem on Ethan's laptop: the dock was holding up startup.

Restart with a long press: hold the power button for about 10 seconds until the PC is completely off, wait a few seconds, and start it again. A full power cycle clears temporary hardware states that a soft restart may not. On a laptop that still hangs, unplug the charger too; on some models with a removable battery, take it out for a minute. If the PC now starts, plug devices back one at a time on later restarts to find the one responsible.

Two small signs tell you whether the PC is frozen or just slow. If the Caps Lock key light turns on and off when you press it, the PC is still responding at a basic level, and waiting a little longer is reasonable. If the drive activity light flickers, Windows is reading or writing, which means work is happening. A PC with no response to Caps Lock and no drive activity for ten minutes is stuck, and it is time to move on to recovery rather than wait longer.

Get into the Windows Recovery Environment

When Windows cannot start, it is designed to open its recovery tools by itself after two failed starts in a row. You can trigger that deliberately when the PC hangs on the logo:

  1. Start the PC. When the logo appears with spinning dots, hold the power button for about 10 seconds until it turns off.
  2. Repeat that two more times.
  3. On the next start, Windows shows Preparing Automatic Repair or Diagnosing your PC, then a blue Automatic Repair screen.
  4. Select Advanced options to open the recovery menu, called the Windows Recovery Environment.

If Automatic Repair runs and says it could not repair the PC, that is normal and not the end; select Advanced options from that screen. If forcing the PC off three times does not bring recovery up, start from a Windows installation USB made on another PC with Microsoft's Media Creation Tool, choose your language, then select Repair your computer at the bottom left instead of Install now. That opens the same recovery tools from the USB drive. Our guide to advanced startup lists every way into recovery, including from a PC that still starts.

If the PC uses BitLocker or device encryption, recovery may ask for the BitLocker recovery key before you can use some tools. The key is usually saved in your Microsoft account; on another device, sign in at the Microsoft account recovery key page to find it. Our guide to BitLocker asking for a recovery key explains where else it may be. Have it ready before you start, since several repair tools need the drive unlocked. If you cannot find it anywhere, do not reset the PC in a hurry: without the key, a reset or reinstall can make the encrypted files unrecoverable, so search every account and printout first.

Quick Machine Recovery: when Windows fixes itself

On recent Windows 11 PCs, the recovery environment can also try Quick Machine Recovery. When a PC fails to start, recovery can connect to the internet, check with Windows Update for a known fix for a widespread startup problem, and apply it automatically. It was introduced after large-scale boot failures showed how hard it is to fix thousands of PCs one at a time, and on home PCs it is generally on by default, while organizations can manage it.

In practice, this means that if your PC hangs on the logo because of a known bad update or driver affecting many PCs, it may fix itself on the next attempt with no action from you, given a network connection. Leave the PC connected by Ethernet or to a known Wi-Fi network if recovery offers it. If the problem is unique to your PC, such as a failing disk, Quick Machine Recovery will not find a fix and recovery continues to the normal options. Our Quick Machine Recovery guide explains how it works and how to check its settings once the PC starts again.

Quick Machine Recovery does not replace the manual steps; it runs first and, if it finds nothing, hands back to the normal recovery options. It needs a working network connection from inside recovery, which wired Ethernet provides most reliably, so if your laptop has no Ethernet port and recovery cannot join Wi-Fi, expect to go straight to the manual ladder below.

The repair ladder: try these in order

In the recovery menu, select Troubleshoot, then Advanced options. You will see several tools. Use them in this order, which goes from safest and fastest to more drastic, and restart after each to see if the PC now starts.

1. Startup Repair. It scans for common startup problems, such as damaged boot files or startup settings, and fixes them automatically. It takes a few minutes. It cannot fix everything, and often reports that it could not repair the PC, but when it works it is the least disruptive fix.

2. Uninstall Updates. If the problem started right after an update, as it did for Ethan, choose Uninstall latest quality update for a monthly update, or Uninstall latest feature update for a version upgrade. Your files and apps stay. Windows may reinstall the update later, by which time a fixed version is often available; if the same update breaks it again, pause updates for a few weeks once the PC starts. Our guide to uninstalling a Windows update covers doing this from a working PC too.

3. System Restore. If restore points exist, this returns system files, drivers and settings to an earlier point while keeping your documents and photos. Choose a restore point from before the problem began. Apps installed after that point will need reinstalling. System Restore must have been turned on beforehand; on many PCs it is on for drive C: by default, but not on all.

4. Startup Settings and Safe Mode. Select Startup Settings, then Restart, and press 4 for Safe Mode or 5 for Safe Mode with Networking. Safe Mode starts Windows with a minimal set of drivers. If it starts, the cause is a driver or startup program; from Safe Mode you can uninstall a recently added driver or program, roll back a display driver, or run the repairs in the next sections. Our guide to Safe Mode covers what to do once you are in. The same menu has Enable low-resolution video, a quick test for display driver problems, and Disable driver signature enforcement and Disable early launch anti-malware protection, which can help identify a problem driver or security product, but should only be used for one start as a diagnostic.

5. Command Prompt repairs. If none of the above work, the Command Prompt in recovery can check the disk, repair system files and rebuild the boot files, covered in the next two sections.

6. Reset or reinstall. The last resort, covered at the end, with options that keep your files.

This table summarizes the tools in the recovery menu, so you can see at a glance what each risks and how long it takes.

Recovery toolWhat it doesKeeps your files?Keeps apps?Typical time
Startup RepairFixes common startup problems automaticallyYesYes5 to 20 minutes
Uninstall UpdatesRemoves the latest quality or feature updateYesYes5 to 15 minutes
System RestoreReturns system files and drivers to a restore pointYesApps added after the point are removed15 to 45 minutes
Startup Settings (Safe Mode)Starts Windows with minimal driversYesYesA few minutes
Command PromptDisk, file and boot repairs by handYes, if used carefullyYesVaries
Reset this PC, Keep my filesReinstalls WindowsYesNo1 hour or more

Check the disk and repair system files from recovery

A damaged file system or damaged Windows files can stop Windows partway through starting. From Advanced options, open Command Prompt. In recovery, drive letters can differ from normal; first find your Windows drive by typing dir C:\Windows, and if that fails, try dir D:\Windows and so on until you see the Windows folder. Use that letter in the commands below; the examples assume C:.

To check and repair the disk's file system, run chkdsk C: /f. On a large hard drive it can take a long time; on an SSD it is usually quick. If it reports and fixes errors, restart and try a normal start. To scan for bad sectors as well, chkdsk C: /r takes much longer and is worth it on a hard drive that is making unusual noises or that you suspect is failing.

To repair Windows system files without starting Windows, run the System File Checker in offline mode: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows. It compares system files to known good copies and replaces damaged ones. If it reports that it found corrupt files and repaired them, restart. If it cannot repair some files, DISM can repair the component store first, but offline DISM needs a source such as a Windows installation USB, which makes it a more advanced step. Our guide to opening Command Prompt when Windows will not start covers these commands and more in detail.

Stop codes during startup and what they point to

Sometimes the logo gives way to a blue screen with a stop code before the PC restarts. Writing the code down, or photographing the screen with your phone, saves a lot of guessing, because each common code points to a different kind of cause. INACCESSIBLE_BOOT_DEVICE means Windows lost access to the drive it starts from, often after a storage driver change, a firmware setting change such as switching between AHCI and RAID, or a failing drive; our INACCESSIBLE_BOOT_DEVICE guide covers it.

UNMOUNTABLE_BOOT_VOLUME points to file system damage or a failing drive, so chkdsk is the first step. BAD_SYSTEM_CONFIG_INFO suggests damage to the registry's system settings, where System Restore is often the quickest fix. CRITICAL_PROCESS_DIED means a core Windows process failed, often from damaged system files or a bad driver, so offline sfc and Uninstall Updates are good starts. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and DRIVER_IRQL_NOT_LESS_OR_EQUAL usually name or imply a driver; display and network drivers are common culprits, and Safe Mode lets you roll them back.

If the screen names a file, such as a .sys driver file, search for that file name to identify the driver and its maker. A recently installed driver or security product named on the blue screen is very likely the cause, and uninstalling or rolling it back from Safe Mode usually ends the hangs.

Repair the boot record on UEFI and older PCs

If Startup Repair fails and you see messages about the boot configuration data, a missing boot manager, or an error code mentioning BCD, the boot files themselves may be damaged. Many guides tell you to run bootrec /fixmbr, bootrec /fixboot and bootrec /rebuildbcd. On modern PCs, which almost all use UEFI firmware with a GPT disk, bootrec /fixboot often fails with "Access is denied", and the MBR command does not apply. The reliable repair on UEFI PCs is to rebuild the boot files with bcdboot.

  1. In the recovery Command Prompt, type diskpart, then list vol. Find the small FAT32 partition of around 100 to 300 MB, labeled System or with no label; that is the EFI system partition. Note its volume number.
  2. Type sel vol N using that number, then assign letter=S, then exit.
  3. Run bcdboot C:\Windows /s S: /f UEFI, using your Windows drive letter. It should report that boot files were successfully created.
  4. Close Command Prompt, select Continue to exit recovery, and start Windows.

On older PCs that use legacy BIOS with an MBR disk, the bootrec commands are the right ones. To check which you have, run diskpart, then list disk: a star in the Gpt column means a GPT disk, which almost always means UEFI. Use the repair that matches; mixing them up is the most common reason these repairs fail.

Boot record repairs are safe when typed carefully, but they write to the system partition, so double-check the volume number in diskpart before assigning a letter, and never format or delete partitions from recovery unless you intend to reinstall. If any step reports an error you do not understand, stop there and note the message; continuing with guesses is how a fixable boot problem becomes a lost partition. The Reset this PC option further down is a safer fallback than experimenting.

Stuck on the Dell, HP or Lenovo logo: firmware and hardware

If the PC stops on the maker's logo without Windows' spinning dots, Windows is not involved yet, and the fixes are different. Start with the same unplugging and full power cycle as above, since a single faulty USB device can stop the firmware. Then check whether you can enter the firmware setup, usually by pressing F2, Delete, F10 or F12 as the logo appears; the logo screen or the maker's manual says which. If you can, the firmware itself works.

In the firmware setup, check that the boot order lists the drive with Windows first, often shown as Windows Boot Manager, and that the drive is detected at all. If the drive is missing from the firmware's list, the problem is the drive or its connection; on a desktop, reseat the drive's cables, and on any PC, consider that the drive may be failing. If settings look wrong after a power cut or battery problem, choose Load default settings or Load optimized defaults, save and exit.

If the PC will not even enter firmware setup, the cause is hardware or firmware: memory, the graphics card, the motherboard, or a firmware update that failed. On desktops, reseat the memory modules and the graphics card, and try starting with one memory module at a time. Many PCs give clues through beep codes or blinking lights on the power button or caps lock key; the maker's support site explains what each pattern means. Dell, HP and Lenovo all have built-in hardware diagnostics, usually started with a key such as F12 or F2 at the logo, that test memory, drives and more without Windows. If those fail, contact the maker's support, especially while under warranty.

Laptops: extra checks when the logo will not move

Laptops have a few causes and cures of their own. A full power drain resets the embedded controller that manages power and the keyboard: unplug the charger, hold the power button for 30 seconds, then plug in and start again. Some laptops have a small reset pinhole on the bottom, which does the same for models with a sealed battery; the maker's manual shows where it is. Several makers also have a recovery button or key combination that opens a menu at startup, useful when the normal function keys do not respond.

A laptop that hangs only when docked, as Ethan's did, or only with an external monitor attached, points to the dock, its firmware, or the graphics switching between the built-in and external displays. Start without the dock, update the dock's firmware and the laptop's graphics and Thunderbolt or USB-C drivers from the maker, and then reconnect. A laptop that hangs when the battery is very low can simply lack the power to finish starting; leave it on the charger for half an hour before trying again.

Desktop PCs: graphics, memory and firmware reset

On a desktop, especially one you built or upgraded, hardware is a more common cause than on a laptop. If the PC has a separate graphics card and the screen stays on the logo or goes black, connect the monitor to the motherboard's own video output instead, if the processor has built-in graphics, and remove the graphics card for a test. If the PC starts that way, the card, its power cable or its driver is the problem. Reseat the card firmly and check its power connectors before concluding it has failed.

Memory is the next suspect. Remove all but one memory module, start the PC, and try each module in turn; a single faulty module can stop a PC at the logo. If you recently changed memory or enabled a memory overclocking profile, return to the default settings. Finally, a firmware reset, often called clearing CMOS, returns all firmware settings to defaults: use the Clear CMOS button or jumper described in the motherboard manual, or, with the PC unplugged, remove the small coin battery for a few minutes. Afterward, set the date and time and check the boot order before starting Windows.

Common causes, and how to prevent the next one

Most stuck-logo cases trace back to a small number of causes. Updates interrupted or gone wrong are the most common, which is why Uninstall Updates is near the top of the ladder. USB devices and docks come next, especially docks with their own firmware and external drives that the PC tries to start from. Drivers, particularly graphics, storage and security software drivers, can hang startup after an update. Disk problems, from file system damage after a power cut to a failing drive, cause slow and failed starts. And firmware settings or failed firmware updates cause stops at the maker's logo.

Prevention follows from that list. Let updates finish; do not hold the power button while Windows shows "Working on updates". Keep the PC plugged in during updates on laptops. Update dock, firmware and storage drivers from the PC maker, since these are often what conflicts with a new Windows version. Keep System Restore turned on for drive C:, so there is always a restore point. And keep backups of your files, so that if the last resort, a reset, is ever needed, it costs you an hour, not your photos.

Once it starts again: find the cause

Getting the PC to start is half the job; the other half is making sure it does not happen again next week. Open Reliability Monitor by typing perfmon /rel in the Run box. It shows a timeline of failures, updates and installations, and the day the PC got stuck usually stands out with a red mark and the name of what failed. In Event Viewer, under Windows Logs, System, errors around the failed start, especially from disk, driver or service sources, point to the cause.

Then check the drive's health. In PowerShell, Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus shows whether Windows considers each drive healthy, and the drive maker's free tool gives more detail. A drive reporting warnings should be backed up immediately and replaced. Finally, update the PC's firmware, chipset, storage and graphics drivers from the maker's support page, and update any dock firmware; these are the updates Windows Update does not always deliver, and they are behind many repeat failures.

Make a recovery drive before you need one

The hardest stuck-logo cases are the ones where recovery itself will not open and there is no other PC handy to make a Windows USB. A recovery drive, made in advance, solves that. Search the Start menu for Create a recovery drive, insert a USB drive of at least 16 GB, which will be erased, and follow the steps; checking the option to back up system files lets the drive reinstall Windows if needed. Label it and keep it with the PC's paperwork.

Alternatively, Microsoft's Media Creation Tool makes a Windows installation USB that also opens the recovery tools through Repair your computer. Either one turns a PC that will not start into a twenty-minute job instead of a trip to a repair shop. Jake keeps one installation USB in his bag for exactly this reason, and it was what he would have used next if unplugging Ethan's dock had not been enough.

Last resort: reset or reinstall without losing files

If nothing on the ladder works, Windows can be reset or reinstalled while keeping your personal files. In recovery, select Troubleshoot, Reset this PC, then Keep my files. Choose Cloud download to fetch a fresh copy of Windows from Microsoft, which avoids damaged local files, or Local reinstall to use the files already on the PC. Your documents and other personal files stay; apps and settings are removed, so you will reinstall your programs afterward. A list of removed apps is saved to the desktop.

A reset can take an hour or more. If the reset itself fails, the remaining options are to reinstall Windows from a USB drive, choosing to keep files if the installer offers it after starting from within Windows, which is not possible on a PC that will not start, or to do a clean installation after copying your files off the drive. To rescue files from a PC that will not start, open Command Prompt in recovery and use notepad, whose File, Open dialog works as a simple file browser for copying files to a USB drive, or remove the drive and connect it to another PC with a USB adapter. If the files matter and nothing else works, a professional data recovery service is safer than repeated attempts on a failing drive.

Stuck on the boot logo in a virtual machine

Windows 11 in a virtual machine, such as Hyper-V, VMware, VirtualBox or Proxmox, can hang on the boot logo for reasons specific to virtualization. The most common are a missing or unsupported virtual TPM or Secure Boot setting after an update, a virtual CPU type that lacks instructions Windows 11 24H2 and later require, and storage or network drivers that do not match the virtual hardware. Check the virtual machine's firmware settings for TPM and Secure Boot, set the CPU type to pass through the host's processor features where the hypervisor allows it, and make sure the hypervisor's guest tools or drivers are current.

Snapshots make VMs easier to fix than physical PCs: if the VM was fine before an update, revert to a snapshot from before it, then pause updates or update the hypervisor first. The recovery steps on this page also work inside a VM, including forcing it off three times to reach Automatic Repair, by resetting the VM from the hypervisor's console.

Windows 10: what is different

Everything on this page works on Windows 10 as well, with two differences. Windows 10 does not have Quick Machine Recovery, so a widespread bad update must be removed with Uninstall Updates or System Restore rather than fixed automatically. And Windows 10 reached end of support in October 2025; home PCs enrolled in Extended Security Updates still receive security updates until October 2027, and those updates can occasionally cause startup problems too, so the same ladder applies.

If a Windows 10 PC gets stuck on the logo repeatedly and the hardware is supported, moving to Windows 11 is worth considering once it starts again, since newer versions have stronger recovery features. If the hardware is not supported, keep it enrolled in ESU, keep its drivers current, and keep a recovery drive handy.

Some people searching for the boot logo want to change it rather than get past it. Windows does not offer a setting to change the startup logo. On most modern PCs, the logo shown during startup is the PC maker's logo stored in the firmware, with Windows' spinning dots beneath it. Some motherboard makers offer tools to replace the firmware logo, and third-party tools exist that change it by modifying startup files, but they can conflict with Secure Boot and firmware updates, and a mistake can stop the PC from starting, which is the very problem this page is about. On a PC you depend on, leave the boot logo alone; personalize the lock screen and sign-in screen instead, which Windows supports.

Frequently asked questions

How do I fix Windows 11 stuck on the boot logo?

Wait up to 30 minutes if an update was installing, unplug all USB devices and restart. If it still hangs, force the PC off three times to open Automatic Repair, then try Startup Repair, Uninstall Updates, System Restore and Safe Mode in that order.

How long should I wait on the Windows loading screen?

After an update, up to 30 minutes, longer on slow hard drives, especially if the drive light is flickering. Without an update, a normal start takes under a minute or two; if it hangs much longer, something is wrong.

How do I get to Automatic Repair if Windows will not start?

Hold the power button about 10 seconds to turn the PC off while the logo shows, three times in a row. On the next start Windows opens Automatic Repair; select Advanced options. Or start from a Windows installation USB and choose Repair your computer.

Why is my PC stuck on the Dell, HP or Lenovo logo?

If there are no Windows spinning dots, Windows has not started. Unplug devices, power cycle, check the firmware boot order and whether the drive is detected, load default firmware settings, and run the maker's hardware diagnostics.

Why is Windows 11 stuck on the boot screen after an update?

The update did not finish or conflicts with a driver or device. Wait, unplug devices, then use Uninstall latest quality update or feature update in recovery. Quick Machine Recovery may fix known widespread update problems automatically.

What is Quick Machine Recovery?

A Windows 11 recovery feature that, when a PC cannot start, connects to Windows Update from recovery to find and apply known fixes for widespread startup problems automatically.

How do I fix a Windows 11 boot loop?

Use recovery's Uninstall Updates first if it began after an update, then Startup Repair and System Restore. Our guide to update restart loops covers loops that happen during an update.

Does bootrec /fixboot work on Windows 11?

Often not on UEFI PCs, where it returns Access is denied. Assign a letter to the EFI system partition with diskpart and run bcdboot C:\Windows /s S: /f UEFI instead. Bootrec suits older legacy BIOS PCs with MBR disks.

How do I boot into Safe Mode when Windows is stuck on the logo?

Open recovery by forcing the PC off three times, then Troubleshoot, Advanced options, Startup Settings, Restart, and press 4 for Safe Mode or 5 for Safe Mode with Networking.

Will Startup Repair delete my files?

No. Startup Repair, Uninstall Updates, System Restore and Safe Mode keep your personal files. System Restore removes apps installed after the restore point but not documents or photos.

Can a USB device stop Windows from booting?

Yes. Docks, external drives, hubs and other USB devices can make startup hang or make the firmware try to start from the wrong drive. Unplug everything except keyboard and mouse and restart.

How do I run chkdsk if Windows will not start?

Open Command Prompt from recovery, find your Windows drive letter with dir C:\Windows, and run chkdsk C: /f, or /r on a hard drive you suspect is failing.

How do I run sfc when Windows will not boot?

From the recovery Command Prompt, run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows, using your Windows drive letter.

My PC asks for a BitLocker recovery key. What now?

The key is usually in your Microsoft account; sign in to the recovery key page on another device to find it. Enter it to unlock the drive and continue with the repairs.

How do I reset Windows if it will not start?

In recovery, choose Troubleshoot, Reset this PC, Keep my files, and Cloud download or Local reinstall. Personal files stay; apps and settings are removed.

How do I get my files off a PC that will not boot?

Use the File, Open dialog of Notepad from the recovery Command Prompt to copy files to a USB drive, or remove the drive and connect it to another PC with a USB adapter.

Why is my Windows 11 virtual machine stuck on the boot logo?

Usually a missing virtual TPM or Secure Boot, a virtual CPU type without required instructions, or outdated guest drivers. Check the VM's firmware and CPU settings, update guest tools, or revert to a snapshot.

Can I change the boot logo in Windows 11?

Windows has no setting for it; the startup logo usually comes from the PC's firmware. Third-party tools can change it but risk Secure Boot conflicts and failed startups, so it is not recommended on a PC you rely on.

Can a faulty graphics card cause Windows to hang on the logo?

Yes. Test with the monitor on the motherboard's video output and the card removed. If the PC starts, check the card's seating and power cables, update its driver, or replace it.

What is a power drain and when should I do it?

Unplug the charger and hold the power button for about 30 seconds to reset the laptop's power controller. It helps when a laptop will not get past the logo or will not turn on properly after a crash or battery problem.

πŸ“š ALSO READ

More fixes for PCs that will not start:

📌 Bookmark this; force off three times, then work the ladder.

A PC stuck on the boot logo looks hopeless, but Windows has more ways back than most people know: patience for updates, unplugging the dock, recovery's own tools from Startup Repair to Uninstall Updates, Quick Machine Recovery on newer PCs, and command-line repairs for the rare cases they cannot reach. Work the ladder in order and most PCs start again with every file intact, as Ethan's did on that Wednesday morning. Then spend ten minutes on the prevention steps and a recovery drive, so the next time is even shorter.

📌 If you keep one line from this page

Stuck on the logo: wait if updating, unplug USB, force off three times, then Startup Repair, Uninstall Updates, System Restore, Safe Mode.

Maker's logo without spinning dots means firmware or hardware, not Windows.

Revision note. Written October 3, 2026. This page began in 2017 as a note about a Windows Insider build that hung during installation, and now covers every reason a Windows 11 or 10 PC gets stuck on the boot logo: which logo you are seeing, first steps, reaching recovery, Quick Machine Recovery, the repair ladder, disk and system file repairs, boot record repair for UEFI and BIOS PCs, firmware and hardware stops, prevention, resetting without losing files, virtual machines, and boot logo customization. May your next restart be a quick one.

Related