Stuck on the Manufacturer Logo? BIOS and Boot Order Fixes

31 Jul 2026

You switch on the computer, see the Dell, HP, Lenovo, ASUS, Acer, Microsoft, or motherboard logo—and then nothing happens.

The spinning dots may never appear. The keyboard shortcuts do not seem to work. Windows does not begin loading, and restarting simply brings you back to the same screen.

When a computer freezes at the manufacturer logo, the problem usually occurs before Windows has fully started. That makes the BIOS or UEFI firmware, connected hardware, storage drive, and boot configuration the main areas to investigate.

The fault can be as simple as a USB device confusing the boot process. It can also indicate a failing SSD, incorrect boot order, corrupted boot files, firmware problem, or hardware component that is preventing the system from completing its initial checks.

The safest approach is to troubleshoot in a controlled order and avoid changing BIOS settings at random.

What the Manufacturer Logo Actually Means

The logo appears during the earliest part of startup.

At this stage, the computer is normally:

Initialising the processor and memory
Detecting storage devices
Checking connected hardware
Loading BIOS or UEFI settings
Identifying bootable devices
Preparing to start Windows
Running a Power-On Self-Test, or POST

If the computer freezes here, Windows may not yet be involved.

That is why reinstalling Windows is not the first step.

Is It Really Frozen?

Some computers take longer than expected to move beyond the logo, especially after:

A BIOS update
Hardware changes
A failed Windows update
Storage errors
A battery fully discharging
A large number of connected USB devices
A firmware reset
Memory retraining on newer systems

Wait a few minutes once before forcing the system off.

If the computer remains on the same screen for ten minutes or more with no sign of disk activity, it is reasonable to treat it as stuck.

Do not repeatedly force it off dozens of times. Repeated interrupted starts can make storage and operating-system problems worse.

Look for On-Screen Clues

The logo screen may show useful information, including:

A spinning circle that freezes
“Preparing Automatic Repair”
“No boot device”
“PXE boot”
“Checking media”
“BIOS recovery”
A storage error
A fan warning
A battery warning
A prompt to press F1, F2, F10, F12, Delete, or Esc
A progress bar that stops

Photograph the message before restarting.

The exact wording can help distinguish between a BIOS, drive, network-boot, or Windows problem.

First: Disconnect External Devices

A faulty or bootable USB device can stop startup before Windows loads.

Shut the computer down and disconnect everything that is not essential.

Remove:

USB flash drives
External hard drives
Memory-card readers
SD cards
Docking stations
USB hubs
Printers
Scanners
Webcams
Game controllers
External optical drives
USB network adapters
Non-essential monitors
Thunderbolt devices

Leave only:

Power
Built-in display or one monitor
Keyboard
Mouse, where required

Then start the computer again.

If it boots normally, reconnect devices one at a time until the problem returns.

Why USB Devices Can Block Booting

The BIOS may try to inspect or boot from connected storage before checking the internal Windows drive.

A USB device can cause a freeze when it contains:

Corrupted partition information
A partially created boot image
A damaged file system
Faulty hardware
An incompatible controller
Old bootable installation media
A failing external disk

The computer may also be configured to give USB storage higher priority than the internal SSD.

Perform a Full Power Reset

Residual power and firmware state can occasionally leave hardware in an unresponsive condition.

For a desktop computer:

Shut it down
Disconnect the power cable
Hold the power button for around 15 seconds
Reconnect power
Start the computer

For a laptop:

Shut it down
Disconnect the charger
Remove the battery only if it is designed to be removable
Hold the power button for around 15 seconds
Reconnect the charger
Start the laptop

Do not dismantle a sealed laptop solely to disconnect the battery unless you are trained to do so.

Try to Enter BIOS or UEFI

The firmware setup screen is commonly opened by pressing a key immediately after powering on.

Common keys include:

F2
Delete
Esc
F1
F10
F12

The correct key varies by manufacturer.

Start pressing the key repeatedly as soon as the computer powers on. Do not wait for the logo to remain on screen for several seconds.

If a wireless keyboard does not respond early enough, use the built-in laptop keyboard or a basic wired USB keyboard.

What If BIOS Will Not Open?

If the computer freezes before accepting the BIOS key, possible causes include:

Hardware failing during POST
A USB device blocking initialisation
Faulty memory
Failing storage
Motherboard or firmware problems
A keyboard that is not active during startup
Fast Boot skipping some input checks
Display output appearing on another monitor

Disconnect unnecessary hardware and try again.

On a desktop with several monitors, connect only one screen directly to the main graphics output.

