How to Fix an SSD That Shows Up in BIOS but Not in Windows September 2026 Guide

You installed a new SSD, your BIOS recognizes it perfectly, but Windows refuses to acknowledge it exists. This is one of the most frustrating storage issues PC builders and upgraders face, and the good news is that it is almost always fixable without replacing your drive.

When your SSD shows up in BIOS but not in Windows, the problem usually comes down to one of six things: an uninitialized disk, a missing drive letter, outdated storage controller drivers, incorrect BIOS storage mode (AHCI vs RAID), M.2 slot incompatibility, or encryption interference. I have dealt with every one of these scenarios across dozens of builds, and each has a clear fix.

Here is a quick summary of the troubleshooting sequence before we go into detail. Open Disk Management and look for unallocated space. If the drive appears there, initialize it and assign a drive letter. If Disk Management does not see it, update your storage controller drivers in Device Manager. If that fails, check your BIOS storage controller mode and switch from RAID to AHCI if needed. Reseat the physical connections, verify M.2 compatibility, and rule out BitLocker interference.

Follow the steps below in order. Most people find their fix within the first three steps, but I have included advanced troubleshooting for stubborn cases where the basics do not work.

Why Your SSD Shows Up in BIOS But Not in Windows

The reason this happens comes down to how BIOS and Windows communicate with storage devices differently. Your BIOS talks directly to the hardware at a low level, so it can detect any drive that is physically connected and receiving power. Windows, on the other hand, relies on storage controller drivers as a middleman between the operating system and your drive.

If those drivers are missing, outdated, or configured incorrectly, Windows simply cannot see the drive even though the BIOS confirmed it is there. Think of it like a phone that is connected to Wi-Fi but cannot load any websites because the DNS server is misconfigured. The hardware link exists, but the software layer is broken.

Here are the most common causes, ranked by how often I see them in practice:

• Uninitialized or unallocated disk – Brand new SSDs have no partition table, so Windows Disk Management sees the space but does not mount it as a usable drive. This is the single most common cause.
• Missing drive letter – The SSD is initialized and formatted but has no letter assigned, making it invisible in File Explorer even though Disk Management shows it.
• Outdated or missing storage controller drivers – NVMe drives especially require specific drivers that may not be included with a fresh Windows installation.
• Wrong BIOS storage mode – If your BIOS is set to RAID or Intel RST mode but Windows was installed in AHCI mode, the storage controller cannot communicate with the drive.
• M.2 slot incompatibility – Some M.2 slots only support SATA or only support NVMe, and putting the wrong type in the wrong slot means Windows will never see it.
• BitLocker or encryption lockout – Encrypted drives from another Windows installation may be blocked from mounting until you provide a recovery key or disable encryption.

Less common but still possible causes include a loose SATA or M.2 connection, a faulty SATA cable, a motherboard BIOS bug requiring an update, or an SSD that has actually failed despite being detected at the hardware level.

Step 1: Check Disk Management First

Disk Management is the first place you should look when Windows does not show your SSD, because it reveals drives that File Explorer hides. This built-in Windows tool shows every storage device connected to your system, including uninitialized drives and partitions without letters.

To open Disk Management, right-click the Start button and select Disk Management from the menu. You can also press Windows Key + X and choose it from the list. Alternatively, press Windows Key + R, type diskmgmt.msc, and press Enter.

When Disk Management opens, look at the bottom section where your drives are displayed as horizontal bars. If your SSD appears as a black bar labeled Unallocated, the drive needs to be initialized and partitioned. If it shows up as a blue bar with no letter, it just needs a drive letter assignment. If the drive does not appear at all, skip ahead to Step 4 for driver troubleshooting.

Before moving on, try clicking Action in the menu bar and selecting Rescan Disks. This forces Windows to refresh its storage device list, and sometimes a newly connected drive will appear after a rescan even though it was not there initially.

Step 2: Initialize the SSD

If your SSD shows up in Disk Management as unallocated space with a black bar, it needs to be initialized before Windows can use it. Initialization writes a partition table to the drive so Windows can create volumes on it. This is normal for brand new SSDs straight out of the box.

