Skip to content
Essential Data Recovery

SSD disappeared from BIOS

A drive absent from the BIOS is invisible to every recovery tool, so the documented checks come first: ports, seating, cables, M.2 sharing and controller modes, before the endpoint the makers themselves name.

Written by Essential Data RecoveryPublished 2026-09-12Safety-critical: owner-reviewedRevision 1
A bare M.2 solid state drive resting on cream paper over pale oak wood, with a soft plant shadow

If the data on this SSD matters and is not backed up, slow down before you start fixing. On a BitLocker-encrypted machine, several of the steps on this page, firmware upgrades, hardware moves, BIOS setting changes, will demand a 48-digit recovery key at the next boot. Locate that key from another device first, and keep the number of experiments low.[1]

An SSD that has vanished from the BIOS or UEFI storage list is invisible to the operating system, to recovery software and to firmware updaters; nothing software-based applies until the machine can see the drive again. The documented causes are rarely fatal: a port disabled or turned off in setup, an M.2 slot sharing lanes with a SATA port, a data cable that broke invisibly inside its insulation, or a RAID or VMD controller mode hiding a healthy drive. Work through them in order, and know the endpoint the drive makers themselves describe: if no system detects the drive, a single power cycle is the last DIY step before replacement or professional recovery.[2][3]

This guide covers internal 2.5 inch SATA and M.2 drives absent from the BIOS or UEFI on Windows desktops and laptops. It does not cover a drive the BIOS can see but Windows cannot, external USB drives, Macs, or RAID arrays; those are different situations.

Not sure which situation you are in? Guided help walks you through it.

The safe checks, in a documented order

Power off, then work down the list

  1. Reseat both connections. For a 2.5 inch SATA drive that is the narrow data cable and the wider power lead; Crucial's guidance is to remove, reseat and double-check both.
  2. Try a different SATA port, and check that the ports are enabled in the BIOS: Seagate notes some motherboard makers disable unused ports by default, and adding a drive can mean enabling one.
  3. Replace the SATA data cable. Cables can break inside their insulation and look fine outside, and Seagate calls replacement the easiest test.
  4. For M.2 drives, confirm the screw is seated and try the other M.2 slot if the board has one; slots differ, as below.
  5. Test the drive in another computer if possible: a drive that appears elsewhere points at the first system, not the drive.
[4][2][3]

The M.2 specifics that catch people out

M.2 slots are not interchangeable, and the failures are mundane. On some boards an M.2 port shares lanes with a specific SATA port, so fitting an M.2 drive silently switches that SATA port off; ASUS documents the pairing and its workaround of moving the SATA cable to another port. Slots also differ in what they speak: ASUS documents slots that support both SATA and PCIe modes and others that support PCIe only, which is why a SATA-mode M.2 drive may never appear in a PCIe-only slot. The physical notch rarely is the problem on modern drives; the slot's protocol is. One reassuring note from ASUS: on some older boards a PCIe-mode M.2 drive showing no details in certain BIOS storage screens is normal, and a BIOS update is the vendor's own recommendation when a drive cannot be found.[5]

Controller modes that hide healthy drives

A drive can be perfect and still invisible because of the mode the controller is in. Crucial notes RAID modes preventing detection of single drives, including PCIe drives hidden by a SATA RAID mode with no SATA drives installed. Intel's VMD does the same in its own way: Lenovo documents that with VMD enabled, everything behind the VMD controller, including the NVMe controllers inside the SSDs, becomes invisible, and names disabling VMD as the workaround. If the drive vanished immediately after a BIOS settings change, this is the first place to look.[6][2]

The BitLocker trap inside this scenario

This situation and BitLocker recovery are intertwined. Microsoft lists BIOS or UEFI firmware upgrades, moving a protected drive to another computer, motherboard changes and boot order changes among the events that trigger BitLocker recovery, and documents that suspending BitLocker before a planned change avoids it. The recovery key is a 48-digit number, kept where you set it up: ASUS points at the Microsoft account as a location and is blunt that the maker cannot retrieve it for you. So the order is: find the key first, then change settings, update firmware or move hardware. If the recovery prompt is already on screen, do not guess; the key page is reachable from any browser.[7][1]

Firmware: the fix you cannot reach from here

Drive firmware issues are real and documented: a current WD and SanDisk advisory fixes a firmware cause of crashes on certain SSD models under Windows 11 24H2, and pairs the update with a warning to back up and verify critical data first. But notice the catch for this page's problem: firmware updaters are software, and they need a detected drive. A drive absent from the BIOS cannot be firmware-fixed at home. That is one more reason the checks above matter: they are how the drive becomes visible to the tools that can then help it.[8]

When nothing detects the drive

If the drive is invisible in every port, every cable and every computer, the vendors' own route is short: Crucial's endpoint is one power cycle attempt and then replacement, and Seagate's equivalent guidance moves to warranty services for a drive nothing detects. That is also the honest boundary for data recovery: recovery software works on drives the system can see, so the remaining routes are the warranty and, where the data matters more than the drive, a professional service. Resist repeating power cycles or reseating loops on a drive in this state; the vendors document one attempt, not a cycle of them.[2]

Choosing a data recovery service: quotes, privacy and honest guarantees.

Sources

Facts on this page are cited to the publishers’ own documentation.

  1. [1] Microsoft — BitLocker recovery overview. captured 2026-09-12.
  2. [2] Crucial — Why doesn't my desktop recognize my SSD?. captured 2026-09-12.
  3. [3] Seagate — The BIOS does not detect or recognize the solid state drive. captured 2026-09-12.
  4. [4] Seagate — The BIOS does not detect or recognize the ATA / SATA hard drive. captured 2026-09-12.
  5. [5] ASUS — Troubleshooting: cannot find the hard disk drive or SSD (M.2) after motherboard powers on. captured 2026-09-12.
  6. [6] Lenovo — NVMe SSD PCI device will be invisible when Intel VMD is enabled. captured 2026-09-12.
  7. [7] ASUS — BitLocker recovery screen appears after startup / find BitLocker recovery key. captured 2026-09-12.
  8. [8] SanDisk — Internal SSD critical firmware update for Windows 11 24H2 (WD/SanDisk advisory). captured 2026-09-12.