SSD not detected in BIOS — what to do safely

Why an SSD may not be detected in BIOS/UEFI

No SSD detection in BIOS/UEFI does not always mean a "damaged drive". Sometimes the cause is the M.2/SATA slot, power delivery, controller mode settings, or unstable firmware. If the SSD contains important data, the key point is to avoid further writes and not worsen the condition of the device. If the issue concerns SSD/NVMe, see how SSD and NVMe data recovery looks in the lab.

Safe steps you can take immediately

• Turn off the computer and do not keep trying to boot it repeatedly "until it finally works".
• If this is a SATA drive: swap the SATA cable and the power lead, and use another port on the motherboard.
• If this is an M.2 NVMe/SATA drive: check that it is seated correctly (gently press it down and tighten the screw), then test the second M.2 slot if one is available.
• In BIOS/UEFI, check whether the device appears in the Storage/NVMe section and whether a device "hiding" mode is enabled (rare, but it happens on some motherboards).
• If the drive appears only sometimes, stop testing — this is a typical sign of instability (controller / firmware), and it is better to move to safe imaging.

What not to do if the data matters

• Do not initialise, format or "repair" the partition.
• Do not run CHKDSK or automatic system repair tools on this device.
• Do not update SSD firmware "just to try". An update can change the FTL state and make recovery harder.
• Do not perform long stress tests — with firmware problems they can push the device into safe mode or make it disappear entirely.

When it is already a job for the lab

If the SSD disappears, shows 0 GB, switches to read-only mode, or the computer freezes during reading, the best decision is to stop testing and hand the device over for SSD/NVMe data recovery. In the laboratory we perform safe imaging first and only then analyse the file system on the copy.

If the problem concerns a spinning drive, the mechanics and symptoms are different — see also HDD data recovery.

Need help? Submit the device through the form — we will prepare a safe course of action without risky "home testing". Go to the submission form. If you want to understand what affects pricing, see the guide: how much data recovery costs.

How to prepare the case before a safe diagnosis

If the SSD is still visible from time to time, do not keep reconnecting it just to "see whether it comes back". Write down the exact symptoms instead: whether the device disappears after warming up, whether the capacity changes, whether the system freezes, and whether the issue started after an update, power cut, or physical shock. This kind of short timeline often helps separate a controller problem from a configuration issue.

If you already tried different slots or another computer, stop there and preserve the current state. On SSD/NVMe media, repeated power cycles and extra write activity may work against you because TRIM and garbage collection keep changing the internal state of the drive even when the device looks only "temporarily missing".

When recovery chances drop the fastest on SSD and NVMe

The most dangerous moment is when the drive is unstable but still sometimes responds. That is when users are tempted to clone it in the operating system, install tools, or run long scans. If the symptoms include overheating, sudden 0 GB capacity, read-only mode, or disappearing during reads, it is safer to stop and compare the case with guides about SSD/NVMe bricking and deleted files on SSD with TRIM. If the device contains unique data, the safest next step is a controlled laboratory workflow described in why SSD/NVMe recovery is not the same as HDD recovery.

What the BIOS behaviour can tell you before you do anything else

If the SSD is never visible, not even for a second, the problem is usually deeper than a simple Windows issue. A controller failure, damaged firmware area, power rail instability or a board-level problem may prevent the device from identifying itself correctly. If the SSD appears briefly with the right model name and then disappears, that often points to an unstable state rather than a healthy drive with a bad operating system.

Write down exactly what the machine shows: correct model and size, wrong capacity such as 0 GB, a generic name, or a total lack of detection. These details help separate a recovery case from a configuration issue and make it easier to choose the safest next step without repeating power cycles.

When the problem may be outside the SSD itself

Sometimes the symptom is not caused by the data medium alone. A damaged M.2 slot, weak power delivery after liquid damage, a failing USB bridge in an external enclosure or a firmware issue on the motherboard can all make an SSD look "dead" in BIOS/UEFI. That is why it is worth stopping after one careful cross-check instead of moving the drive through many adapters and computers.

If the SSD contains unique data, the goal is not to prove every possible cause at home. The goal is to preserve the current state long enough for safe diagnosis. In practice that means documenting what was tested once, then deciding whether the case looks more like SSD/NVMe bricking, a TRIM-sensitive scenario, or a hardware problem that should go straight to SSD/NVMe data recovery.