If Disk Management does not prompt you automatically, right-click the disk label on the left side (it will say Unknown or Not Initialized) and select Initialize Disk. A dialog box will appear asking you to choose a partition style: GPT (GUID Partition Table) or MBR (Master Boot Record).

Choose GPT unless you are running a very old system. GPT supports drives larger than 2TB, allows unlimited partitions, and is required for UEFI-based systems which cover virtually every PC from the last decade. MBR is a legacy format that limits you to 2TB and four primary partitions.

After initialization, the disk will show as Unallocated space with a black bar. Right-click that unallocated space and select New Simple Volume. Follow the wizard to set the volume size (use the maximum if this is a new drive), assign a drive letter, and choose NTFS as the file system. When the wizard finishes, your SSD should appear in File Explorer immediately.

One thing to note: initializing a disk does not erase data on an already-formatted drive, but if the drive contains data from another system and shows as unknown, the original partition table may be corrupted. In that case, initialization will make the space available but you will lose access to any existing data without recovery tools.

Step 3: Assign a Drive Letter

Sometimes your SSD is already initialized and formatted, but Windows has not given it a drive letter, making it invisible in File Explorer. This happens frequently when you move a drive from one system to another or when Windows has a letter conflict with another device.

Open Disk Management and look for your SSD in the bottom panel. If you see a healthy partition with a blue bar but no letter next to the volume name, right-click the partition and select Change Drive Letter and Paths. Click Add, choose a letter (I recommend picking one later in the alphabet like S or T to avoid conflicts with USB drives), and click OK.

Your SSD should immediately appear in File Explorer after the letter is assigned. If Windows gives you an error about the letter being in use, choose a different letter. Conflicts happen when a network drive or USB device has already claimed the letter Windows tried to assign.

If Disk Management will not let you assign a letter, you can try the command-line alternative. Open Command Prompt as Administrator, type diskpart, then type list volume to see all volumes. Find your SSD in the list, type select volume X (replace X with the volume number), and then type assign letter=S with whatever letter you want. Type exit when you are done.

Step 4: Update Storage Controller Drivers

If your SSD does not appear in Disk Management at all, the problem is likely a driver issue. Windows needs a storage controller driver to communicate with the hardware, and if that driver is missing, outdated, or incompatible, the drive remains invisible even though the BIOS detects it.

Open Device Manager by right-clicking the Start button and selecting it from the menu. Expand the Storage controllers category (sometimes called IDE ATA/ATAPI controllers on older systems). Look for any devices with a yellow exclamation mark, which indicates a driver problem.

Right-click the storage controller and select Update driver. Choose Browse my computer for drivers and point it to any driver files you have downloaded. For NVMe drives specifically, I recommend downloading the latest driver directly from your motherboard manufacturer or SSD manufacturer. Samsung has its own NVMe driver, and Intel provides the Rapid Storage Technology (RST) driver that covers many configurations.

If you just installed Windows and the SSD is still not showing, the issue may be that the Windows installation media lacks the NVMe driver entirely. This is common with older Windows 10 installation USB drives on newer NVMe hardware. Download the latest storage driver from your motherboard manufacturer, put it on the same USB drive, and use the Load driver option during Windows setup.

Another approach is to uninstall the current storage controller driver and let Windows reinstall it. In Device Manager, right-click the controller, select Uninstall device, then restart your computer. Windows will detect the hardware on boot and install a fresh driver automatically.

For users coming from Reddit threads about this exact problem, the fix that comes up repeatedly is unchecking Hide incompatible drivers in the BIOS boot override menu. Some motherboards hide certain storage drivers by default, and unhiding them allows Windows to load the correct controller driver during boot.

Step 5: Check BIOS Storage Settings

BIOS storage controller mode is one of the most common culprits when a drive shows up in BIOS but disappears in Windows. The mode determines how the storage controller communicates with the operating system, and if it is set wrong, Windows cannot find your SSD.

Restart your computer and enter the BIOS by pressing Delete, F2, or whatever key your motherboard uses during POST. Navigate to the storage or SATA configuration section. The exact location varies by manufacturer: ASUS puts it under Advanced, MSI under Settings, and Gigabyte under Peripherals or Settings.

Look for SATA Mode or Storage Controller Mode. You will typically see three options: AHCI, RAID, and sometimes Intel RST (Rapid Storage Technology). Here is how each mode affects SSD detection:

