This guide explains the differences between a missing SATA or NVMe drive, a missing startup entry and an installer that requires a storage driver. Follow the diagnostic sequence appropriate to your computer before selecting any repair.
Identify Which Stage Cannot Detect The SSD
An SSD that does not appear in a computer’s BIOS or UEFI settings can prevent Windows from starting, interrupt an upgrade or leave a newly purchased storage device unavailable. Before opening the computer or changing a firmware setting, determine exactly where the drive is missing. A drive that cannot be identified by the motherboard is a different problem from a recognized drive that does not have a bootable operating system. A drive that is visible to the firmware but not to Windows Setup presents another distinct situation.
BIOS is commonly used as a general term for firmware setup, even on relatively modern computers that use UEFI. The particular setup interface and storage information available depend on your motherboard and computer model. Do not expect every computer to display the same screens. Some list detected SATA disks separately from PCIe storage or show devices under a storage controller menu instead of a general system-information page.
| Observation | First Investigation |
|---|---|
| SSD absent from the appropriate firmware storage inventory | Interface compatibility, installation, controller settings and hardware. |
| SSD listed in storage inventory but absent from boot options | Boot entries, operating-system availability and startup configuration. |
| SSD detected by firmware but missing in Windows Setup | Supported storage controller drivers and installation media. |
| SSD present in Windows Disk Management but absent from File Explorer | Partitions, access, volume state and drive letters. |
| Existing SSD intermittently appears or disappears | Protect data first, then investigate connections and drive reliability. |
Do not assume that a missing Windows Boot Manager entry establishes that the physical drive is dead. Our No Bootable Device Found guide addresses that related startup symptom. The following procedure focuses on identifying the storage device before attempting operating-system repair.
Protect Important Files And Recovery Credentials
Decide whether the SSD is a genuinely new empty drive or contains data that you need to retain. A new drive can be replaced without recovering files, but an existing SSD that contains the only copy of your work requires a different approach. If the original drive sometimes becomes accessible, prioritize an independent copy of important files rather than spending the available operating time benchmarking or testing every possible setting. Verify that representative copies open from the independent destination.
A drive that repeatedly disconnects, reports serious diagnostic errors or has suffered damage may need professional assessment. Repeated power cycling and writes to an unstable storage device can complicate the recovery situation. Do not open an SSD enclosure or try physical component repairs without appropriate qualifications. If there is an electrical smell, visible damage or unusually high heat, stop operating the equipment and seek qualified service.
Drive encryption also matters. On an authorized Windows computer using BitLocker or device encryption, ensure that the required recovery key is available separately before making storage or firmware changes. Microsoft explains why a change in the startup environment can require additional verification in its BitLocker recovery guidance. Our BitLocker recovery key guide explains how to prepare this information. Protect the key from public disclosure. Neither storage recognition nor a successful physical repair removes the need for the legitimate encryption credentials.
Do not initialize, format, secure-erase or delete partitions on a drive that may contain valuable information. These actions do not repair a firmware-level identification problem. See Best Backup Software For Windows for future backup planning. If important files have no independent copy, discuss recovery options before approving a hardware return or repair that may destroy the original data.
Check SATA, M.2 And NVMe Compatibility
The shape of an SSD does not establish how it communicates with the computer. A typical 2.5-inch internal SATA SSD connects through a SATA interface. An M.2 SSD is a small module that can use different storage interfaces. Some M.2 drives use SATA, while many modern M.2 drives use PCI Express with NVMe. A socket that accepts the physical module may not support the storage interface required by that module.
Identify the exact SSD part number and the computer or motherboard model, including its revision where relevant. Consult the official specification for both. Look for support for the required interface, module dimensions and particular socket. A designation such as 2280 describes module dimensions, not the communication protocol. Do not buy a replacement merely because it looks similar to the original.
| Drive Type | Compatibility To Verify |
|---|---|
| 2.5-Inch SATA SSD | Compatible SATA data and power connection or the correct laptop caddy. |
| M.2 SATA SSD | M.2 storage socket supporting SATA and the specified card dimensions. |
| M.2 PCIe/NVMe SSD | Compatible PCIe storage socket, supported module size and firmware capabilities. |
| SSD In An External Enclosure | Enclosure protocol, external connection and required power. |
Kingston’s SSD support information illustrates the distinction between a physical M.2 module and its storage interface. Check the specific system specifications rather than extrapolating from a different computer. An M.2 socket intended for wireless hardware is not automatically suitable for an SSD. An incompatible module should not be forced into a connector, regardless of whether its overall length appears correct.
Inspect The Firmware Storage Inventory
Use the computer manufacturer’s documented startup key to enter BIOS or UEFI setup. On some PCs the key is F2 or Delete, but this is not universal. If Windows is still working on another system drive, the UEFI Firmware Settings option in the Windows recovery environment may be available. Always use the method appropriate to that model.
- Enter firmware setup using the supported procedure.
- Locate the system’s storage information rather than relying exclusively on the boot order screen.
- Inspect the appropriate SATA, NVMe or storage-controller section.
- Look for the SSD model, approximate capacity and connection location.
- Record what appears and exit without saving changes if you have not deliberately changed anything.

