Stuck on the Manufacturer Logo? BIOS and Boot Order Fixes
You press the power button.
The Dell, HP, Lenovo, ASUS or other manufacturer logo appears.
Then nothing happens.
No Windows login screen.
No spinning desktop.
Sometimes the logo simply stays there indefinitely. Other times the machine restarts, freezes or drops into firmware setup.
The first thing to establish is:
Is the computer stuck before Windows starts, or is Windows starting and then failing?
That distinction changes the entire troubleshooting path.
What the Manufacturer Logo Actually Means
On a modern Windows 11 PC, the manufacturer logo is normally displayed during the UEFI/firmware stage.
Microsoft describes the first startup phase as PreBoot, where UEFI firmware performs initialisation and POST, loads its settings and looks for a valid boot device. Only after that does Windows Boot Manager take over.
So if the PC freezes before it ever reaches Windows Boot Manager, the problem may involve:
hardware detection
USB devices
storage
UEFI firmware
boot order
failed POST
rather than Windows itself.
First: Remove External Devices
Start with the simplest test.
Shut the PC down.
Disconnect non-essential devices such as:
USB drives
external hard disks
docks
printers
card readers
USB hubs
unusual peripherals
Leave only what is genuinely required:
power
display
keyboard/mouse where necessary
Then boot again.
A system can appear stuck at the manufacturer logo while firmware is waiting on or struggling with an external device during POST.
If the PC starts normally after removing everything, reconnect devices one at a time until the problem returns.
Can You Enter BIOS/UEFI?
Restart and use the manufacturer’s firmware key.
Common examples include:
F2
Delete
Esc
F10
F12
The exact key depends on the manufacturer.
If you can enter UEFI setup, that tells you something useful:
the machine is at least completing enough firmware initialisation to enter configuration.
Now check the storage device and boot configuration.
Is the Windows Drive Detected?
Inside BIOS/UEFI, look for:
Storage
NVMe
SATA
Boot
System Information
Confirm whether the system drive appears.
For example, you might see:
Samsung NVMe SSD
or:
WD SNxxxx
Drive appears
Good.
The firmware can see the storage hardware.
Move on to boot order.
Drive does not appear
Stop changing Windows boot settings.
If the firmware cannot detect the drive, Windows Boot Manager cannot load from it.
Possible causes include:
failed SSD
loose storage device
controller problem
BIOS configuration
motherboard fault
A missing drive in firmware is primarily a hardware/storage problem.
Check the Boot Order
On a normal modern Windows 11 UEFI installation, you would typically expect:
Windows Boot Manager
to appear as the primary boot entry.
Microsoft’s UEFI boot documentation recommends Windows Boot Manager as the primary firmware boot item for a standard Windows installation.
If the system is instead trying to boot first from:
USB
network/PXE
another disk
old boot entry
move Windows Boot Manager back to the correct position.
Do not randomly disable every other boot option.
Just restore a sensible order.
Boot Order Only Matters if the Firmware Can See the Drive
This distinction is important.
If BIOS/UEFI reports:
No NVMe drive
then moving Windows Boot Manager higher in the boot list is not the fix.
Likewise, if the drive is detected but no Windows Boot Manager entry exists, the issue may be:
damaged EFI boot files
corrupted BCD
changed firmware mode
damaged system partition
Now Windows recovery tools become more relevant.
Do Not Randomly Switch UEFI to Legacy/CSM
Modern Windows 11 systems are designed around UEFI.
Microsoft’s current Secure Boot guidance recommends UEFI rather than Legacy/CSM and notes that firmware settings determine whether Secure Boot is available.
If a machine was installed in UEFI mode and you suddenly change it to:
Legacy
Windows may stop booting even though nothing was wrong with the installation.
Unless you have a specific reason:
do not change UEFI/Legacy mode as a generic fix.
Be Careful With Secure Boot
Do not disable Secure Boot simply because the machine is stuck.
Secure Boot is a Windows security feature that allows only trusted, signed boot components to load. Microsoft recommends re-enabling it if it must ever be temporarily disabled for troubleshooting.
Also note that Microsoft is actively servicing the Secure Boot certificate transition during 2026 because older certificates begin expiring from June 2026. On supported Windows devices, Microsoft intends that certificate updates happen automatically.
So:
manufacturer logo problem ≠ disable Secure Boot.
Only change it when there is evidence it is involved.
If the Manufacturer Logo Appears With Spinning Dots
This usually suggests Windows has progressed further than pure firmware/POST.
At that point, Windows Boot Manager or the operating system may be involved.
Microsoft’s startup troubleshooting separates this from the earlier PreBoot phase.
Now Windows Recovery Environment becomes useful.
Enter Windows Recovery Environment
Windows 11 can automatically enter Windows RE after repeated failed startup attempts.
Microsoft currently documents this method:
1. Start the computer.
2. When the Windows/manufacturer logo appears, hold the power button until it shuts off.
3. Repeat this twice.
4. Start it a third time.
5. Windows should enter Automatic Repair.
6. Choose Advanced options.
Do this only when the machine is clearly progressing into Windows startup.
If the firmware itself is completely frozen before Windows begins, forced Windows recovery may never appear.
Try Startup Repair
In Windows RE choose:
Troubleshoot > Advanced options > Startup Repair
Microsoft says Startup Repair can diagnose and repair problems involving:
damaged system files
corrupt Boot Configuration Data
boot records
incompatible drivers
Registry problems.
It is the right first recovery tool when Windows is failing to start.
It is not the first tool for a drive missing from BIOS.
If Startup Repair Fails
You still have several recovery options.
Microsoft’s current recovery guidance recommends different tools depending on the scenario. For startup failures, the normal escalation is:
Startup Repair
then, where appropriate:
System Restore
or other recovery options.
Windows RE also provides:
Uninstall Updates
Startup Settings
Command Prompt
System Restore
UEFI Firmware Settings.
Did the Problem Start After a Windows Update?
Use:
Troubleshoot > Advanced options > Uninstall Updates
You may be able to remove the latest:
quality update
feature update
This is particularly useful when the system reached Windows normally before an update and stopped booting immediately afterwards.
Do not assume every logo freeze is caused by the newest cumulative update.
First identify whether the failure occurs before or after Windows begins loading.
Try Safe Mode
From Windows RE:
Troubleshoot > Advanced options > Startup Settings > Restart
Then choose:
Safe Mode
Microsoft explains that Safe Mode starts Windows with only essential services and drivers, making it useful for identifying driver or software problems.
If Safe Mode works but normal Windows does not, investigate:
recent driver
startup software
security software
recent application
graphics driver
The storage and basic boot path are clearly working.
BitLocker May Ask for the Recovery Key
This is normal when using some recovery operations.
Microsoft warns that encrypted devices may require the BitLocker recovery key when accessing WinRE tools such as Startup Repair or Startup Settings.
Have the recovery key available before making firmware or boot changes on an important business device.
Do not begin randomly resetting TPM or clearing Secure Boot keys because BitLocker asks for recovery.
What If the PC Freezes Even Inside BIOS?
That is a very different problem.
If the computer:
freezes in UEFI setup
reboots while inside firmware
cannot consistently detect RAM/storage
hangs during hardware detection
Windows is unlikely to be the cause.
Investigate:
RAM
SSD
motherboard
CPU
power
firmware
For desktops, reseating hardware may be appropriate for a competent technician.
For laptops and business devices, manufacturer diagnostics or hardware service may be safer.
Run Manufacturer Diagnostics
Most business PCs include built-in preboot diagnostics.
Examples commonly test:
memory
storage
processor
motherboard
If the machine stops at the manufacturer logo and the firmware diagnostic reports:
SSD failure
you have far stronger evidence than repeated attempts at Windows Startup Repair.
Use the manufacturer’s diagnostic environment before assuming Windows needs reinstalling.
A Failing SSD Can Cause Long Logo Delays
A storage device does not always fail cleanly.
An SSD or HDD can become slow or unreliable enough that firmware spends an unusually long time trying to identify it.
Possible symptoms include:
manufacturer logo displayed for several minutes
storage sometimes detected, sometimes missing
eventual “No bootable device”
intermittent startup
If important data is on the drive and hardware failure is suspected, prioritise data protection before running aggressive repair tools.
“No Bootable Device” Is Different
If the PC progresses beyond POST and reports:
No bootable device
that usually means firmware completed hardware initialisation but could not find a valid boot target.
Now check:
1. Is the SSD detected?
2. Does Windows Boot Manager exist?
3. Is UEFI mode correct?
4. Is boot order correct?
If all of those look right, the EFI/Windows boot files may need repair.
Advanced: Boot Files and BCD
Microsoft documents manual Boot Configuration Data repair methods, but these should be treated as advanced recovery steps rather than the opening move.
For most users:
Startup Repair first.
If that fails and the drive is healthy, an IT professional can investigate:
EFI System Partition
BCD
Windows Boot Manager
boot files
Avoid blindly copying bootrec commands from an old Windows 7 article.
Modern Windows 11 typically boots through UEFI and its EFI System Partition.
Don't Reset BIOS to Defaults Without Thinking
Loading firmware defaults can be useful when a bad UEFI configuration is suspected.
But it can also change:
storage mode
Secure Boot
virtualisation
boot order
TPM-related settings
On managed business PCs, record existing settings first.
A BIOS reset can turn one boot problem into several configuration problems if important settings are lost.
What If This Started After a BIOS Update?
Firmware updates can occasionally introduce:
boot-order reset
storage setting changes
firmware regression
If the problem began immediately after a BIOS update:
1. Check whether the SSD is still detected.
2. Check Windows Boot Manager.
3. Check UEFI/Secure Boot/storage mode.
4. Review manufacturer support information for that exact BIOS release.
Do not install firmware from unofficial websites.
The Fastest Troubleshooting Order
If the PC is stuck on the manufacturer logo:
1. Disconnect non-essential USB devices.
2. Restart and try entering BIOS/UEFI.
3. Check whether the Windows drive is detected.
4. Check whether Windows Boot Manager exists.
5. Check boot order.
6. Leave UEFI/Legacy and Secure Boot alone unless evidence points there.
7. Run manufacturer hardware diagnostics.
8. If Windows starts loading, enter WinRE.
9. Run Startup Repair.
10. If necessary, try Uninstall Updates, System Restore or Safe Mode.
11. Investigate BCD/EFI repair only after the hardware and basic recovery checks.
12. Reinstall Windows only when safer repair routes have failed and your data is protected.
The key principle is:
If the machine is stuck before Windows Boot Manager, troubleshoot firmware and hardware first. If Windows has started loading, move into Windows recovery.
A Useful Example
Suppose a Lenovo laptop stops indefinitely at the Lenovo logo.
You enter UEFI.
The NVMe drive is not listed.
Restarting five times changes nothing.
That is not where I would run:
Startup Repair
or:
Safe Mode.
The firmware cannot even see the system drive.
Investigate the SSD or hardware path.
Another laptop shows:
manufacturer logo + spinning dots
then repeatedly restarts.
The SSD is detected and Windows Boot Manager is first in the boot order.
Now:
WinRE > Startup Repair
is a sensible next step.
Those are different faults even though both initially look like:
“stuck at the logo.”
How Hamilton Group Can Help
Boot failures can involve anything from a USB device confusing firmware to a failed SSD, corrupt boot configuration or Windows update.
Hamilton Group can help with:
Windows 11 boot problems
BIOS/UEFI
boot order
Windows Boot Manager
Startup Repair
WinRE
BitLocker recovery
SSD diagnostics
Safe Mode
Windows recovery
data protection
For business devices, we can establish whether the fault is hardware, firmware or Windows before reinstalling machines unnecessarily.
Visit hgmssp.com or call 0330 043 0069.