Check Whether the Storage Drive Is Detected

Inside BIOS or UEFI, look for pages labelled:

Storage
NVMe configuration
SATA information
System information
Boot devices
Device list

Confirm whether the internal SSD or hard drive appears.

Drive Is Detected

The problem may involve:

Boot order
Windows Boot Manager
Corrupted boot files
Wrong boot mode
Secure Boot settings
Storage-controller configuration
Operating-system corruption

Drive Is Missing

Possible causes include:

Failed SSD or hard drive
Loose data or power cable
Faulty M.2 connection
Disabled storage controller
Drive-controller failure
Motherboard fault
Damaged drive firmware

A missing drive should be investigated before changing Windows settings.

Do Not Keep Restarting a Clicking Drive

If the computer contains a mechanical hard disk that is:

Clicking
Grinding
Beeping
Scraping
Repeatedly spinning up and down

stop unnecessary attempts to boot.

A failing mechanical drive can deteriorate further each time it runs.

If the data is important and not backed up, arrange professional assessment before running repair scans.

Check the Boot Order

The boot order tells the computer which device to try first.

A typical Windows UEFI system should normally start from:

Windows Boot Manager

This entry should refer to the internal system drive.

Other possible boot entries include:

USB storage
Network or PXE
DVD drive
Another SSD
Linux boot manager
External drive
Legacy hard drive entry

If the computer is trying USB or network boot first, it may pause, fail, or display unexpected messages.

What the Correct Boot Order Usually Looks Like

For most modern Windows computers:

Windows Boot Manager
Internal SSD or approved secondary entry
USB storage, if required
Network boot, only where intentionally used

Exact options vary by computer.

On managed business devices, network boot may be deliberately enabled for deployment or recovery. Do not disable it without checking with your IT provider.

Use the One-Time Boot Menu

Many systems offer a temporary boot menu without permanently changing BIOS settings.

Common keys include:

Select Windows Boot Manager or the internal system drive.

If the computer starts correctly from the one-time menu, the permanent boot order may be wrong.

Return to BIOS and place the correct entry first.

Windows Boot Manager Is Missing

If the drive is detected but Windows Boot Manager does not appear, the boot entry or EFI system partition may be damaged.

Possible causes include:

Corrupted boot files
A failed update
Disk-cloning errors
Partition changes
BIOS reset
Drive moved from another computer
Wrong UEFI or Legacy setting
Storage-controller changes

Windows recovery media may be needed to rebuild the boot environment.

Do not create or delete partitions until important data is backed up.

UEFI vs Legacy Boot Mode

Modern Windows systems generally use UEFI.

Older systems may use Legacy BIOS or Compatibility Support Module settings.

Changing between UEFI and Legacy can prevent an existing Windows installation from starting.

Common symptoms include:

Windows Boot Manager disappears
The drive appears but is not bootable
“No boot device” appears
The system loops back to BIOS
Network boot starts unexpectedly

If the computer previously worked, restore the boot mode that was in use before the problem began.

For most Windows 11 systems, that is normally UEFI.

Do Not Change Every BIOS Setting at Once

Changing multiple settings makes it difficult to identify which one caused or solved the problem.

Before making changes:

Photograph the current settings
Note the original values
Change one option at a time
Save and test
Restore the previous value if it does not help

Avoid changing CPU voltage, memory timings, storage modes, or security features during basic boot troubleshooting.

Check Secure Boot

Secure Boot helps prevent untrusted boot software from loading.

A Secure Boot problem may occur after:

Firmware reset
Drive cloning
Operating-system repair
Dual-boot changes
Security-key changes
BIOS update
Hardware replacement

Disabling Secure Boot is sometimes suggested as a quick fix, but it can reduce protection and may affect BitLocker.

Do not disable it casually on a business device.

First confirm:

Whether Windows was installed with Secure Boot enabled
Whether BitLocker recovery information is available
Whether the computer is managed
Whether the boot files are genuinely incompatible

A correct Windows 11 installation should normally work with Secure Boot enabled.

BitLocker Warning

BIOS changes can trigger BitLocker recovery.

Changes involving:

Secure Boot
TPM
Boot order
Firmware
Storage controller
Motherboard settings

may cause Windows to request the BitLocker recovery key.

Before changing firmware settings, make sure the recovery key is available.

For business systems, the key may be stored in Microsoft Entra ID, Active Directory, or the organisation’s device-management platform.

Do not clear the TPM as a routine boot fix.

Check the Storage Controller Mode

BIOS may offer storage modes such as:

AHCI
RAID
Intel RST
VMD
IDE on older systems

