PC Stuck on Manufacturer Logo? Causes and Fixes

TL;DR: A PC stuck on the manufacturer logo usually means Windows can't finish loading past initial hardware checks, often due to a corrupted boot file, a failing drive, bad RAM, or a stuck update. Try a forced restart, boot into recovery, and check your drive health before assuming the worst. If none of that works, the hardware might be failing and it's time for a real diagnostic.

What you need

• A USB flash drive (8GB or larger) if you need to create Windows recovery media
• Access to another working computer to download recovery tools
• Your PC's power cable and, if it's a laptop, the charger plugged in
• Patience. Some of these steps take 15-20 minutes to even show progress
• Optional but helpful: knowledge of your PC's brand and model, since logo screens and boot key prompts differ by manufacturer (Dell uses F2 and F12, HP uses F10 and Esc, Lenovo uses F1 or F2, ASUS uses Del or F2)

If you don't have a spare computer or a recovery drive lying around, that's normal. Most people don't until they need one. Keep reading , there are options that don't require either.

Why this happens in the first place

When you press the power button, your PC goes through a sequence before Windows ever appears. The firmware (UEFI or older BIOS) runs a Power-On Self-Test, checks that basic hardware like RAM and storage are responding, then hands control over to a small bootloader that kicks Windows into motion. That handoff is where things most commonly break.

The manufacturer logo you see , whether it's a Dell swoosh, an HP logo, or a Lenovo splash screen , appears during or just after that firmware phase. If Windows can't load its initial boot files from your drive, or if something interrupts the process, the logo just sits there. The system isn't necessarily dead. It's stuck waiting for something that isn't coming.

The most common culprits, in rough order of how often they show up:

• Corrupted Boot Configuration Data (BCD): Windows stores boot instructions in a small data store on your drive. If a bad update, unexpected shutdown during patching, or disk error scrambles that file, Windows never gets the signal to start. This is arguably the single most common cause.
• A failing or undetected storage drive: If your SSD or hard drive is starting to fail, the firmware may detect it just long enough to show the logo, but Windows can't actually read its files off a dying drive. You'll often hear clicking from a failing HDD or notice the system takes far longer than usual to even reach the logo.
• Bad or improperly seated RAM: RAM issues can cause the system to stall mid-POST or right after. If you recently opened your machine, bumped it, or if it's been running for years, RAM seating is worth checking.
• A Windows Update that didn't finish: Windows sometimes needs to apply changes to system files on the next reboot. If power cuts out mid-update, or the update itself has a bug, the half-applied changes can leave the OS in an unbootable state. Microsoft has issued several updates over the years (notably some Windows 10 cumulative updates) that caused exactly this kind of freeze for a subset of users.
• A recently connected external device: USB drives, external hard drives, SD cards, even some docks can confuse the boot order. The firmware tries to boot from them first, finds nothing it recognizes, and stalls.
• Corrupted system files: Beyond the BCD, core Windows files like winload.exe or ntoskrnl.exe can become corrupted. These are needed to actually launch the kernel, and without them, nothing loads.

1. Rule out a simple freeze first

Before you panic, do a real forced shutdown. Hold the power button for a full 10 seconds until the machine turns off completely. Wait 30 seconds, then power back on.

This sounds too simple to matter, but a meaningful percentage of "stuck on logo" situations are exactly this: a one-time freeze caused by a minor timing glitch, a driver that took too long to initialize, or a brief storage hiccup during POST. One hard reset clears it.

While you're at it, disconnect everything that doesn't need to be plugged in. Unplug external hard drives, USB sticks, SD cards, extra monitors connected via USB-C docks, and any peripherals beyond your basic keyboard and mouse. A bootable USB left in from a previous session is a surprisingly common culprit , the system tries to boot from it, finds no valid OS, and just sits there looking confused.

If the machine boots normally after a hard reset and peripheral removal, you're done. Make a note of what was plugged in and test each device one at a time later to find the offender.

2. Let Windows attempt its own repair

If a single forced restart doesn't fix it, Windows has a built-in safety net. After two or three failed boot attempts in a row, Windows 10 and Windows 11 are supposed to automatically launch Startup Repair , a recovery environment that tries to diagnose and fix common boot problems on its own.

