You installed a Windows update, rebooted, and now your SSD is gone. It’s not in File Explorer, maybe not even in the boot menu, and your stomach drops thinking the whole drive died overnight. Take a breath. Most of the time a Windows update didn’t kill the drive, it just knocked something loose in the software stack: a driver reset, a changed boot order, a dropped drive letter, or a BIOS setting that reverted. We researched the common causes and the fixes that actually bring the drive back, in the order you should try them.
This guide walks the whole path, from a 30-second sanity check to the point where you’re genuinely looking at a dead drive. If it turns out the SSD is failing and you need a replacement, our roundups of the best 2TB NVMe SSDs for 2026 and the current best SSD deals can point you at a solid successor. And if you’d rather move your data to something portable while you troubleshoot, the best external SSDs guide covers reliable options.
First check the obvious (the 30-second check)
Before you tear into anything, confirm the drive is truly missing and not just hidden. Open Disk Management (right-click Start, then Disk Management) and look for the drive there. Sometimes an update strips the drive letter but the disk itself shows up fine, and you just need to reassign a letter. That’s a 20-second fix, not a dead drive. If the SSD appears in Disk Management with no letter, right-click it, choose Change Drive Letter and Paths, and add one.
If it’s not in Disk Management either, reboot once more and tap into your BIOS/UEFI. See whether the motherboard detects the drive at the hardware level. A drive that shows in BIOS but not Windows is a software problem, which is good news. A drive that’s absent from BIOS too points at hardware or connection. That single distinction tells you which half of this guide you’re in, so check it before anything else.
While you’re in Disk Management, note whether the disk shows as Online or Offline. An update can flag a secondary drive Offline, and it looks exactly like a missing disk in File Explorer even though the drive is perfectly healthy. If you see the drive listed but grayed out and labeled Offline, right-click it and choose Online, then reassign a letter if needed. That one right-click brings back a lot of “vanished” data drives. It’s the fastest possible fix, so rule it out first.
Cause #1: Windows changed the boot order or fast startup cached a bad state
A big Windows feature update sometimes reshuffles the UEFI boot order or leaves Fast Startup holding a stale hardware snapshot. When that happens, the system either boots the wrong device or resumes from a cached state that never re-scans your SSD. It looks like the drive vanished, but it’s really the boot logic pointing the wrong way. This is one of the most common post-update culprits, and it’s harmless to the drive itself.
Fix it in two steps. First, enter BIOS and set the correct SSD as the primary boot device, saving on exit. Second, disable Fast Startup in Windows (Control Panel, Power Options, Choose what the power buttons do, then uncheck Fast Startup) and do a full shutdown, not a restart. A complete power-off forces Windows to re-enumerate every drive from scratch on the next boot. Nine times out of ten, a drive that “disappeared” after an update is back after this. If the drive is showing in BIOS but Windows still won’t mount it, move to the driver fix next.
Cause #2: Storage controller driver got reset or reverted
Windows updates love to touch storage drivers. An update can swap your motherboard’s NVMe or AHCI/RAID controller driver for a generic Microsoft one, or flip the SATA mode in a way the current driver doesn’t expect. When the controller driver and the BIOS storage mode disagree, the SSD is physically connected but Windows can’t talk to it. The drive’s fine. The translation layer broke.
Open Device Manager and expand Storage controllers and Disk drives. Look for anything with a yellow warning triangle. Right-click the storage controller and choose Update driver, or better, grab the current chipset and storage driver straight from your motherboard maker’s site and install it. If your BIOS storage mode was changed (AHCI versus RAID/Intel VMD), match it back to what your Windows install expects, since switching it blind can stop Windows booting. For laptops and prebuilt systems where the storage is baked in, a vendor support-assistant utility often reinstalls the right driver in one click. A prebuilt like the msi Codex Z2 gaming desktop, which ships with a 2TB m.2 NVMe SSD and Windows 11 preinstalled, relies on exactly these vendor drivers to see its drive, so its support tool is the fast path if you’re on that kind of machine.
If Device Manager shows the controller working but the drive still won’t mount, try uninstalling the storage controller entry (check “delete the driver” only if you have the vendor driver ready to reinstall) and rebooting. Windows re-detects the controller on startup and often loads a working driver fresh, which clears a corrupted post-update driver state. You can also roll back a driver from its Properties tab if the trouble started the moment the update installed a newer version. Rolling back to the driver that worked yesterday is sometimes the whole fix, and it takes about a minute.
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.
Cause #3: The M.2 drive worked loose or the drive is genuinely failing
If the SSD is missing from BIOS entirely, software fixes won’t help, and it’s time to look at the hardware. M.2 drives are held by a single tiny screw, and thermal cycling plus the vibration of a heavy update-and-reboot session can let a marginally seated drive lose contact. A SATA SSD can have a half-connected data or power cable doing the same thing. Reseating is free and fixes a surprising number of “dead” drives.
Power down, unplug, and open the case. For an M.2 drive, remove the screw, pull the drive, and reseat it firmly at the correct angle before screwing it back down. For a SATA drive, reconnect both cables at the drive and the board, or swap in a known-good SATA cable. Boot back into BIOS and look again. If the drive now appears, you’re saved. If it’s still absent from BIOS after a proper reseat on a known-good slot, the drive or its controller may genuinely be failing, and that’s when replacement enters the picture.
One extra thing to try before you write the drive off: move an M.2 SSD to a different M.2 slot if your board has a spare. Some boards share bandwidth between an M.2 slot and certain SATA ports or PCIe lanes, and an update that changed a BIOS setting can disable a slot entirely. If the drive shows up in a second slot, the first slot or a lane-sharing conflict was the problem, not the drive. Check your motherboard manual for which slots share lanes, since that detail explains a surprising number of drives that “died” right after an update.
Preventive maintenance
A little habit-building keeps this from ruining your week. Keep a current backup, ideally an image plus your important files on a second drive or cloud, so an update hiccup is an annoyance and not a disaster. Before a major Windows feature update, note your BIOS storage mode and boot order so you can restore them if the update reshuffles things. And update your motherboard chipset and storage drivers from the vendor now and then, since fresh drivers ride out Windows changes better than stale ones.
It also pays to pause feature updates for a week or two after Microsoft releases them, letting early bug reports surface before the update lands on your machine. You can defer updates in Windows settings, and that short delay dodges a lot of the driver and boot-mode churn that causes this exact problem. Keep your SSD firmware current too, since drive makers occasionally ship firmware that improves compatibility with newer Windows builds. Small, boring maintenance beats an afternoon of panicked troubleshooting.
When it’s not fixable: what to replace
If the drive stays invisible in BIOS across multiple slots and cables, it’s likely dead, and no amount of driver fiddling brings back failed flash. At that point you’re replacing the drive. For most people the smart move is a fresh 2TB NVMe SSD and a clean Windows install, then restoring from your backup. Our SSD buying guides above list current picks at sensible prices, and a modern Gen4 drive will be faster than whatever failed anyway.
If the failed drive is the boot drive in a laptop or a prebuilt you can’t easily service, replacing the whole system is sometimes the more practical route, especially if the machine was already aging. A prebuilt like the msi Codex Z2, with a Ryzen 7 8700F, an RTX 5070, 32GB of DDR5, and a working 2TB NVMe SSD, is one example of a ready-to-go replacement if repair isn’t worth it. For a workstation or AI-focused rig at the extreme end, something like the ASUS Ascent GX10 exists too, though at $3,970.99 it’s far beyond what a simple SSD failure warrants for most users. Match the replacement to your actual need, not the priciest option on the shelf.
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.
A few more questions
Can a Windows update actually break my SSD?
Rarely does it damage the hardware. Far more often an update changes a driver, boot setting, or drive letter and only makes the SSD look gone. Start with Disk Management and BIOS to confirm whether the drive is truly absent or just unmounted. A drive that still shows in BIOS is almost always a quick software fix, not a failure.
Will I lose my data if the SSD disappeared after an update?
Usually not. If the drive still appears in BIOS or Disk Management, your data is intact and you just need to fix a driver, letter, or boot setting. Data loss risk climbs only if the drive is physically failing and absent from BIOS entirely. This is exactly why a current backup matters, so a scare stays a scare.
Should I reset BIOS to defaults to fix this?
It can help, but do it carefully. Loading BIOS defaults can restore a boot order an update scrambled, though it may also flip your storage mode (AHCI versus RAID/VMD) and stop Windows booting. Note your current storage mode first, load defaults, then set that mode back to match your Windows install. Change one thing at a time so you know what fixed it.
Why did only my second drive disappear, not my boot drive?
Because your boot drive is the one Windows loads from, so it’s rarely the one an update knocks Offline or strips a letter from. Secondary data drives are far more likely to go Offline, lose their letter, or sit in a lane-sharing slot that a BIOS change disabled. Check Disk Management for an Offline flag first, then reassign the letter. The data is almost always intact.
Write Your Review
No reviews yet. Be the first to share your experience!