PC Boots Straight to BIOS Instead of Windows: Boot Drive, Windows Boot Manager, and Startup Repair

A PC that powers on and enters BIOS or UEFI has already reached a different failure layer from a machine that cannot complete POST. Start by checking whether firmware detects the system SSD at all and whether the boot menu contains Windows Boot Manager or another expected operating-system entry. Do not treat those observations as interchangeable: firmware can detect an NVMe or SATA drive as storage while still lacking a usable boot entry for the Windows installation.

If the system drive is absent from firmware storage information, stay on the hardware-detection path: use the exact PC or motherboard documentation to check the drive connection, slot or port compatibility, shared-lane rules, and storage-controller configuration. Do not run Windows boot-repair commands against a drive the firmware cannot reliably detect.

When the SSD is visible in firmware, check the boot-order page for Windows Boot Manager and place the correct existing Windows boot entry first when it is available. ASUS's current support workflow for systems that enter BIOS directly likewise tells users to verify the correct OS drive or boot option after loading documented defaults.

Avoid blindly toggling CSM, Secure Boot, SATA modes, RAID settings, or UEFI/legacy compatibility options. Those settings can change which existing installation is bootable and, on some systems, which storage path is exposed. Record the original configuration first and use the exact system or motherboard documentation. Windows 11 is designed around UEFI and Secure Boot-capable firmware, so enabling legacy compatibility at random is not a universal repair.

If firmware consistently detects the system SSD but no Windows Boot Manager entry is available, the storage device and the Windows boot path are separate suspects. The EFI boot files or boot configuration can be damaged even while the Windows partition and SSD remain physically present. Conversely, an intermittently detected SSD can create similar symptoms and should not be treated as a pure bootloader problem.

Before destructive recovery, protect important data when possible. Do not initialize, format, repartition, or reinstall Windows merely because the boot entry is missing. Those actions can destroy recoverable data and are not required to establish whether the drive, firmware boot entry, or Windows boot files are the failing layer.

When the drive is detected and Windows itself will not start, use Windows Recovery Environment and try Startup Repair from Troubleshoot > Advanced options. Microsoft documents Startup Repair as the built-in recovery tool for startup failures including damaged system files and corrupted Boot Configuration Data. If the device is encrypted, have the BitLocker recovery key available before recovery work.

If Windows RE is not available from the installed system, Microsoft documents installation or recovery media as another route into recovery tools. Keep repair attempts scoped to the startup problem. Manual BCD or EFI-partition commands are advanced recovery steps and should follow Microsoft's procedure for the exact boot configuration rather than a copied command sequence that assumes drive letters or partition identities.

A drive that disappears from firmware storage information is below the Windows bootloader layer. With the PC safely powered down, use the manufacturer's service instructions to reseat a user-serviceable M.2 drive or verify SATA data and power connections where appropriate. Test another documented-compatible slot, port, cable, or drive only when the hardware supports that comparison.

Intermittent detection is especially important if the SSD contains data you need. Repeated boot attempts are not a substitute for backup. If the drive becomes readable again, prioritize preserving important data before extended testing. If a known-good compatible drive works in the same host path while the original does not, the original drive becomes more suspect; if multiple known-good drives fail in the same path, investigate the host, slot, controller, firmware, or power path.

If the system SSD is absent from firmware, troubleshoot storage detection first. If the SSD is detected and Windows Boot Manager exists, verify the documented boot order and reproduce the failure. If the SSD is detected but the Windows boot entry is missing or Windows will not start, move to Windows Recovery Environment and Startup Repair before destructive recovery. If the PC cannot complete POST at all, use a no-POST workflow instead.

The goal is to identify the first layer that fails: hardware detection, firmware boot selection, Windows boot files, or the operating system startup path. Changing several firmware settings, reinstalling drivers, repartitioning the SSD, and rebuilding boot files at once destroys that evidence and can turn a recoverable startup problem into a data-loss problem.