Affiliate links. I may earn a commission at no extra cost to you. #ad
I get this after the second SSD is already in the cart. Screw is down, boot menu is empty, and they’re pricing motherboards. A lot of those drives are fine. The BIOS page they opened only lists things that can boot. Or the slot is the SATA kind and the stick is NVMe. Or it looks screwed flat and the gold fingers are still sitting a millimeter short. I don’t buy the next part until I know which one it is.
Missing from the boot list is a different job
People say “not in BIOS” when they mean the boot menu doesn’t have Windows on it. Those are not the same screen. Boot Order is a list of loaders. A new drive has no loader. An old drive you just moved might have one the board won’t offer until CSM is off, or until you pick the disk itself from a one-time boot menu (F8, F11, F12, the splash tells you). The hardware page is the one I trust.
| What you see | What I think | What I don’t buy yet |
|---|---|---|
| Model name is on the NVMe page, Boot Order has no Windows Boot Manager | Empty drive, or the loader isn’t there. Detection already worked. | A new motherboard. You don’t have a dead slot. |
| Model name is only under Intel VMD, RST, or RAID | The board parked it behind that controller. It’s still there. | Another SSD. And don’t turn VMD off if this Windows install used to boot. |
| No model name on any storage page, in any slot | Not seated, wrong slot type, or the stick is actually dead. | A Windows repair USB. Drivers don’t run before BIOS sees the drive. |
| It shows, then it’s gone, then it’s back next boot | Controller or the connection. Clone while it still shows. | A weekend of reseating it and hoping. |
| BIOS sees the model. File Explorer doesn’t. | No partition or no letter. Disk Management still lists it. BitLocker is a lock, not a missing disk. If Disk Management is blank too, that’s the VMD/driver case above, not a dead stick. | A new stick because Explorer is empty. |
Seat it before you blame it
Power off. Desktop: PSU switch off, cord out, hold the case button ten seconds. Laptop: bottom cover off, and if the pack isn’t a pillow I unplug the battery connector before I touch the stick. A pack that’s already swelling is the swollen-battery guide. I don’t pry those.
The drive goes in at an angle. Gold fingers all the way into the socket until you feel it stop, then you push the other end down onto the standoff and screw it. If you screw it down first and the fingers are short, it sits flat and does nothing. I take it out and do that again even when it “looks fine.” On a stick that’s been in before, a clean band across the fingers means it wasn’t in. A new one is clean everywhere, so that trick doesn’t work.
- Standoff has to be in the hole that matches the length. 2280 is the normal desktop and a lot of laptops. 2242 is shorter and common in smaller laptops. 2230 is the little one, some thin laptops and handhelds. 22110 is the long desktop one. A 2280 over a standoff that’s still in the 2242 hole will bow. A 2230 with no standoff under the screw hole just floats.
- The little screw is not a random case screw. Too long and it can hit the board under the standoff. If you lost it, don’t jam a fan screw in there. The hold-down is the same small Phillips as the rest of the cover. If the bit doesn’t seat, stop. That’s the screwdriver post, not “more force.”
- Shields over the drive are often a heatsink with a pad. Note which way the pad faced. A thick pad on top of the chips bows the stick out of the socket when you screw the shield down. A thick one under the stick lifts the connector the same way. Factory label on the chips stays. That’s not tape you peel so it will “fit.”
- Don’t put it in the short wireless slot. That card is the Wi-Fi module. The key is different. If the stick doesn’t drop in without force, it’s the wrong socket.
The slot might not speak NVMe
M.2 is the shape. NVMe is the language, and it’s PCIe. Some M.2 sockets only speak SATA. The stick clicks in, because a lot of those sockets are still M-key, and then BIOS has nothing to say. Older laptops do this. Cheap boards do this on slot 2 while slot 1 is the real NVMe socket. The manual has one sentence on it. I read that sentence before I order a second drive.
A SATA M.2 usually has two notches (B+M). An NVMe stick usually has one notch, on the M side. One notch into a slot that won’t take it means don’t force it. Two notches doesn’t promise it’ll work either. A B+M SATA drive can physically sit in an NVMe-only slot and still never show up. The notch is not the spec.
PCIe generation is the excuse I hear next. A Gen4 stick in a Gen3 slot still shows up. It just runs at Gen3. A Gen3 stick in a Gen4 slot shows up. Buying a Gen5 drive because the old board “can’t see NVMe” doesn’t fix a dark slot. If the board never had an NVMe socket, a faster stick doesn’t grow one.
Shared ports are the other manual sentence. A lot of boards shut off one or two SATA ports when a chipset M.2 is filled. The primary NVMe slot, the one wired to the CPU, often shuts off none. A few boards do the reverse: the M.2 stays dark while a disk is plugged into the shared SATA port. Unplug the SATA data cables, look again, then put them back. The boot disk is sometimes the shared one, so leaving it plugged in is how you miss the test.
Settings that move it, not kill it
Intel boards from the last few years can tuck the NVMe under VMD. Older boards do a similar trick with RST or RAID mode. The model name moves to that submenu. Windows setup then acts blind until you load Intel’s storage driver off a USB. The stick isn’t dead. If this machine used to boot Windows, leave VMD where it was. Turning it off so the name looks nicer can make that install throw an inaccessible-boot stop until you turn it back on.
CSM is the legacy switch. With it on, a UEFI-only disk often disappears from the boot menu and stays on the NVMe page. That’s still “detected.” A few boards hide the drive entirely until CSM is disabled. If I flip it, I write down the old value first. An old Windows install that boots legacy will not come back up with CSM off. Secure Boot is not this problem. It can refuse a USB installer. It doesn’t erase a drive from the hardware list.
If the board was running two sticks as a RAID and now you see one disk or none, stop. Deleting the array to make a drive “appear” can wipe it. RAID 0 is gone. A mirror sometimes isn’t, and the BIOS warning is not the spec. That’s a data job. I don’t do it to win an argument with the BIOS screen.
The enclosure is the test
One known-good USB enclosure answers the only question that matters. Does this stick enumerate on a different machine? NVMe side of the enclosure, not the SATA pocket. A charge-only USB-C cable will show you nothing, so I swap the cable once before I call the drive dead. If the model name pops up on the other computer, the SSD is alive and the slot or the seating is wrong. Invisible in the enclosure is not a cart yet. One bad adapter does that too. I shop when a different stick shows up in the same socket and this one stays invisible after the cable swap.
On the bench
USB-C NVMe enclosure (the test, not a bench trophy)
This is how I separate a dead stick from a dead slot without buying a motherboard. A SATA-only enclosure will not talk to NVMe. Use the NVMe side if the box does both.
- 10Gbps is enough. You’re asking it to show up, not to win a speed test.
- One enclosure can be bad. If you have a second machine and a second cable and it’s still invisible, I trust that more than one flaky adapter.
Laptop notes
Some of these don’t have a stick at all. The storage is soldered, or it’s a tiny eMMC, and the M.2 pads on the board are empty footprints with no connector. If you can’t see a module and you can’t see a socket, stop. There’s nothing to reseat. The upgrade guide says the same thing. I don’t order a 2280 for a board that has nowhere to put it.
- Second socket: look at it. A plastic outline with no metal connector is not a slot the factory “forgot to enable.”
- Length is in the service manual. A 2280 in a 2242 machine hits the fan or the battery. I’ve seen people screw it down anyway.
- After the battery is plugged back in, then you check BIOS. Checking with the pack still unplugged is fine on most of them if the charger is in. If it acts drunk that way, reconnect the pack and look again before you condemn the stick.
- BIOS on a lot of laptops hides the useful page behind F10, or an Advanced mode, or a key the splash doesn’t print. Search the model and “BIOS advanced NVMe” before you decide the drive is gone. I don’t pay for a BIOS mod off a forum.
Desktop extras, still before a new board
Two M.2 sockets is the easy test. Same stick, other socket, look for the model name. Shows in socket 2 and not socket 1: the stick is fine. Socket 1 is disabled, sharing lanes, or dead. I don’t call socket 1 the SATA slot just because socket 2 worked. On a lot of boards the SATA-only socket is the second one. No second socket: the enclosure test above is the one I trust. A PCIe adapter card is a later experiment, and only an NVMe adapter. The cheap ones that need a SATA cable back to the board are SATA adapters. An NVMe stick on one of those stays invisible. If that adapter has a power plug, I connect it before I blame the drive.
Date in BIOS also years off? That’s the coin-cell guide. A tired cell can dump settings, and a dumped setting can change boot order or turn a storage option off. It does not usually delete the model name off the NVMe page. I still read that page after I set the clock, because I’ve had a board come back with CSM flipped and the drive “gone” from the boot list only.
A BIOS update is late
New stick, board from a few years back, enclosure says the stick is fine, slot is actually NVMe, seating is honest. Then I read the BIOS notes on the board maker’s site for that exact revision. Sometimes they added storage support and the notes say so. Flash from their built-in tool, file from their support page, power that won’t die halfway. Laptop stays on the charger. I don’t flash a random “NVMe mod” someone posted. And I don’t flash as the first move when I haven’t reseated the drive.
When the stick is actually the part
A different known-good stick shows in that socket, and this one stays invisible in the enclosure after a cable swap. That’s a dead SSD. A second slot that also ignores it is extra proof, not a requirement. If it sometimes shows, you don’t shop yet. You clone while it still enumerates. That’s The disk is dying: clone it before you shop. A drive that vanishes and comes back is the same rule as the lifespan post. Copy off, then replace. A brand new stick that never enumerates anywhere is a return, not a motherboard.
On the bench
Replacement 1TB TLC NVMe, only after the slot is proven
Buy this when a different stick shows up in that socket and the old one stays invisible in the enclosure. Not before. Match the length the socket uses. A browser laptop can be a cheap DRAM-less drive. A work disk, I stick with a known TLC 1TB and I don’t chase PCIe 5.0 numbers on a board that just needed a drive that enumerates.
- 2242 or 2230 machines don’t take a 2280. Read the manual before you add it to the cart.
- If the data still matters and the old stick sometimes appears, clone first. The upgrade guide is the order. This post doesn’t replace it.
Verdict
Model name on a storage page means the drive is there. Look at that page before Boot Order. Reseat it, confirm the slot is NVMe, then let a USB enclosure tell you whether the stick or the socket is lying. A new motherboard is the last part on the list, and most of these never get there.