To trigger it intentionally, force-shutdown the machine during the boot process (while the logo is showing) two times in a row. On the third restart, you should see a message like "Preparing Automatic Repair" before landing on a blue recovery screen.

From there, go to Advanced Options > Troubleshoot > Advanced Options > Startup Repair. Windows will scan your drive, check the BCD, and attempt to patch whatever it finds broken. This works particularly well for corrupted boot configuration caused by a bad update or an interrupted shutdown. It won't fix a physically failing drive, but it's a free and often effective first attempt that requires no extra tools.

If Startup Repair runs and says it couldn't fix the problem, don't treat that as a dead end , it's actually useful information. It means the issue is likely deeper than a simple BCD corruption, and you'll want to move toward manual repair or hardware checks.

3. Boot into recovery and run manual repair commands

If automatic repair doesn't trigger or doesn't work, you can get into the Windows Recovery Environment (WinRE) manually and run repairs yourself.

To access WinRE without a recovery drive:

• Use the same "interrupt boot three times" method described above
• On some machines, you can hold Shift while clicking Restart from the Windows login screen (if you can get that far)
• Many laptops have a dedicated recovery partition you can access with a function key during boot (check your manufacturer's documentation)

Once inside WinRE, go to Troubleshoot > Advanced Options > Command Prompt. From there, run these commands in order:

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

The first two rewrite the Master Boot Record and boot sector respectively. The last two scan for Windows installations and rebuild the Boot Configuration Data from scratch. After running all four, type exit, close the prompt, and restart.

If bootrec /fixboot returns an "Access is denied" error , which happens on some UEFI systems , you'll need to run a couple of additional commands first to assign a drive letter to the EFI partition and mark it active. That's a slightly more advanced process, but documented thoroughly in Microsoft's support articles.

You can also run sfc /scannow from this command prompt to check for corrupted system files, though it requires the /offbootdir and /offwindir flags when run from WinRE rather than a live Windows session.

Computer acting up? Get a real diagnosis. Book a free diagnostic

4. Check your drive health

If repair commands don't resolve the freeze, there's a real possibility your storage drive is the problem , not your Windows installation. A corrupted OS on a healthy drive is fixable. A healthy OS on a dying drive is a ticking clock.

From the WinRE Command Prompt, run:

wmic diskdrive get status

A result of "OK" is a good sign. "Pred Fail" or "Unknown" suggests the drive is reporting problems to its own diagnostics.

For a more thorough check, you can run:

chkdsk C: /f /r

This scans for file system errors and bad sectors. On a drive with real physical problems, this will either find issues and attempt to repair them or get stuck , both of which tell you something important.

If you have access to another computer, tools like CrystalDiskInfo (free, Windows) can read a drive's S.M.A.R.T. data , a set of self-monitoring attributes the drive tracks internally. Things like "Reallocated Sector Count" climbing over time, "Pending Sector Count" above zero, or an overall health rating of "Caution" or "Bad" are signs the drive is failing and needs to be replaced, not repaired.

For NVMe SSDs, manufacturers like Samsung (Magician), Western Digital (Dashboard), and Crucial (Storage Executive) all offer free tools that show health status and can run diagnostics. If your drive is under warranty and showing bad health, that data is also useful documentation when requesting a replacement.

5. Reseat or test your RAM

If the drive checks out fine, RAM is the next hardware component worth examining. Bad RAM can cause the system to stall at almost any point during boot, including right at the logo screen.

If you're comfortable opening your machine, power it down completely, ground yourself to discharge static, and physically remove and reseat the RAM sticks. If you have two sticks, try booting with only one installed, then swap to test the other. A faulty stick will often cause the machine to fail to boot or produce beep codes, while removing it allows the system to start normally.

For a software-based test, Windows includes Windows Memory Diagnostic (search for it in the Start menu if you can boot into Windows at all, or access it from WinRE under Advanced Options). It runs a full memory test over a reboot cycle and logs results. Third-party tools like MemTest86 run from a bootable USB and are more thorough, running multiple pass algorithms that catch intermittent errors the Windows tool sometimes misses.

6. Create and use a bootable recovery drive

If none of the above resolves the issue and you have access to another computer, creating a Windows recovery USB is your most powerful option short of a full reinstall.

Download the Windows Media Creation Tool from Microsoft's website on a working computer, insert an 8GB or larger USB drive, and follow the prompts to create installation media. Once created, plug it into the affected PC, restart, and press the boot menu key for your machine's brand (F12 on most Dell machines, Esc then F9 on HP, F12 on Lenovo) to boot from USB.

From the Windows setup screen, select Repair your computer rather than Install , this gives you access to the full WinRE toolkit including Startup Repair, Command Prompt, System Restore, and if you've backed up to an image, system image recovery. If a recent System Restore point exists from before the problem started, restoring to it is often the fastest path back to a working machine.

As a last resort from the same media, you can choose to do a Reset this PC which reinstalls Windows while giving you the option to keep your personal files. It won't save installed programs, but documents, photos, and downloads stored in standard user folders are typically preserved.

7. When it's a hardware problem

If you've worked through all of the above and the machine still won't boot, the remaining possibilities are almost all hardware. A failing SSD that passes basic diagnostics but is actually degraded, a motherboard with a bad storage controller, a GPU causing display issues that look like a logo freeze, or in rarer cases, a CPU or motherboard problem.

At this point, a professional diagnostic is worth considering , not necessarily because you can't do it yourself, but because narrowing down which hardware component is failing requires either spare parts to swap in and test, or diagnostic equipment most people don't have at home. A local repair shop can usually tell you within an hour whether it's the drive, the board, or something else.

If the machine is older (5+ years for a laptop, 7+ for a desktop), the cost of diagnosis and repair may approach the cost of a replacement. That's not a reason to give up immediately, but it's worth knowing the economics before committing to repairs.

Final thoughts

A PC stuck on the manufacturer logo is alarming, but it's one of the more diagnosable problems a Windows machine can have. Work through the steps in order , forced restart, automatic repair, manual BCD rebuild, drive health check, RAM test , and you'll either fix it or at minimum understand exactly what's wrong before spending money. The majority of these freezes come down to a corrupted boot configuration or a drive in early failure, both of which are fixable with the right approach.

Computer acting up? Get a real diagnosis.

Fix My PC Store has repaired thousands of machines across West Palm Beach. Free diagnostics, honest pricing, no upsell games.

Book a free diagnostic

Frequently asked questions

Why is my PC stuck on the manufacturer logo screen?

Your PC is likely stuck because Windows can't finish loading past the initial hardware checks. The most common causes include corrupted Boot Configuration Data (BCD), a failing storage drive, bad or unseated RAM, or a Windows update that didn't finish applying correctly.

How do I fix a PC that's frozen on the manufacturer logo?

Start by holding the power button for 10 seconds to force a shutdown, disconnect all unnecessary USB devices, then restart. If that doesn't work, intentionally interrupt the boot process twice to trigger Windows Automatic Startup Repair, which can fix many common boot issues without extra tools.

How can I manually repair Windows boot files when stuck on the logo?

Boot into the Windows Recovery Environment (WinRE) by interrupting the startup process three times, then go to Troubleshoot > Advanced Options > Command Prompt. Run the commands bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, and bootrec /rebuildbcd in order to rewrite boot records and rebuild the Boot Configuration Data.

Could a failing hard drive or SSD cause the logo freeze?

Yes, a failing storage drive is one of the most common hardware causes. From the WinRE Command Prompt, you can run 'wmic diskdrive get status' for a quick check or 'chkdsk C: /f /r' for a deeper scan. Free tools like CrystalDiskInfo can also read a drive's S.M.A.R.T. data to identify signs of physical failure.

What should I do if none of the software fixes work?

If all repair attempts fail, the issue is likely hardware-related, such as a failing drive, bad RAM, or a motherboard problem. Consider visiting a local repair shop, as narrowing down which component is failing typically requires spare parts to swap in or specialized diagnostic equipment most users don't have at home.