A drive can be recognized under a controller’s own inventory without appearing as a separate individual boot entry. Examine the available information carefully, especially when a storage controller manages multiple drives. Some systems provide only limited detail in firmware setup. Manufacturer documentation and approved preboot diagnostics can help when the interface does not expose a complete inventory.
For an existing system that previously started normally, record the original settings before altering the storage configuration. A photograph or private written note of the relevant screen can help you restore the original values, but avoid sharing visible device identifiers or security information publicly. Dell’s storage troubleshooting resource gives an example of model-specific firmware inspection and diagnosis.
Check A 2.5-Inch SATA SSD Connection
If a compatible SATA drive is missing from the relevant firmware inventory, examine its connection only when the computer can be safely serviced. Follow the manufacturer service manual for the exact model. Shut down, remove external power and follow the documented procedure for isolating any internal battery when required. Use appropriate electrostatic discharge precautions and do not handle internal equipment while it is energized.
A conventional desktop SATA drive normally needs both an appropriate data connection to the motherboard and power from the approved power supply. A disconnected or loose component in either path can prevent the device from functioning. Laptop implementations may instead use a model-specific cable, interposer or caddy. Examine the arrangement shown in the service manual before deciding that a cable is missing.
On a serviceable desktop, if authorized and safe, check that the existing connectors are seated correctly. Where the motherboard supports it, compare a known-working SATA data cable or a different compatible, enabled SATA port. Change one component at a time. Never substitute a modular power-supply cable purely because its connector fits; use only a cable explicitly compatible with that exact power supply. Incorrect power wiring can permanently damage connected equipment.
Reassemble the computer according to its instructions before restoring power, and check the relevant firmware storage screen again. If the device appears after a cable change, preserve important data and observe its normal operation. A single successful detection is not proof that an intermittently failing drive is reliable.
Check The Installation Of An M.2 SSD
A newly fitted M.2 SSD may not be fully connected, may occupy an incompatible storage socket or may have been installed with an incorrect retaining arrangement. Verify both the part specification and the system’s service instructions before removing it. If a laptop has non-user-serviceable storage or the repair involves complicated battery isolation, arrange qualified service rather than attempting a generic desktop procedure.
For a user-serviceable computer, shut it down fully, disconnect external power and follow its documented internal-power and static-protection precautions. Identify the intended storage socket and mounting hardware. If permitted, remove and reinstall the SSD using the manufacturer’s angle, retention and thermal-management instructions. Ensure the correct standoff or retention mechanism is used for the module length. Never bend the drive, force the connector or overtighten its retaining mechanism.
Some systems have a removable heatsink, thermal pad or tool-free latch. Follow the exact assembly instructions for that design. A heatsink intended for a different module height may interfere with correct installation. Leave manufacturer labels in place unless the instructions specifically direct otherwise. Do not substitute an improvised screw or conductive material near the connector.
Once the system is safely reassembled, check whether the SSD is recognized. If the board supports another compatible storage socket, a controlled comparison may be useful. Check the documentation first because two sockets on the same motherboard can support different interfaces or configurations. Do not move a drive that is part of a managed RAID arrangement without consulting the administrator or appropriate service documentation.
Check Shared Ports And Motherboard Storage Limits
A motherboard may contain more storage connectors than it can operate in every possible combination. Installing an M.2 module can disable a particular SATA port or change how available expansion resources are assigned. The exact rules are specific to the board, processor configuration and storage sockets. If a previously working SATA drive disappeared after installing an M.2 SSD, investigate those documented sharing rules before concluding that the old drive failed.
Read the storage and expansion sections of the official motherboard manual. Locate any table showing which SATA ports are unavailable under specified M.2 arrangements. Also verify whether the intended socket supports your processor configuration. Record the original and proposed changes. On an authorized serviceable desktop, moving a SATA data cable to an available compatible port may resolve a documented shared-port conflict. Follow the appropriate shutdown and service precautions first.
ASUS’s motherboard SSD detection guide includes a concrete example of an M.2 socket and SATA connector sharing resources. The port names used in that example should not be treated as a universal motherboard layout. Your board may share different connections or use a different arrangement entirely. A drive installed in the correct physical location still needs an enabled and compatible signal path.
After a change, confirm that all expected storage devices remain available, not merely the SSD you added. If your storage arrangement includes a boot drive and several data drives, check each identified model. The objective is to resolve the conflict without introducing a second missing drive or changing the intended startup configuration.
Review BIOS Storage Settings Without Changing Them Blindly
Storage configuration can include options involving SATA controller operation, AHCI, RAID or Intel VMD. Their availability and meaning depend on the platform. A system configured with a storage management controller may expose devices in a different manner from a computer using a direct storage interface. Neither mode is inherently wrong merely because a different troubleshooting tutorial shows another configuration.
Compare the existing settings with the manufacturer’s documentation for the actual model and installed storage arrangement. Confirm whether the intended controller or port is enabled. If a documented setting must change, seek model-specific instructions and ensure that important data and encryption credentials are protected first. On a managed computer, have the relevant administrator review the settings.
Changing the mode of a controller used by an existing Windows installation can prevent the operating system from reaching the startup volume. It can also disrupt an existing RAID configuration or prompt BitLocker recovery. Do not disable RAID or VMD, switch controller modes, clear the TPM or disable Secure Boot merely to make the screen resemble someone else’s firmware setup. Do not reset all firmware settings as an early step. A default configuration is not necessarily identical to the computer’s previously working configuration.
If a specific firmware update addresses storage compatibility for your model, use the official update procedure. Check the motherboard revision, update requirements, reliable power and backup preparation. Our What Is Firmware article explains why firmware differs from an operating-system driver. A BIOS update is not a routine substitute for verifying a disconnected cable or incompatible interface.
Distinguish Missing Firmware Detection From A Windows Setup Driver Problem
If the SSD is recognized by the firmware or storage controller but Windows installation media does not show it as an available destination, investigate the installation environment. Certain computers expose storage through a controller for which the particular Windows installer needs a compatible driver. This is not the same as a drive that cannot communicate with the motherboard at all.
Check your exact computer model and operating-system architecture. Obtain the supported storage controller driver from the computer manufacturer’s official support page when its installation instructions require one. Some platforms need an extracted Intel Rapid Storage Technology driver during Windows Setup; others use a native storage path that needs no separate package. Do not assume one particular Intel or AMD driver applies to every NVMe drive.
For systems that require a driver, the manufacturer’s instructions generally explain how to prepare it on installation media or another supported USB drive and use the installer’s driver-loading option. Consult the model-specific reference rather than installing arbitrary controller software. ASUS and Dell provide separate examples in their installation storage troubleshooting guide and storage driver loading reference. Our Windows driver guide describes reliable sources.
Once the installer lists a disk, stop and verify the destination before approving any operation. Detection alone is not permission to delete its partitions. If you intended to recover an existing Windows system, use the appropriate repair route instead of starting a clean installation. Microsoft’s Windows recovery options explain the distinction between recovery and reinstallation.
Check Windows Disk Management If Firmware Can See The Drive
If Windows starts from another drive, you can inspect the available storage independently of File Explorer. Open Disk Management and compare the reported disks, capacities and partitions with the expected SSD. Do not save unrelated changes or assume that the highest-numbered disk is the new one. If prompted to initialize a disk whose history is uncertain, cancel the prompt before investigating further.
A new, verified empty secondary SSD may need a partition structure, volume, file system and drive letter before it appears in File Explorer. Follow Microsoft’s new disk initialization instructions only after positively identifying an empty drive. A disk containing a previous installation or files must not be treated as new just because Windows labels it uninitialized or displays unallocated space. An unexpected label may indicate a problem with existing storage metadata.
For a read-only inventory on an accessible Windows machine, the following commands can list the disks recognized by the operating system. Use an authorized terminal and exit DiskPart after the query:
diskpart
list disk
exitSee the official DiskPart reference for its command syntax. Do not proceed to destructive commands such as clean or format. DiskPart is powerful, and the listing is all that this diagnostic example requires. For additional context, see the Disk Management overview. Neither utility makes an electrically unrecognized SSD visible to the firmware.
Compare The SSD With Known-Compatible Equipment
If the firmware still does not identify the drive, a controlled comparison can narrow the hardware possibilities. Only use safe, trusted equipment with explicitly compatible interfaces and power arrangements. A USB enclosure for an M.2 SATA drive is not necessarily suitable for an NVMe module. Likewise, a successful external connection does not prove that the original internal socket supports the same SSD.
| Comparison Result | Next Investigation |
|---|---|
| SSD works in a known-compatible alternative system | Original socket, controller, documented compatibility or connection. |
| A known-good compatible SSD also fails in the original socket | Host connection path and motherboard support. |
| SSD fails on several verified compatible connections | SSD hardware and manufacturer assessment. |
| Both drives work independently but one disappears when installed together | Shared-port rules or controller configuration. |
Do not expose an unstable data-bearing drive to unnecessary tests. For an ordinary empty test SSD, manufacturer-approved diagnostics may be appropriate once hardware recognition is established. A diagnostic result can provide evidence for service, but it does not guarantee future operation. If hardware diagnostics report a failure, prioritize appropriate repair or replacement and consider recovery needs separately.
Plan Service And Verify A Stable Repair
If detection remains unsuccessful after confirming compatibility and following the approved installation and connection checks, contact the SSD or computer manufacturer with the exact parts involved. Describe the drive model, motherboard or laptop model, affected socket, observed firmware inventory, changes preceding the problem and any diagnostic reference codes. Report whether the SSD is new or contains existing data. Ask how warranty service handles the original drive before approving an exchange.
When detection is restored, confirm that the same model and expected capacity appear in the appropriate firmware and operating-system inventory. For an existing readable drive, secure valuable files promptly. For a confirmed empty secondary drive, prepare it through the appropriate supported procedure. For an existing boot drive, verify ordinary startup after saving work. Keep any previous verified backup until the repaired system and important files have been checked.
Watch for recurrences during normal use. If the drive repeatedly disappears, do not call the problem resolved just because one restart worked. Document the actual pattern and obtain qualified assistance when necessary.
Frequently Asked Questions
Why Is My New SSD Not Showing In BIOS?
Check the exact drive and socket compatibility, supported connection, documented shared-port rules and appropriate storage inventory. A defective drive or host connection can also cause the symptom.
Can An SSD Be Detected But Not Appear In The Boot Menu?
Yes, a recognized drive does not necessarily have a usable boot entry or operating system.
Can I Use An M.2 SATA SSD In Any M.2 Socket?
No, the socket must support the required storage interface as well as the module dimensions and connector.
Should I Format An SSD That Is Missing From BIOS?
No, formatting cannot repair firmware-level detection and can destroy access to existing data.
Should I Switch From RAID Or VMD To AHCI?
No, not as a routine fix. Changes to storage management can prevent an existing installation from starting or disrupt an array. Follow the model-specific supported procedure.
Why Does Windows Setup Not Find A Drive That BIOS Shows?
The installation environment may need a compatible storage controller driver, depending on the computer and operating system.
Does Updating BIOS Always Fix A Missing NVMe SSD?
No, check compatibility and connections first. Use a supported firmware update when evidence identifies a relevant fix.
Official References
Technical review: November 16, 2026. Sources: ASUS SSD Detection, Dell Storage Diagnostics, Kingston SSD Compatibility, Microsoft BitLocker Recovery, ASUS Windows Setup Storage Drivers, Dell Storage Driver Loading, Microsoft New Disk Initialization, Microsoft Disk Management, Windows Recovery Options, DiskPart Command Reference. Illustrations are conceptual rather than actual firmware screenshots. This guide was researched against official documentation; physical storage installation, firmware configuration and Windows command execution were not tested.



