You plugged in a shiny new drive, booted up, opened File Explorer, and nothing. No new letter, no extra capacity, just the same drives you already had. An SSD not showing in Windows is one of the most common storage headaches out there, and the good news is that most of the time it’s a software hiccup rather than a dead drive. A brand-new SSD often ships raw, with no partition and no drive letter, so Windows sees it at a low level but won’t display it in Explorer until you tell it to. That gap between “the hardware is present” and “I can see it in File Explorer” trips up beginners and veterans alike.
This guide walks through the usual suspects in the order a seasoned builder would check them, from a 30-second glance to the rare case where the drive is genuinely gone. Work top to bottom and you’ll almost always find the fix before you reach the end. If you’re shopping while you troubleshoot, our roundups of the best 2TB NVMe SSD picks for 2026 and current SSD deals are worth a look, and for a rescue drive that mounts instantly, an external SSD can save you an afternoon. Let’s find your missing drive.
First check the obvious (the 30-second check)
Before you assume the worst, do the quick pass. Reboot once. Windows sometimes fails to enumerate a drive on the first cold boot, and a clean restart clears it more often than you’d expect. While the machine is off, reseat the drive: for a 2.5-inch SATA SSD that means pushing both the SATA data cable and the power cable in firmly at both ends, and for an M.2 stick it means loosening the retention screw, reseating the module at a slight angle, and tightening it back down. A half-seated M.2 is the single most common reason a new drive vanishes, and it’s easy to under-insert one when the standoff sits a hair too high.
Next, open Disk Management. Right-click the Start button, pick Disk Management, and look at the list of disks along the bottom of the window. If your SSD appears there as “Unknown,” “Not Initialized,” or a black bar labeled “Unallocated,” congratulations, the drive is alive and the hardware is fine. It just needs a few clicks. If it doesn’t appear in Disk Management at all, jump ahead to the BIOS and cable causes below, because the problem sits lower in the stack. That one look splits your troubleshooting cleanly in two and tells you which half of this article you actually need.
Cause #1: The drive is uninitialized or unallocated
This is the number one culprit for a new SSD. Fresh drives leave the factory without a partition table, so Windows can read the disk but has nowhere to hang a drive letter. In Disk Management the drive shows up as a separate disk with a solid black bar and the word “Unallocated,” or it prompts you to initialize it the moment you open the window. Nothing is broken. You just haven’t formatted it yet, and that’s a two-minute job.
Here’s the fix. If Windows asks you to initialize, choose GPT (GUID Partition Table) for any drive over 2TB or any modern build, and MBR only for genuinely old legacy systems that need it. Then right-click the unallocated black bar, pick New Simple Volume, click through the wizard, assign a drive letter, and format it as NTFS with the default allocation unit size. Give it a label you’ll recognize later. Thirty seconds after the wizard finishes, the drive pops up in File Explorer with its full capacity showing. One important caution: initializing and formatting wipes the disk completely, so only do this on a genuinely new or empty drive, never on one that still holds data you want back.
Cause #2: Missing drive letter or a stale storage driver
Sometimes the SSD is fully partitioned and formatted, yet it still won’t show in Explorer because Windows never handed it a drive letter. This happens a lot with drives moved from another PC, drives that shared a letter with a removed USB device, or after a messy clone. In Disk Management the volume looks perfectly healthy, with a blue bar and an NTFS partition, but there’s no letter beside its name. The data’s all there. It’s just invisible to Explorer.
To sort it, right-click the healthy volume, choose Change Drive Letter and Paths, click Add, and pick any free letter. It’ll appear in Explorer immediately, no reboot required. If the volume instead shows as “RAW” rather than NTFS, the file system is corrupt and you’ll need recovery software before you format, so don’t rush to reformat a RAW drive that holds real files you care about.
Separately, a stale controller driver can hide a drive entirely. Open Device Manager, expand Disk drives and Storage controllers, and look for any yellow warning icon or a device flagged with an error code. Right-click and update the driver, or better, grab the current NVMe or chipset driver straight from your motherboard maker’s support page rather than trusting Windows to find it. We’ve researched plenty of owner reports where a single chipset driver update brought a “dead” NVMe drive back on the very next reboot. If Windows Update recently changed a storage driver and the drive vanished right after, rolling that driver back is worth a shot too.
Cause #3: BIOS detection, cabling, or the M.2 slot itself
If the SSD never reaches Disk Management, the problem sits at the firmware or physical layer. Reboot and enter BIOS or UEFI (usually Delete or F2 at startup) and hunt for the storage or NVMe configuration page. If the drive isn’t listed there either, Windows has zero chance of seeing it, so this is where you focus. For SATA drives, swap the data cable for a known-good one and try a different SATA port on the board, since dead cables and dead ports are far more common than dead drives. Verify the SATA power lead from the PSU is fully seated too.
For M.2 NVMe sticks, motherboard lane sharing trips up a huge number of builders. On many boards, populating a second M.2 slot or certain SATA ports disables lanes elsewhere, so your drive goes dark for a reason buried deep in the manual. Read your board’s M.2 and SATA sharing table carefully, then move the drive to the primary M.2 slot closest to the CPU. Confirm the slot supports your drive type too, because an NVMe stick won’t work in a SATA-only M.2 key, and a SATA M.2 stick won’t run in an NVMe-only slot. If the drive shows up in one slot but not another, you’ve found your answer, and it isn’t the SSD.
Preventive maintenance
A few habits keep drives from disappearing later. Update your motherboard BIOS and chipset drivers once or twice a year, since newer firmware improves NVMe compatibility, especially for Gen4 and Gen5 drives on older boards that shipped before those drives existed. Keep an M.2 heatsink installed on high-speed drives so thermal throttling doesn’t cause dropouts under sustained load. When you add or clone a drive, initialize it as GPT and use NTFS from the start to sidestep the RAW and letter-assignment snags above. And label your volumes clearly, so a missing letter is obvious at a single glance instead of a mystery.
When it’s not fixable: what to replace
Occasionally the drive really is done. If the SSD never shows in BIOS across multiple slots and cables, clicks or gets very hot with no activity, or has already thrown SMART warnings, it’s time to stop fighting it. A single failed drive doesn’t have to mean a full rebuild, but if the machine is old and the storage was the last straw, replacing the whole system can be cleaner than nursing a dying board. For a straightforward drop-in that skips the drama, a fresh NVMe stick from our boot-drive picks gets you back up in minutes.
If you’d rather start clean, a prebuilt with storage already configured skips the whole initialization dance entirely. The MSI Codex Z2 gaming desktop pairs an AMD R7-8700F and GeForce RTX 5070 with a 2TB M.2 NVMe SSD and 32GB DDR5, running about $2,067.34 at a 4.1 rating, and it ships with Windows 11 already seeing every drive. That’s the real appeal of a configured box: no lane-sharing puzzles, no format wizard, no guessing which slot is wired to the chipset.
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
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.
At the extreme high end, if your storage headaches come from an AI or heavy-compute workstation rather than a gaming rig, the ASUS Ascent GX10 is a different animal entirely. It’s a compact AI supercomputer built on the NVIDIA GB10 Superchip with 128GB LPDDR5x and a 1TB PCIe Gen4 NVMe SSD, Wi-Fi 7, and a stackable chassis, priced around $3,970.99 at a 4.2 rating. Overkill for a missing game library, sure. But for agentic AI work where drive reliability can’t be a variable, a purpose-built system removes the guesswork. Most readers won’t need it. It’s here for the few who do.
Pros
- GB10 Superchip targets 1 petaFLOP AI throughput suitable for on-device LM prototyping
- 128GB unified memory pool avoids CPU-GPU copy overhead common on discrete GPU rigs
- NVLink-C2C fabric gives higher effective bandwidth than PCIe Gen5 x16 for AI workloads
- ConnectX-7 enables two-node stacking, scaling to roughly 400B parameter model fine-tuning
Cons
- Limited independent owner fedback and third-party benchmarks available at time of writing
- 1TB NVMe fills quickly with modern checkpoints, external NVMe or NAS staging likely need
- Closed NVIDIA ARM-based stack, not a general-purpose x86 workstation for gaming or standard DC aps
The ASUS Ascent GX10 is a flagship developer-class AI appliance built on the NVIDIA DGX Spark reference design, pairing the GB10 Grace Blackwell Superchip with128GB LPDDR5x and a 1TB PCIe Gen4 NVMe SSD. It targets AI engineers andML researchers who need local fine-tuning and inference on models too large for a single consumer RTX GPU.
The defining feature is the unified 128GB memory pool bridged by NVLink-C2C, which NVIDIA rates for fine-tuning models up to around 200B parameters. Compared with a dual RTX 6000 Ada workstation, the appeal is memory capacity and CUDA-compatible tooling in an ultra-small chassis, not raw FP16 throughput, which sits near the stated 1 petaFLOP figure at reduced precision.
Trade-offs are typical of this tier and platform. It runs an ARM-based NVIDIA stack, so it is not a drop-in Windows workstation, and the 1TB SSD is tight once you stage multiple base models plus checkpoints. Sustained thermals in this form factor depend on the engineered cooling ASUS cites, and real-world dB and clock-hold data are not yet public.
Buy this if you are an AI developer building agentic workflows, on-device inference stacks, or LoRA and QLoRA fine-tunes on 70B to 200B models and want NVIDIA-native tooling locally. Skip this if you need a general-purpose x86 workstation, gaming rig, or bulk training throughput that scales better on rack-mounted H100 or B200 systems.
Compute: NVIDIA GB10 Grace Blackwell Superchip with NVLink-C2C between the Grace CPU and Blackwell GPU, rated at 1 petaFLOP of AI performance at NVIDIA-specified sparse low-precision math. Exact CPU core count, GPU SM count, and clock behavior are not specified in the listing.
Memory and storage: 128GB LPDDR5x unified memory shared between CPU and GPU, sized for fine-tuning models up to 200B parameters per NVIDIA. Storage is a single 1TB PCIe Gen4 NVMe SSD. Additional M.2 slots, DRAM channel count, and TBW endurance are not specified.
Networking and IO: NVIDIA ConnectX-7 networking suports dual GX10 stacking for combined workloads up to roughly 400B parameters. Wireless is WiFi 7 and Bluetooth 5.4. Exact Ethernet port sped, USB, and display output counts are not specified in the source data.
Chassis and software: Stackable ultra-small form factor with engineered cooling for sustained AI loads. Ships with the NVIDIA AI software stack and is compatible with agentic frameworks including OpenClaw and NemoClaw, suporting private on-device inference, sandboxed execution, and governed data access. PSU wattage, dimensions, and weight are not specified.
Tools and parts needed
You won’t need much for any of this. A Phillips screwdriver for the M.2 retention screw and case panels, one known-good SATA data cable for 2.5-inch drives, and maybe an M.2 heatsink if yours shipped bare. Everything else is software you already have: Disk Management, Device Manager, and your motherboard’s BIOS. Keep a spare SATA cable in your parts bin, because ruling out a bad cable in ten seconds beats an hour of blind guessing every time.
A few more questions
Why does my new SSD show in BIOS but not in Windows?
That’s the classic uninitialized-drive situation. BIOS sees the raw hardware, but Windows won’t display a drive without a partition and a letter. Open Disk Management, initialize the disk as GPT, create a New Simple Volume, and format it NTFS. It’ll appear in File Explorer right away. Just remember this wipes the drive, so only do it on a new or empty SSD you don’t need to recover anything from.
Can I recover files from a drive that suddenly stopped showing?
Often, yes, as long as the drive still appears in Disk Management, even as RAW. Don’t reformat it. Run reputable recovery software first to pull your files off, then format afterward once they’re safe. If the drive doesn’t appear in BIOS at all, physical failure is the likely reason, and professional recovery becomes your only realistic option at that point.
Does the M.2 slot I choose really matter?
It genuinely does. Many boards share PCIe lanes between M.2 slots and SATA ports, so filling one slot can disable another without warning. Check your motherboard manual’s M.2 sharing table and use the primary slot near the CPU for your main NVMe drive. Confirm the slot matches your drive’s type too, since a SATA M.2 stick won’t run in an NVMe-only slot, and the mismatch looks exactly like a dead drive.
Write Your Review
No reviews yet. Be the first to share your experience!