New NVMe SSD Not Showing Up? Work Through These Fixes in Order
You installed a new M.2 SSD, booted up, and it is not there. Before you assume the drive is faulty, know that most missing-drive problems come from a short list of predictable causes, and only a few of them involve bad hardware. Work through this list from the top. The checks run from quickest and most likely to least likely.
Step 1: Find out where it is missing
The fix depends on where the drive fails to appear, so narrow that down first.
| Where you looked | Drive visible? | Most likely cause | Go to |
|---|---|---|---|
| BIOS/UEFI storage or NVMe info page | No | Seating, slot type, lane sharing, or a disabled slot | Steps 3–5 |
| BIOS: yes. Windows Disk Management: yes. File Explorer: no | Partly | The drive has not been initialized or formatted | Step 2 |
| Windows Setup "Where do you want to install Windows?" | No | A storage driver is needed (Intel VMD/RST) | Step 6 |
| Visible, then disappears under load or after a while | Sometimes | Heat, firmware, or a marginal connection | Step 7 |
In most UEFI setups, NVMe drives are listed on a storage, NVMe configuration, or "M.2 information" page, and sometimes in the boot order. A brand-new blank drive may not appear as a boot option at all, so check the storage information page rather than the boot menu.
Step 2: Initialize it in Disk Management (the most common fix)
A new SSD arrives completely blank. Windows will not show it in File Explorer until it has a partition table and a formatted volume.
- Right-click Start and open Disk Management.
- A prompt to initialize the disk usually appears. Choose GPT, which is the right choice for any modern UEFI system.
- Right-click the unallocated space and choose New Simple Volume. Accept the defaults, pick a drive letter, and format as NTFS.
- The drive now appears in File Explorer.
Disk Management lists every drive. Before you initialize or format anything, confirm the disk number and size match the new SSD, and that it shows as "Not Initialized" or "Unallocated". Formatting the wrong disk erases it.
On macOS or Linux the idea is the same: use Disk Utility, or a partitioning tool such as gparted, to create a partition table and a filesystem.
Step 3: Check seating and the standoff
M.2 drives go into the slot at an angle, then get pressed down and secured. If the drive is not fully inserted, it can look fine but make only partial contact.
- The gold contacts should be almost completely hidden inside the slot, with even depth on both sides.
- The standoff (or tool-less latch) should be at the correct length position for your drive. Most consumer drives are 2280, meaning 80 mm long.
- The drive should lie flat when secured. If it bows upward, the standoff is in the wrong spot.
- If the board has an M.2 heatsink, remove the plastic film from its thermal pad, and make sure the heatsink is not pushing the drive out of the slot.
Reseating takes two minutes and fixes more of these problems than people expect. If you need a refresher, see the M.2 installation walkthrough.
Step 4: Check that the slot actually supports NVMe
"M.2" describes the connector shape, not the protocol. An M.2 slot can support NVMe (PCIe), SATA, or both. A small number of slots, particularly on older or budget boards and some laptops, are SATA-only. An NVMe drive in a SATA-only slot will not be detected.
- Check the specifications table in the manual for each M.2 slot. Look for wording like "supports PCIe x4 and SATA modes" or "SATA mode only".
- Check the keying. NVMe drives are almost always M-key. A slot keyed only for B-key or another standard is not meant for them.
- Older platforms may be able to see an NVMe drive as storage but not boot from it. That is a separate limitation, covered in the FAQ.
Step 5: Check for lane sharing and disabled slots
This is the cause most people miss. Motherboards have a limited number of PCIe lanes, so slots and ports often share them. The manual usually includes a table or footnote with rules like these:
- "When M2_2 is populated, SATA ports 5 and 6 are disabled." Here the drive works, but a SATA drive disappears.
- "M2_3 shares bandwidth with the PCIEX4 slot." Here a card in that slot may disable the M.2 slot, or the other way around.
- Some slots on certain platforms are disabled unless a specific CPU type is installed, or need to be switched on manually in the BIOS.
If the drive is missing from one slot, move it to the primary M.2 slot, which is normally the one closest to the CPU and wired directly to it. If it appears there, the drive is fine and the other slot has a sharing rule or a BIOS setting that needs changing. Read the "M.2" and "Storage" sections of the manual. The answer is usually spelled out there.
Look for settings such as "M.2 slot mode", "PCIe bifurcation", or "SATA/PCIe mode" on the storage page. Some boards make you choose a mode per slot. Updating the BIOS can also fix detection problems with newer drives. If you go that route, follow the safe BIOS update steps.
Step 6: Windows Setup cannot see the drive (VMD/RST)
Many recent Intel-based laptops, and some desktops, ship with Intel Volume Management Device (VMD) or RST enabled. With it on, a plain Windows installer cannot see NVMe drives until you load the storage driver. You have two options:
- Load the driver. Download the Intel RST/VMD driver for your exact system from the laptop or motherboard support page, extract it to the installer USB, and choose "Load driver" on the drive selection screen.
- Turn VMD off in the BIOS (sometimes labeled "RAID" vs "AHCI/NVMe" mode). Only do this before installing Windows. Switching it on an existing installation can stop that installation from booting.
On AMD systems, a similar problem appears if the board is set to RAID mode. In that case the AMD RAID driver is needed.
Step 7: The drive drops out intermittently
- Heat. Fast drives can throttle under sustained load, and in rare cases disconnect, without proper cooling. Use the board's M.2 heatsink or add one (browse M.2 heatsinks on Amazon). See NVMe heatsinks for small cases.
- Firmware. Install the drive maker's toolbox utility and check for firmware updates. Back up first.
- Power settings. Aggressive PCIe power-saving (ASPM / Link State Power Management) can cause trouble with some drive and board combinations. Setting PCI Express Link State Power Management to "Off" in the Windows power plan is a quick test.
Step 8: Test the drive somewhere else
If none of the above helps, test the drive in a USB NVMe enclosure or another computer. If it is detected there, the drive is healthy and the problem is with your board or slot. If it is not detected anywhere, start a return or warranty claim with the seller or manufacturer.
An enclosure is useful well beyond this test. When the old drive comes out, it becomes fast portable storage. Pick an enclosure that supports NVMe. Some cheap ones handle M.2 SATA only.
Frequently asked questions
Why does my NVMe SSD show in BIOS but not in Windows?
It almost always needs to be initialized (GPT) and formatted in Disk Management. A new drive has no partitions, so File Explorer has nothing to display.
Can an M.2 SATA slot run an NVMe drive?
No. A SATA-only M.2 slot cannot talk to an NVMe drive even though the connector fits. Check the manual's slot specifications.
My old motherboard sees the NVMe drive but will not boot from it. Why?
Booting from NVMe needs UEFI firmware support. Some older boards can use the drive as storage but cannot boot from it. Check for a BIOS update that adds NVMe boot support, or keep the operating system on a SATA drive.
Will adding an M.2 drive disable my SATA ports?
On many boards, filling certain M.2 slots disables specific SATA ports because they share lanes. The manual lists which ones.
Do I need to install NVMe drivers?
Windows 10 and 11 include a standard NVMe driver, so it works out of the box. The exception is when the system uses Intel VMD/RST or AMD RAID mode, which needs the vendor driver.
Wrapping up
Most missing SSDs are not defective. Start by finding out where the drive is missing. Then initialize it if Windows can see it in Disk Management, reseat it, and read the motherboard manual's M.2 lane-sharing rules. Load the VMD driver if the Windows installer is the problem. Test it in an enclosure before you send it back. Following that order solves almost every case.