AHCI (Advanced Host Controller Interface) is the standard mode for individual drives. Windows includes built-in AHCI drivers, so any SSD should work immediately in this mode without additional drivers. If you are not running a RAID array, this is the mode you want.

RAID mode is for combining multiple drives into arrays. When RAID mode is enabled, Windows needs the manufacturer’s RAID driver to see any connected drives. If you switched to RAID mode or bought a prebuilt with RAID enabled, Windows will not detect your SSD unless you install the Intel RST or equivalent RAID driver. Many users accidentally have RAID mode enabled without realizing it.

Intel RST is Intel’s proprietary storage technology that works on top of RAID mode. It offers features like Smart Response Technology (SSD caching) but requires the Intel RST driver installed in Windows. If your BIOS is set to Intel RST and Windows does not have the driver, the SSD will not appear.

If your system is set to RAID or Intel RST, try switching to AHCI mode. Save the BIOS settings and restart. Windows should now detect the SSD using its built-in AHCI drivers. However, if Windows was installed in RAID mode, switching to AHCI may cause a blue screen on boot because Windows is looking for the RAID driver. In that case, you need to enable AHCI in Safe Mode first or change the registry setting storahci start value to 0 before switching modes in BIOS.

While you are in the BIOS, also verify that the SATA port your SSD is connected to is enabled. Some motherboards disable certain SATA ports by default, especially when M.2 slots are occupied because some M.2 slots share lanes with SATA ports. Check the SATA configuration page and make sure all ports are set to Enabled.

Step 6: Reseat Physical Connections

Physical connection issues are less common but still worth checking, especially for newly installed drives. A cable that looks connected may have a loose contact that provides enough power for BIOS detection but causes intermittent issues in Windows.

Power off your computer completely and unplug the power cable. For SATA SSDs, disconnect and reconnect both the SATA data cable and the SATA power cable. Try using a different SATA port on the motherboard, since individual ports can fail. Also try a different SATA cable, as faulty cables are a surprisingly frequent cause of detection issues.

For M.2 SSDs, unscrew the retention screw, remove the drive, and reinsert it carefully. The M.2 connector can be tricky; you need to insert the drive at a 30-degree angle and press it down until it seats flat against the motherboard. An improperly seated M.2 drive can be detected by BIOS but fail under Windows load.

If you are using a PCIe adapter card for an NVMe drive, make sure the card is fully seated in the PCIe slot and that any required power cables are connected. Reseat the card in a different PCIe slot if available.

M.2 SATA vs M.2 NVMe: Why Your Slot Might Be Wrong

One of the most confusing aspects of M.2 SSDs is that they come in two fundamentally different types that look almost identical but use completely different technologies. Putting the wrong type in the wrong slot can cause exactly this problem: BIOS detects something, but Windows cannot use it.

M.2 SATA drives use the same SATA protocol as traditional 2.5-inch SSDs but in the M.2 form factor. They max out at around 550 MB/s and connect through the SATA controller.

M.2 NVMe drives use the PCIe interface and can reach speeds of 3,500 MB/s to over 7,000 MB/s depending on the PCIe generation. They connect through the PCIe bus and require NVMe driver support.

Not all M.2 slots support both types. Some motherboard M.2 slots only support NVMe (PCIe) drives, while others only support SATA drives. Check your motherboard manual to see which M.2 slots support which types. If you put an M.2 SATA drive in an NVMe-only slot, the BIOS might show the slot as populated but Windows will never see the drive.

To identify what you have, look at the notches on the connector edge of your M.2 drive. The notch positions correspond to different key types. M.2 SATA drives typically have a B+M key configuration (two notches), while M.2 NVMe drives usually have an M key only (one notch). The motherboard M.2 slot will have a corresponding key ridge that only accepts the matching drive type.

BitLocker and Encryption Interference

BitLocker and other full-disk encryption can prevent Windows from mounting a drive that was encrypted on a different system. If your SSD came from another Windows installation that had BitLocker enabled, Windows may detect the drive in Disk Management but show it as locked or read-only rather than mounting it normally.

