A missing SSD usually comes down to a poor connection, the wrong M.2 interface, a disabled controller, or failed hardware. Work through these checks without formatting the drive.
Shut the PC down fully, reseat the SSD, then check it in the BIOS storage menu rather than only the boot list. If it stays missing, verify M.2 compatibility plus shared-port limits before resetting firmware settings. Test the drive in another computer last.
Do not initialize, format, secure-erase, or reinstall Windows on the SSD if it contains needed files. Those actions will not make a drive appear in BIOS. They may make later recovery harder once the hardware becomes visible.
BIOS detection happens before Windows, macOS, or recovery software loads. Disk-management tools, driver reinstallations, partition commands, plus file-recovery scans cannot communicate with a drive that the firmware never presents to the operating system.
Software becomes useful once the SSD appears as a physical disk, even if its partition is damaged or has no drive letter. Until then, focus on power, cables, slots, compatibility, firmware, plus testing in another machine.
If the SSD appears under NVMe or storage information but not in the boot menu, it may simply lack a bootable operating system. If it appears in another PC only, suspect the original slot, cable, controller setting, or motherboard. If no known-good system can detect it, the SSD itself becomes the main suspect.
Begin with the connection checks, then move toward firmware or hardware testing.
| Method | Best for | Time | Success rate |
|---|---|---|---|
| 1. Power-Cycle the PC, Then Reseat the SSD TRY FIRST | Loose SSDs or cables | ~10 min | ● 78% |
| 2. Check the SSD Port, Slot, Plus Motherboard Limits | New M.2 installations | ~15 min | ● 72% |
| 3. Restore Safe BIOS Storage Settings | Changed or unstable BIOS settings | ~10 min | ● 58% |
| 4. Update the BIOS, Then Clear CMOS if Needed | Older boards with newer SSDs | ~30 min | ● 46% |
| 5. Test the SSD Elsewhere, Then Recover Its Files | Suspected board or SSD failure | ~30–90 min | ● 64% |
A loose M.2 connection, weak SATA plug, or incomplete power cycle can keep an SSD out of BIOS. Reseating the drive is the quickest useful test, especially if the problem began after work inside the PC.
M.2 describes the drive's shape, not its electrical interface. Some sockets accept PCIe NVMe only, while others accept M.2 SATA. A populated M.2 slot may also disable one or two regular SATA ports.
A disabled storage controller or unstable firmware setting can hide a working SSD. Loading defaults gives you a clean baseline, though existing RAID or Intel RST setups need extra care.
A motherboard firmware update may improve storage compatibility or correct detection bugs. If settings remain stuck afterward, a CMOS reset can rebuild the hardware configuration from scratch.
Testing the SSD through another compatible connection separates a drive failure from a motherboard problem. If the second computer detects it, copy critical files first or scan it with Disk Drill before attempting initialization, formatting, or repairs.
Begin with a full power cycle plus a careful SSD reseat. That is the right first move after installing hardware, moving the PC, or opening its case. For a new M.2 drive, compatibility plus lane sharing deserve the next look.
If another computer detects the SSD, protect the files before making repairs. Use Disk Drill only after the operating system can see the physical device. A drive missing from every compatible system likely has a hardware fault.
Change one thing at a time, then check the BIOS storage page after each restart so you know which step solved the problem.