You install a drive, boot the machine, and it’s just not there. No new letter in File Explorer, nothing in the boot menu, maybe a blank spot where your SSD should sit. It’s one of the more frustrating storage problems because the drive usually isn’t dead. Nine times out of ten it’s a loose cable, a sleeping BIOS setting, or an uninitialized volume that Windows hasn’t been told to show yet. We researched the common failure points and owner reports, and this guide walks through them in the order that fixes the most people fastest. If you’re shopping while you troubleshoot, our roundups of the best 2TB NVMe SSDs for 2026 and the best external SSDs are worth a look.

Before you assume the worst, know this. A drive that spins up but doesn’t appear is almost always a connection or configuration issue, not a hardware death. Let’s rule those out first.

First check the obvious (the 30-second check)

Start with the cheapest fixes. If it’s a SATA SSD, reseat both the data cable and the power cable at the drive and at the motherboard or PSU. If it’s an M.2 NVMe stick, power down, unscrew the standoff, pull the drive, and reseat it firmly at a slight angle before laying it flat. Loose contact is the single most common cause, and it costs nothing to rule out. While you’re in there, glance at whether the drive gets warm after a few minutes of power. Warmth means it’s receiving current, which is a good sign.

Next, open Disk Management in Windows by right-clicking the Start button. If the drive shows up there as unallocated or offline, congratulations, the hardware is fine and you just need to initialize or bring it online. That single window answers half of all SSD-not-detected questions. If the drive appears here but not in File Explorer, skip ahead to Cause #2.

One more quick pass before you dig deeper. If you just moved the drive from another PC or a laptop, plug it back into that original machine to confirm it still reads. That tells you whether the drive traveled fine and the fault is in the new system. It’s a 30-second sanity check that saves you from tearing apart the wrong computer.

Cause #1: Loose or dead cable and connection

For SATA drives, cables fail more often than the drives they connect. A data cable can look seated while one contact isn’t quite making it, and cheap cables sometimes crack internally. Swap the SATA data cable for a known-good one and move it to a different SATA port on the motherboard. Ports fail too, and rotating to a fresh one rules out a dead header. Do the same with the power lead from the PSU, since a single bad strand on a daisy-chained cable can starve one drive while others run fine.

M.2 drives don’t use cables, but they have their own gotcha. Many motherboards share bandwidth between an M.2 slot and certain SATA ports, so populating one disables the other. Check your motherboard manual for that shared-lane note. If your NVMe drive vanished the moment you added a second SATA disk, that’s your culprit. Move the drive to the primary M.2 slot, which is almost always wired straight to the CPU and never shared. A quick swap here fixes a surprising number of cases.

While the drive is out, inspect the gold contacts and the slot itself. Bent or oxidized M.2 pins are rare but real, and a fingerprint smudged across the edge connector can be enough to break contact. Wipe the contacts gently with a lint-free cloth and a little isopropyl alcohol, let it dry, then reseat. On the SATA side, verify the drive is getting power at all by feeling for faint warmth or listening for the very slight click some drives make on spin-up. No power reaching the drive is a different problem than a data cable that’s simply loose, and telling them apart saves you from swapping the wrong part.

Cause #2: Drive not initialized or has no letter

A brand-new SSD ships raw, with no partition and no volume Windows can mount. It’s there electrically, but the OS won’t show it until you tell it to. In Disk Management, a new drive appears as a black bar labeled Unallocated, often with a prompt to initialize it. Choose GPT for any modern system, right-click the unallocated space, pick New Simple Volume, and let the wizard format it. That’s the whole fix, and it’s the most common reason a working drive stays invisible.

The related case is a drive that already has data but lost its letter. If Disk Management shows a healthy partition with no letter beside it, right-click the partition, choose Change Drive Letter and Paths, and assign one. Don’t reformat a drive that shows an existing volume, or you’ll wipe it. Assigning a letter is instant and non-destructive. If the partition reads as RAW instead of NTFS, that points to file-system corruption, which we’ll cover next.

A RAW volume is worth a closer look before you give up on the data. Windows sometimes marks a partition RAW when the file-system header gets scrambled by an unsafe shutdown, even though the actual files sit untouched underneath. Run chkdsk from an elevated command prompt against the drive letter, and in many cases the volume mounts normally again. If chkdsk refuses because there’s no recognizable file system, a dedicated recovery utility can often still pull your files off before you reformat. Copy anything important elsewhere first, then format. Data comes back rarely once you’ve written over it.

