Samsung 990 PRO Not Showing Up? Check BIOS, Windows and the M.2 Slot

You install an SSD, close the case and open File Explorer. There is no new drive letter. That can happen with a perfectly working new SSD because Windows has no usable volume to display. It can also happen because the drive never reached the operating system. These need different solutions.

This guide follows the Samsung 990 PRO from its physical connection to the place you expect to see your files. If the drive previously contained important data, protect that data before attempting a repair.

Find the Missing Layer First

Use the firmware’s storage or NVMe inventory rather than the boot-priority list alone. A new blank SSD may have no bootable operating system, so its absence as a boot option does not prove that the hardware is missing.

Check the M.2 Slot, Not Just the Shape

The 990 PRO is a PCIe NVMe M.2 2280 drive. The number 2280 describes a board approximately 22 mm wide and 80 mm long. It does not mean that every socket accepting an 80 mm M.2 board supports this drive.

Read the motherboard or computer manual for the exact slot. An M.2 SATA-only socket is different from a PCIe NVMe socket. Some systems also share connections between an M.2 slot, expansion slots and SATA ports. The permitted combination depends on that board and processor.

1. Record the PC or motherboard model and the slot designation.
2. Confirm PCIe NVMe support and the supported module length.
3. For a physical inspection, shut down and disconnect power as directed by the PC maker. Follow its electrostatic-handling procedure.
4. Check that the module is fully inserted and secured with the correct standoff and fixing method, without bending the board.
5. If the manual permits another compatible slot, use it as a controlled isolation test.

An enclosure introduces another compatibility check: an M.2 SATA enclosure is not automatically an NVMe enclosure. If an external drive is detected but repeatedly disconnects, use the external SSD connection guide rather than treating every failure as an internal-slot fault.

When Windows Sees the Disk but Explorer Does Not

Open Disk Management and identify the SSD by its capacity and other available device details. Do not choose a disk just because it is labelled Disk 1 or appears near the bottom of the window. Those positions can change.

A genuinely new, blank SSD may need initialisation, a partition, a filesystem and a drive letter before Explorer can use it. Confirm that it is the intended empty drive before following the Windows new-disk procedure. A newly purchased drive that contains a clone or restored data is no longer an empty disk.

A previously used SSD needs a different approach. A missing letter, an unsupported filesystem, encryption, an offline state or damaged partition information can all prevent ordinary access. Read the displayed state and exact error before acting. If an expected data volume appears RAW or unallocated, do not create a new volume over it.

Leave system, recovery and EFI partitions alone. If the volume is encrypted, use its proper unlock process and recovery information; formatting it removes the existing structure rather than unlocking it.

Controller Settings and Samsung Magician

If firmware detects the drive but Windows does not, check the PC maker’s storage-controller documentation. A managed RAID or VMD configuration may require the appropriate manufacturer-supported controller driver. Do not switch RAID, VMD or AHCI settings at random: an existing Windows installation can depend on its current boot configuration.

Magician is useful for supported drive information, diagnostics and firmware management, but its device list is not a substitute for checking whether Windows can see the disk. Certain controllers, RAID configurations and external adapters limit what a management application can identify.

Use the current supported Magician version, refresh its device list and compare it with Windows. If Windows can read and write the drive but Magician cannot identify it, investigate that software path. Repartitioning the SSD will not make an unsupported bridge expose management commands.

Back up accessible data before a firmware update, confirm the exact drive and follow the supported procedure with stable power. Do not use Secure Erase as a troubleshooting shortcut for missing files.

Detection and Speed Are Separate Questions

Once the drive appears consistently, test an ordinary file operation before moving a complete workload. Then check the negotiated connection and performance under a suitable workload. A compatible older PCIe connection can limit throughput without making the SSD defective; a drive’s advertised peak rate is not a promise for every file copy.

For an external workflow, the USB-C SSD speed guide explains why a fast drive can still be limited by its cable, enclosure or host port.

Record These Details Before Replacing the SSD

Keep the motherboard model, slot name, SSD part number, firmware detection result, Windows disk status and exact error together. Record whether the SSD is new, cloned or previously used, and whether another compatible slot changes the result.

The practical answer: investigate slot support and installation when the firmware cannot detect the drive. Investigate Windows access when firmware sees it. Investigate the volume when Windows sees the disk but Explorer does not. That sequence avoids buying another SSD to solve a drive-letter problem, or formatting a data disk to solve a connection problem.

Frequently Asked Questions