Windows is installed with drivers for a particular configuration.

Changing the storage mode can cause:

Inaccessible boot device errors
Failure to detect the operating system
Startup loops
Windows recovery screens

If the setting changed after a BIOS reset or update, restore the previous mode.

Do not switch between AHCI and RAID randomly.

BIOS Defaults Can Help—but Use Them Carefully

Loading BIOS defaults can correct an accidental configuration change.

Look for options such as:

Load Setup Defaults
Optimised Defaults
Restore Defaults
Factory Defaults

Before using them, record the current settings.

Defaults may change:

Boot order
Secure Boot
Storage mode
Virtualisation
Fan profiles
Thunderbolt security
Network boot
Date and time
TPM behaviour

On business devices, those changes can affect encryption, deployment, and management.

Check the System Date and Time

A completely incorrect date or time does not usually cause a permanent logo freeze by itself, but it may indicate that BIOS settings were lost.

Possible causes include:

CMOS battery failure
Firmware reset
Motherboard power loss
BIOS corruption

Repeatedly losing the time can be a warning that the CMOS battery or motherboard settings are not being retained.

Run Built-In Hardware Diagnostics

Many manufacturers include pre-boot diagnostics.

They may test:

SSD or hard drive
Memory
Processor
Battery
Fan
Motherboard
Display
Network adapter

Common access methods use keys such as F2, F10, F12, Esc, or a dedicated diagnostic button.

Run the short tests first.

If the drive test reports:

SMART failure
Short test failure
Read error
NVMe error
Drive not detected

protect the data and replace the failing storage device.

Memory Problems Can Freeze the Logo Screen

Faulty or unstable RAM can prevent POST from completing.

Symptoms may include:

Freeze at manufacturer logo
Blank screen
Restart loop
Beep codes
Flashing diagnostic lights
Random progress through startup
BIOS opening only occasionally

On desktops with accessible memory, a technician may reseat modules or test them individually.

Do not dismantle a device under warranty without checking the service terms.

Pay Attention to Beep Codes and Lights

Computers often signal hardware faults using:

Beeps
Power-button flashes
Keyboard light patterns
Coloured diagnostic LEDs
Motherboard code displays

The pattern can identify problems involving:

RAM
CPU
Graphics
Storage
Power
Motherboard

Record the exact pattern and consult the manufacturer’s support information for that model.

A generic interpretation from another brand may be wrong.

Check Whether the Keyboard Responds

Try pressing Caps Lock or Num Lock while the logo is frozen.

If the indicator light changes, the system may still be partly responsive.

If it does not, the firmware may be completely stalled.

This is not a definitive test, but it can help distinguish a frozen display from a system that is still processing something slowly.

Check the Display Connection

Sometimes the computer continues booting but sends the picture to the wrong display.

This can happen after:

BIOS reset
Graphics-card change
Docking-station issue
Multiple-monitor configuration
Switching between integrated and dedicated graphics

Test:

One monitor only
Another cable
Another display port
Direct connection without a dock
The motherboard output, where appropriate
The graphics-card output, where appropriate

Do not assume the system has frozen solely because one screen remains on the logo.

Remove Newly Installed Hardware

If the problem began after adding hardware, remove or reverse the change.

Potential causes include:

New RAM
Additional SSD
Graphics card
USB expansion card
Wi-Fi card
Docking station
External storage
PCIe accessory
Recently replaced battery

Confirm that the hardware is compatible and correctly fitted.

A new drive can also change boot order automatically.

A Second Drive Can Steal Boot Priority

Installing another SSD or connecting an old system disk can create several bootable entries.

The BIOS may attempt to start from the wrong one.

Symptoms include:

Old Windows installation loading
Logo freeze
Recovery screen
Boot manager menu
“No operating system”
Looping back to BIOS

Disconnect the secondary drive temporarily and test.

Then set Windows Boot Manager on the correct system drive as the first boot option.

Network Boot and PXE Messages

Messages such as:

Start PXE over IPv4
Start PXE over IPv6
Checking media presence
Network boot

usually mean the computer did not find a bootable local device and moved to the next option.

This can happen because:

Internal drive failed
Windows Boot Manager is missing
Boot order changed
Network boot is first
Storage controller mode changed
Drive is disabled

Do not focus only on disabling PXE. Find out why the internal boot option was skipped.

“No Boot Device Found”

This message commonly indicates:

Storage drive not detected
No valid operating-system boot entry
Wrong boot mode
Corrupted EFI partition
Failed SSD or hard drive
Loose cable
Incorrect storage-controller setting

