You finished the build, hit the power button, and instead of Windows you get a stark message: no bootable device found. It is a deflating moment, but this error almost never means a dead drive or a wasted build. It simply means the system cannot find a drive with an operating system to start from, and the causes are few and straightforward to work through.
What the error really means
The motherboard powers on, runs its self-test, and then looks for a drive containing a bootloader. When it cannot find one, it reports no bootable device. On a brand-new build this usually means the drive is not detected, the boot order is wrong, or Windows was never actually installed yet. It is a configuration issue, not a hardware death sentence, the vast majority of the time.
Causes ranked by likelihood
| Cause | How common | Fix |
|---|---|---|
| OS not installed yet | Very common | Install Windows from USB |
| Drive not seated properly | Common | Reseat M.2 or SATA drive |
| Wrong boot order in BIOS | Common | Set correct drive as first boot |
| Boot mode mismatch (UEFI/Legacy) | Occasional | Match install and BIOS mode |
| Loose SATA power/data cable | Occasional | Reseat both cables |
Work through it step by step
First, enter the BIOS and check whether the drive appears at all. If the BIOS does not see your SSD, the problem is physical: reseat the M.2 stick in its slot, or on a SATA drive, reseat both the data and power cables and confirm the power cable actually connects to the power supply. If the BIOS does see the drive but you still get the error, the issue is boot order or a missing operating system.
Install order and boot mode
On a fresh build, remember you have to install Windows yourself from a bootable USB drive; the error is expected until you do. Set the USB as the first boot device, install Windows to your SSD, then change the boot order to that SSD. Also make sure the BIOS boot mode matches how the installer was created; modern installs should use UEFI mode with the drive partitioned as GPT.
Reinstalling or repairing an existing Windows install
If you moved a drive from an old computer into a new build and now see this error, the issue is often that the old Windows installation was set up for the previous motherboard’s boot mode or is missing the right boot files for the new platform. In many cases the cleanest fix is a fresh installation, since transplanting a Windows drive between very different systems can cause driver and boot conflicts even when it does eventually start. Back up your files first, then install Windows cleanly to avoid lingering instability.
When you do want to repair rather than reinstall, a Windows installation USB includes recovery tools that can rebuild the boot configuration. Booting from the USB and using the startup repair option, or manually rebuilding the boot record from the command-line recovery environment, restores the pointer the firmware needs to find the operating system. This is the right approach when the drive and its data are fine but only the boot files are missing or misconfigured. If repair fails after a couple of attempts, a clean install is the reliable fallback.
Frequently asked questions
The BIOS does not detect my NVMe drive at all. What now?
Power down, reseat the M.2 drive firmly into its slot, and make sure the retention screw holds it flat. Check your motherboard manual, because some M.2 slots share bandwidth with SATA ports and disable them, or require a specific slot for a bootable NVMe. If it still does not appear, test the drive in another slot or update the motherboard BIOS.
It worked before and now shows this error. Did my drive die?
Not necessarily. A cable can work loose after moving the PC, or the boot order can reset after a BIOS update or CMOS clear. Reseat the drive and its cables, and re-check the boot order. Only if the drive completely disappears from every slot and cable, after those checks, should you suspect a genuine drive failure.
Bottom line: No bootable device after a build almost always means the OS is not installed yet, the drive is not seated, or the boot order is wrong. Confirm the BIOS sees the drive, install Windows from USB in UEFI mode, and set your SSD as the first boot device to get up and running.