Cause #3: BIOS settings, outdated firmware, or NVMe not enabled

If the drive doesn’t appear in Disk Management at all, the problem sits below Windows, in firmware. Reboot into BIOS or UEFI and look at the storage or boot device list. If the SSD isn’t listed there either, the board itself isn’t seeing it. Confirm the SATA mode is set to AHCI rather than an old IDE or a RAID mode that hides individual drives, since switching to RAID can make a single AHCI drive disappear. For NVMe, make sure the M.2 slot is enabled and not disabled or set to SATA-only in the storage configuration.

Firmware is the other lever. A stale motherboard BIOS sometimes lacks support for a newer drive controller, and a drive’s own firmware can carry a bug that a manufacturer update resolves. Update the motherboard BIOS to the latest stable release, and check the SSD maker’s toolbox utility for a firmware patch once the drive is visible on another machine. We’ve seen brand-new PCIe Gen5 drives refuse to post on older boards until a BIOS bump added support. If a firmware refresh brings the drive back, you’ll want a reliable daily driver, and our picks for the best 2TB NVMe boot drives are a solid starting point.

Preventive maintenance

Most detection problems trace back to install-day shortcuts, so slow down during the build. Seat M.2 drives fully and torque the standoff screw snug, not loose and not crushing. Keep a spare known-good SATA cable in your parts box. And check your motherboard manual for shared M.2 and SATA lanes before you plan your storage layout, because knowing that map upfront saves an hour of confusion later.

Firmware upkeep matters too. Update your motherboard BIOS once when you build and again if you add a newer drive, then leave it alone. Run the SSD vendor’s health utility every few months to catch a failing drive before it drops off entirely. A drive that’s throwing warnings today is the one that goes dark next month.

Heat is the quiet killer people overlook. NVMe drives throttle and, in extreme cases, drop off the bus when they cook, especially fast Gen4 and Gen5 sticks crammed under a hot GPU. Use the M.2 heatsink your motherboard shipped with, or add a cheap aftermarket one, and make sure there’s some airflow reaching the slot. Good thermals won’t fix a loose connection, but they’ll stop a healthy drive from disappearing under sustained load.

When it’s not fixable: what to replace

If the drive shows up on a second computer but never on yours, and you’ve cleared cables, ports, BIOS, and firmware, the fault is likely the motherboard slot or controller rather than the SSD. When the drive won’t appear on any machine, refuses to initialize, or throws read failures the moment it mounts, it’s reached the end of its life. Back up anything recoverable immediately and plan a replacement. A drive that intermittently vanishes under load is telling you the same thing, just more slowly.

Sometimes the cheaper path is a fresh system rather than chasing a dying board. If your machine is old enough that the storage controller is the weak link, a modern prebuilt sidesteps the whole problem with current firmware and a known-good drive already installed. The MSI Codex Z2 Gaming Desktop, priced around $2,067.34 with a 4.1 rating, ships with a Ryzen 7 8700F, a GeForce RTX 5070, 32GB of DDR5, and a 2TB M.2 NVMe SSD running Windows 11 Home. It’s a full-system reset for anyone tired of coaxing an aging board into recognizing drives, and the included NVMe means storage works out of the box.

1
Best Seller

MSI Codex Z2 Gaming Desktop

In Stock
9.9 /10
PCBolt Score
PCBolt Score is calculated based on product ratings, reviews, and sales performance to help you make informed purchasing decisions. Learn more ›
A prebuilt tower pairing the AMD Ryzen 7 8700F with an RTX 5070 and 32GB DDR5, the MSI Codex Z2 has the raw specs for 1440p and entry 4K gaming but carries very limited owner feedback at this stage. Best for buyers comfortable purchasing a newer listing and willing to verify current reviews before committing.
Pros & Cons

Pros

  • RTX 5070 Blackwell GPU is well above average for this prebuilt price tier
  • 32GB DDR5 at 6000 MHz avoids the need for a near-term RAM upgrade
  • 2TB NVMe SSD is a practical capacity for a modern game library
  • WiFi 6 and Bluetooth built in with no added cost