Check drive detection and Windows Boot Manager before attempting a Windows reinstall.

If the Logo Appears With Spinning Dots

When the manufacturer logo remains visible but Windows spinning dots appear, the system has likely progressed beyond BIOS and begun loading Windows.

The problem may then involve:

Windows update
Storage corruption
Driver failure
Startup service
BitLocker
Automatic repair
Damaged system files

At that stage, Windows Recovery Environment becomes more relevant than BIOS settings alone.

Enter Windows Recovery Environment

After several failed starts, Windows may enter recovery automatically.

You may also boot from approved Windows installation or recovery media.

Recovery options can include:

Startup Repair
Uninstall Updates
System Restore
Safe Mode
Command Prompt
UEFI Firmware Settings
System Image Recovery

Start with the least destructive options.

Do not select Reset this PC or reinstall Windows before confirming that important data is backed up.

Try Startup Repair

Startup Repair attempts to correct common boot problems.

It may help with:

Damaged boot configuration
Missing startup files
Failed updates
Certain registry problems

It will not repair a physically failing storage drive.

If the drive is producing errors or unusual noises, assess its health before running repeated repair operations.

Uninstall a Recent Update

If the computer became stuck immediately after an update, Windows Recovery may allow you to remove:

Latest quality update
Latest feature update

This can restore startup when a particular update or driver caused the problem.

Do not permanently avoid security updates. Once the system works, identify the incompatible driver or software and install a corrected version.

Use Safe Mode

Safe Mode loads a reduced set of drivers and services.

If Windows starts in Safe Mode, the problem may involve:

Graphics driver
Security software
Recent application
Startup service
Device driver
Update

Safe Mode is less useful if the computer never passes the firmware logo or cannot reach Windows Recovery.

Boot Configuration Repair

Advanced recovery may involve tools such as:

bcdboot
bootrec
DiskPart
EFI partition repair

These commands can alter the boot configuration and partitions.

Incorrect use can make recovery more difficult.

Back up data first and use professional assistance when the partition structure or encryption status is unclear.

Do Not Rebuild the Boot Files Blindly

Before repairing boot records, confirm:

The correct Windows partition
The EFI system partition
Whether the drive uses GPT or MBR
Whether BitLocker is enabled
Whether multiple operating systems exist
Whether the drive is healthy

Running old Legacy BIOS repair commands on a modern UEFI system may not solve the problem and can create confusion.

Check the SSD or Hard Drive Health

A drive can be detected in BIOS yet fail under load.

Warning signs include:

Slow BIOS detection
Logo screen taking longer over time
Intermittent booting
Automatic repair loops
File corruption
SMART warnings
Read errors
Drive disappearing after restart

Manufacturer diagnostics or professional tools can assess the drive.

For important data, clone or recover the drive before running intensive repairs.

BIOS Update: Useful but Not the First Fix

A BIOS update can resolve:

Hardware compatibility
Boot bugs
Storage detection
Security vulnerabilities
Firmware instability
Docking or USB issues

However, updating BIOS while the system is unstable carries risk.

Do not update firmware merely because the computer is stuck at the logo.

First:

Remove external devices
Check boot order
Confirm drive health
Restore known-good settings
Review the manufacturer’s update notes
Ensure stable power

Use only firmware intended for the exact model.

Never Interrupt a BIOS Update

Power loss during firmware installation can leave the computer unable to start.

For a laptop:

Connect the correct charger
Confirm the battery has sufficient charge
Do not disconnect power
Do not close the lid
Do not force shutdown

Some manufacturers provide BIOS recovery procedures, but recovery is not guaranteed.

BIOS Recovery

A failed or corrupted BIOS may produce:

Blank screen
Logo freeze
Repeated restarts
Fan running at high speed
Recovery message
Beep or light codes

Some systems include:

Automatic BIOS recovery
Recovery key combination
USB firmware recovery
Dual BIOS
Dedicated recovery button

Use only the manufacturer’s procedure for the exact model.

CMOS Reset

Resetting CMOS clears stored firmware settings.

It may help when BIOS settings are corrupted or the system cannot complete POST after a configuration change.

However, it can also reset:

Boot order
Storage mode
Secure Boot
TPM settings
Date and time
Fan controls
Memory profiles

On business devices, a CMOS reset may trigger BitLocker recovery and alter managed settings.

This is normally a technician-level step, particularly on laptops.

Overclocking and Memory Profiles

Unstable overclocking can cause startup freezes.

This includes:

CPU overclock
GPU settings
XMP or EXPO memory profiles
Manual memory timings
Undervolting
Custom power limits