In Disk Management, an encrypted drive may show as a healthy partition with a lock icon. In File Explorer, it may appear with a padlock icon. To access the drive, you need the BitLocker recovery key from the original system, which is typically saved to a Microsoft account, printed, or saved to a file.

If you have the recovery key, open File Explorer, right-click the locked drive, select Unlock Drive, and enter the recovery key. Once unlocked, you can either access your data or disable BitLocker by right-clicking the drive, selecting Manage BitLocker, and choosing Turn off BitLocker. Decryption can take a while depending on drive size.

If you do not have the recovery key and do not need the data, you can bypass BitLocker entirely by opening Disk Management, deleting all partitions on the drive, and creating a new simple volume. This erases everything on the drive, including the encryption, giving you a clean drive that Windows can use.

This issue is commonly overlooked in troubleshooting guides, but I have seen it catch people off guard frequently, especially when repurposing drives from corporate laptops that had BitLocker enforced by IT policy.

Advanced Fixes: Diskpart and Command Line Tools

When the graphical Disk Management tools are not working, the command-line utility diskpart gives you more direct control over disk operations. This is the tool to use when Disk Management shows errors, refuses to initialize a disk, or when you need to completely clean a problematic drive.

Open Command Prompt as Administrator. Type diskpart and press Enter. Then type list disk to see all connected drives, including ones that Disk Management might not display properly. Identify your SSD by its size and note the disk number.

Type select disk X (replace X with your SSD number) and press Enter. Be absolutely certain you have selected the correct disk before proceeding, because the next commands will erase all data on it.

To completely reset the drive, type clean and press Enter. This removes all partition and volume information, essentially returning the drive to a factory-fresh state. After cleaning, type convert gpt to set the partition table to GPT, or convert mbr if you need the legacy format.

Now create a new partition by typing create partition primary, then format fs=ntfs quick to format it, and assign letter=S to give it a drive letter. Type exit to leave diskpart, and your SSD should appear in File Explorer ready to use.

Another useful command is list volume within diskpart, which shows every volume even if it has no letter or is hidden. If you see your SSD volume here but not in Disk Management, you can select it and assign a letter directly.

For drives that have a corrupted partition table but contain data you want to keep, try chkdsk X: /f (replace X with the drive letter) from a regular Command Prompt. This scans for and repairs file system errors that might be preventing Windows from mounting the drive.

When Your SSD Might Be Faulty

If you have tried every software fix and your SSD still does not appear in Windows, the drive itself may have a hardware fault. SSDs can fail in a way where the controller chip is partially functional (allowing BIOS detection) but the flash memory or internal logic is corrupted.

Signs that point to a physically faulty SSD include: the drive appearing and disappearing in BIOS intermittently, the drive showing up with an incorrect or zero capacity, extremely slow BIOS POST times when the drive is connected, or the drive being detected as a different model than what it actually is.

The most definitive test is to install the SSD in a different computer. If a known-good system also cannot see the drive in Windows or Disk Management despite BIOS detection, the SSD is almost certainly faulty and needs replacement. Most SSDs come with a 3 to 5 year warranty, so check with the manufacturer for a replacement if the drive is still covered.

If the drive contains important data, stop using it immediately and consult a professional data recovery service. Continuing to power cycle a failing drive can cause further damage and reduce the chances of successful recovery. Professional recovery can be expensive, but it is the safest option for irreplaceable data.

Before declaring the drive dead, try updating your motherboard BIOS. I have seen cases on Gigabyte Z690 boards and other platforms where a BIOS update fixed NVMe detection issues that no amount of Windows troubleshooting could solve. Check your motherboard manufacturer’s website for the latest BIOS version and changelog notes mentioning storage fixes.

FAQ’s

Conclusion

Fixing an SSD that shows up in BIOS but not in Windows comes down to working through a logical troubleshooting sequence: check Disk Management, initialize the drive, assign a letter, update drivers, verify BIOS storage mode, and reseat connections. The vast majority of cases are resolved within the first three steps, and the more advanced fixes like diskpart and BIOS mode changes cover the stubborn ones.

If you have exhausted every step and the drive still does not appear in Windows after testing in a second computer, it is likely a hardware failure and time to use the warranty. But before you get there, double-check that your M.2 slot type matches your drive type, since that incompatibility is easy to miss and affects a surprising number of builds in 2026.