Cons

  • No verified owner reviews at time of writing, making real-world reliability hard to assess
  • Ryzen 7 8700F uses Socket AM4, limiting CPU upgrade path compared to AM5 platform alternatives
  • RTX 5070 ships with 12GB GDDR6, which may become a ceiling in demanding 4K scenarios by 2027
Detailed Review

The MSI Codex Z2 is a mid-to-high-end gaming tower aimed at buyers who want RTX 5070-class performance without building from scratch. Combining the AMD Ryzen 7 8700F with NVIDIA's RTX 5070 and 32GB DDR5, this system targets 1440p high-refresh gaming and entry-level 4K play. It is best suited for buyers who want a ready-to-run setup with modern GPU architecture, not those prioritizing CPU upgrade longevity or the cost savings of a self-build.

The RTX 5070 is the headline component here. Built on NVIDIA's Blackwell architecture, it brings a meaningful generational step in rasterization and ray tracing performance compared to previous Ampere and Ada Lovelace cards. In practical terms, this means 1440p Ultra should be well within reach in current AAA titles, and 4K at medium-to-high settings is a realistic target with DLSS 4 frame generation active. Paired with the 8-core Ryzen 7 8700F boosting to 5.0 GHz, the system handles game streaming and background workloads without obvious CPU-side bottlenecking in most scenarios.

MSI has put some effort into the thermal design. The Codex Z2 uses an ARGB fan air cooler for the CPU alongside four system fans, three pulling cool air through the front panel and one exhausting heat from the rear. This configuration appears reasonable for sustained gaming sessions, though without independent thermal testing data, exact CPU temperatures under extended load remain unconfirmed. The compact tower footprint at 16 x 8.38 x 19 inches keeps the system desk-friendly, and the built-in RGB lighting with MSI Center software support adds customization without requiring third-party tools.

There are several considerations worth taking seriously before purchasing. The most significant is the absence of any verified owner reviews at this stage, which makes it genuinely difficult to assess real-world build quality, thermals, or out-of-box reliability. Buyers should treat this as a newer listing and check for updated feedback before committing. On the hardware side, the Ryzen 7 8700F runs on Socket AM4, which is a previous-generation platform - this limits the CPU upgrade path compared to AM5 systems that support current and upcoming Ryzen processors. Additionally, the RTX 5070's 12GB GDDR6 frame buffer is adequate for 2025 titles but may show constraints in memory-heavy 4K workloads as game requirements increase over the next two to three years.

Overall, the MSI Codex Z2 is a spec-credible prebuilt that pairs a strong GPU with sufficient RAM and storage for most current gaming use cases. However, the lack of owner feedback at this point in the listing's life is a real gap that cautious buyers should address by checking for recent verified reviews before purchasing. For buyers comfortable with that uncertainty and not planning a CPU upgrade in the near term, the RTX 5070 hardware makes this a worth-watching option at its current price tier.

Tools and parts needed

You don’t need much. A Phillips screwdriver for the M.2 standoff and case screws, a spare SATA data cable to swap in, and access to a second computer or a USB-to-M.2 enclosure so you can confirm whether the drive works elsewhere. That external enclosure is the most useful item on the list, since it isolates the drive from your motherboard in about a minute. If the SSD reads fine in an enclosure, you’ve proven the drive is healthy and the fault lives in your PC.

A few more questions

Why does my SSD show in BIOS but not in Windows?

That pattern almost always means the drive is healthy but hasn’t been initialized or given a drive letter. Open Disk Management, and if the drive appears as unallocated, create a new simple volume. If it shows a partition with no letter, assign one. Both fixes are quick and, aside from formatting a raw drive, non-destructive.

Can a new NVMe SSD disable my SATA ports?

Yes, on many boards. Manufacturers share PCIe lanes between certain M.2 slots and SATA ports, so filling one can switch off the other. Check your motherboard manual for the shared-lane diagram, and move your NVMe drive to the primary slot wired directly to the CPU if you hit this.

How do I know if the drive is truly dead?

Put it in a USB enclosure or connect it to a second computer. If it doesn’t appear there either, won’t initialize, or throws read errors as soon as it mounts, the drive itself has failed. If it works fine on the other machine, your original motherboard slot, cable, or BIOS setting is the real problem.