You're confused about why your SSD doesn't initialize when using an adapter.
You're confused about why your SSD doesn't initialize when using an adapter.
I just put in a NVMe M.2 card with a 2TB 970 EVO Plus, but when I try to set it up I see this problem. My board is an X370 MSE Gaming Plus and only one M.2 port is taken.
Yes, you're viewing Disk Management to attempt initializing the drive. It appears in one of the PCIe Gen 3.0+ slots on the motherboard, though several others remain PCIe 2.0. Some NVMe devices strictly require a Gen 3.0 or newer port.
I agree with @SlayerOfHellWyrm. Many boards released when PCIe3 was introduced didn’t include it. Also, the processor matters—this board uses an M.2 slot, suggesting it’s for auxiliary storage or dual boot. Some older CPUs can’t boot from a PCIe setup like this. For Intel, it seems to be 2nd-gen Core i3/5/7 models, and I’m not sure about Ryzen yet.
NVMe startup depends on UEFI firmware version 2.3.1 or higher, typical for systems released after 2012. To meet these requirements, ensure your system runs in UEFI mode, uses a compatible operating system—Windows 7 needs additional updates and has restricted support, while Windows XP and earlier are not supported. The hardware must feature a PCIe Gen 3.0 or newer interface, and the BIOS should include an NVMe boot module (not all models do). For processors, any Ryzen chip is acceptable, and Intel supports any Z-series chipset with Z97 or newer. Certain server-grade C-series chips are compatible, but confirm directly with the manufacturer. Generally, these technical details are less critical for supplemental data drivers; the key factors remain PCIe version and supported OS.
It appears the white device is connected via PCI_E4, but the disk isn't showing up with the correct error. After trying to reinsert the adapter and SSD without success, it seems the problem might lie with the adapter itself.
It seems you're considering a few possibilities. Confusing M.2 SAT and M.2 PCIe is common and could cause problems. If the slot isn't at x1, another issue might exist. A faulty drive or adapter could also be the culprit. You might want to try another computer, preferably one you can install the M.2 in directly to verify functionality.