Return the system to standard settings.

A computer that works only after several restarts may have marginal memory or power stability.

Business computers should prioritise reliability over performance tuning.

Fast Boot Can Hide Problems

BIOS Fast Boot reduces startup checks.

It can also make it harder to:

Enter BIOS
Detect USB keyboards
Initialise some devices
Recognise hardware changes
Use external boot media

Temporarily disabling Fast Boot can assist troubleshooting.

Do not confuse BIOS Fast Boot with Windows Fast Startup. They are separate features.

Windows Fast Startup

Windows Fast Startup saves part of the operating-system state during shutdown.

This can occasionally preserve driver or hardware problems.

A full Restart performs a more complete startup than a normal shutdown with Fast Startup enabled.

If the problem is intermittent, try Restart rather than repeatedly shutting down and powering on.

Laptop Battery and Power Problems

A failing battery or charger can interfere with startup.

Check for:

Battery warning
Incorrect charger message
Charger not recognised
Swollen battery
Intermittent power
Device shutting off during POST
BIOS reporting insufficient adapter wattage

Stop using a swollen battery and arrange replacement.

Do not continue BIOS updates or storage repairs on unstable power.

Desktop Power-Supply Problems

A weak or failing power supply may allow the logo to appear but fail as more components initialise.

Symptoms can include:

Freeze during POST
Restart loop
Drives disappearing
Fans changing speed
Graphics not initialising
USB devices cutting out
Random shutdowns

Power-supply testing and replacement should be handled by someone competent with desktop hardware.

Protect the Data Before Major Repairs

Before reinstalling Windows, resetting partitions, or replacing the drive, consider whether the data is backed up.

Possible recovery methods include:

Removing the drive and connecting it to another computer
Booting approved recovery media
Using professional data-recovery tools
Restoring from cloud or local backup
Cloning a failing drive

Encryption can complicate access.

Make sure the BitLocker recovery key is available before removing or repairing an encrypted drive.

What Not to Do

Avoid:

Changing every BIOS setting
Clearing the TPM without understanding BitLocker
Forcing repeated restarts on a failing drive
Installing unofficial BIOS files
Downgrading firmware randomly
Reinstalling Windows before checking drive detection
Deleting partitions without a backup
Forcing hardware into slots
Opening a sealed laptop under warranty unnecessarily
Ignoring clicking or grinding storage noises

A cautious diagnosis usually preserves more recovery options.

A Practical Troubleshooting Order

Use this sequence:

Wait once to confirm the computer is genuinely stuck
Photograph any message or error
Disconnect all non-essential USB and external devices
Perform a full power reset
Try entering BIOS or the one-time boot menu
Confirm whether the internal drive is detected
Check that Windows Boot Manager is first
Restore the correct UEFI and storage-controller settings
Run built-in drive and memory diagnostics
Remove recently added hardware
Test one monitor and a basic wired keyboard
Enter Windows Recovery if spinning dots appear
Try Startup Repair or uninstall a recent update
Assess drive health before intensive repair
Back up important data
Consider BIOS recovery or update only when justified
Arrange professional diagnosis if the system still cannot pass POST

This order starts with low-risk checks and gradually moves toward more advanced repairs.

When to Contact an IT Professional

Professional help is recommended when:

The internal drive is not detected
The drive clicks, grinds, or repeatedly disappears
BIOS cannot be opened
The computer reports memory or motherboard errors
BitLocker recovery is triggered
Storage-controller settings are unclear
Windows Boot Manager is missing
The system is business-critical
BIOS recovery may be required
Important files are not backed up
The problem began after hardware replacement
The computer freezes before completing POST
Several devices show the same issue after an update

A technician can test the storage, memory, power supply, motherboard, boot partitions, firmware, and Windows installation without making unnecessary destructive changes.

Get Past the Logo and Back Into Windows

A computer stuck on the manufacturer logo has usually failed before Windows starts normally.

The cause may be a boot-order change, connected USB device, missing Windows Boot Manager entry, incorrect BIOS setting, failing drive, unstable memory, or firmware fault.

Begin by disconnecting external devices and checking whether the internal drive appears in BIOS. Then confirm the correct boot order and run the manufacturer’s built-in diagnostics.

Avoid reinstalling Windows until the storage device and important data have been assessed.

Hamilton Group can diagnose computers stuck during startup, repair BIOS and boot-order problems, recover damaged Windows boot files, replace failing drives, and protect important business data.

Call 0330 043 0069 or visit hgmssp.com to book a meeting with one of our IT experts.

Previous Next