SSD Disappeared After Windows 11 24H2 Update
You installed a Windows 11 version 24H2 cumulative update. During or after a large file transfer, your NVMe SSD vanished. It is not in File Explorer, not in Disk Management, and in some cases not in BIOS. A drive showing 0 bytes or an INACCESSIBLE_BOOT_DEVICE blue screen after reboot are variations of the same problem.
Two separate bugs cause this. On Phison-based SSDs, Microsoft's modified NVMe driver timing triggers a dormant firmware bug. On WD SN770 and SN580 2TB models, a Host Memory Buffer overallocation crashes the DRAM-less controller. In both cases, the NAND flash holding your files is intact. The controller firmware lost its mapping tables. We rebuild those tables using PC-3000 SSD and image the drive without writing to user data areas. $200 to $1,200 depending on severity. No data, no fee.
What the 24H2 Update Does to Your SSD
Windows 11 version 24H2 shipped with a modified NVMe storage driver. The change altered the timing and sequencing of NVMe commands the OS sends to the SSD controller during write operations. On most drives, the change is invisible. On drives with certain Phison controller firmware revisions, the modified command timing hits a bug in the controller's state machine.
The bug fires during sustained writes. Copying 50GB or more, installing a large game, running a Windows system image backup, or any operation that pushes the controller past roughly 60% write utilization for an extended period can trigger it. The controller enters a protection mode mid-operation and stops responding to the OS. The flash translation layer (the internal map that tells the controller where each file lives on the NAND chips) is left in a partially written state.
The specific cumulative update most frequently linked to the issue is KB5063878, released August 12, 2025. Microsoft released KB5064081 later that month to fix the NVMe driver trigger. Installing KB5064081 prevents the bug from activating on drives that have not yet been affected, but it cannot repair drives whose firmware already corrupted.
A second, separate mechanism affects WD and SanDisk DRAM-less NVMe drives. Windows 11 24H2 increased Host Memory Buffer (HMB) allocation from 64MB to 200MB. DRAM-less NVMe SSDs use HMB to store their flash translation layer metadata in system RAM. The WD Black SN770 2TB firmware only supports 64MB of HMB. When Windows allocates 200MB, the controller stalls mid-operation and drops offline. The WD Blue SN580 2TB supports 200MB in theory, but its original firmware could not handle the allocation correctly on 2TB models. Both paths end the same way: drive disappears from BIOS or throws INACCESSIBLE_BOOT_DEVICE.
What You Will See
Mild case (drive recovers on reboot)
- ●SSD vanished during a large file copy or game install
- ●SMART data briefly unreadable in monitoring tools
- ●Cold reboot (full power off for 30 seconds, then power on) brings the drive back
- ●Drive works normally until the next sustained write triggers the bug again
Severe case (drive stays gone)
- ●Drive not detected in BIOS after reboot; M.2 slot appears empty
- ●Disk Management shows the drive at 0 bytes or does not list it at all
- ●BSOD with INACCESSIBLE_BOOT_DEVICE if the affected drive was the boot drive
- ●Multiple cold reboots do not bring it back; controller firmware is corrupted
If your drive came back after a cold reboot, install KB5064081 immediately and back up your data before the next sustained write triggers the bug again. If the drive did not come back, stop rebooting and contact us for a free evaluation.
Affected Controllers and Drives
Community stress-testing by @Necoru_cat across 21 SSDs from Samsung, WD, Seagate, Corsair, SK hynix, Crucial, Solidigm, ADATA, HP, XPG, and Hanye found Phison-controller drives heavily represented among those that disappeared under sustained writes after the 24H2 update. Three Phison controller generations are confirmed affected, though drives from other manufacturers also failed in the test.
Phison E16 (Gen4)
PS5016-E16. First-gen PCIe 4.0 controller. A joint investigation by Phison and PCDIY! found that the failures were isolated to drives running pre-production engineering firmware, not retail production firmware. Corsair Force MP600 and Silicon Power US70 specifically identified in community reports.
Phison E18 (Gen4)
PS5018-E18. The most widely deployed Gen4 NVMe controller. Found in the Seagate FireCuda 530, Corsair MP600 Pro, Kingston KC3000, PNY CS3040, Team T-Force Cardea A440, and dozens of other brands. Community reports confirm NVMe drives with E18 controllers disappearing after the update under heavy write loads.
Phison E26 (Gen5)
PS5026-E26. Gen5 NVMe controller already prone to thermal failure. The 24H2 NVMe driver change adds a second failure path. Corsair MP700, Crucial T700, Inland TD510, Sabrent Rocket 5.
WD and SanDisk NVMe Drives: HMB Overallocation
A separate failure path affects Western Digital and SanDisk DRAM-less NVMe SSDs. These drives use Host Memory Buffer (HMB) instead of onboard DRAM for FTL metadata caching. Windows 11 24H2 tripled the HMB allocation from 64MB to 200MB, and the original firmware on specific 2TB models cannot handle the larger buffer. Only 2TB capacities are affected; 1TB and 4TB models of the same drives are not.
WD Black SN770 2TB
SanDisk Polaris MP16+ controller. Firmware supports only 64MB HMB, but 24H2 allocates 200MB. The controller stalls on read/write operations and triggers BSOD or disappears from BIOS. WD released firmware 731130WD to fix the allocation handling. Model numbers: WDBBDL0020BNC, WDS200T3X0E. The proprietary Polaris controller limits third-party tool support, making recovery more involved than Phison-based drives.
WD Blue SN580 / SN5000 2TB
The SN580 2TB (WDS200T3B0E) and SN5000 2TB (WDS200T4B0E) share the same HMB incompatibility. Both are DRAM-less Gen4 NVMe drives. WD released firmware 281050WD for the SN580 and 291020WD for the SN5000. The SanDisk Extreme M.2 2TB (SDSSDX3N-2T00) uses the same SN770-based platform and received firmware 731130WD.
The WD Blue SA510 (SATA, not NVMe) has also been reported as affected through a third mechanism unrelated to either the Phison NVMe driver bug or the HMB issue. If your SSD disappeared after the 24H2 update regardless of brand, send us the model number for a free assessment.
What Not to Do With a Missing SSD
- ✗Do not flash firmware from the manufacturer. A firmware update reinitializes the flash translation layer. That destroys the mapping your files depend on. Even if the manufacturer released a "fix," applying it wipes user data.
- ✗Do not keep rebooting. Each power cycle gives the controller another chance to overwrite corrupted FTL metadata with garbage. One cold reboot to check if the drive recovers on its own is reasonable. Ten reboots is not.
- ✗Do not run data recovery software. If the drive is not visible as a block device, no software can access it. If the drive appears at 0 bytes, recovery software has nothing to scan.
- ✗Do not roll back Windows and assume the drive is fixed. Uninstalling KB5063878 prevents future triggers but does nothing to repair firmware that already corrupted. The damage lives on the SSD's NAND, not in Windows.
- ✗Do not apply WD's firmware update if the drive already disappeared. Western Digital released firmware patches for the SN770, SN580, and SN5000 2TB models. These patches fix the HMB allocation handling on healthy drives. Applying a firmware update to a drive whose FTL is already corrupted reinitializes the translation layer and destroys the mapping your files depend on. Update firmware only on drives that still work. If your data matters, recover first.
PC-3000 SSD Recovery for Update-Bricked Drives
The recovery follows the same general path as any Phison NVMe firmware failure, with one difference: the firmware corruption was caused by an external driver interaction, not by a hardware defect. The controller silicon and NAND are healthy. The only damage is to the firmware modules and FTL stored on the NAND itself. Because the hardware is intact, the FTL rebuild process can work from clean NAND pages rather than fighting physical defects.
Controller Identification and Firmware Dump
We connect the drive to PC-3000 SSD through an M.2 adapter. PC-3000 sends vendor-specific Phison commands that bypass the normal NVMe initialization sequence. Even when the drive is invisible to BIOS, PC-3000 can communicate with the controller at the firmware level. We dump the firmware area from NAND to identify which modules corrupted during the failed write operation.
FTL Journal Rollback
Phison controllers use a journaled flash translation layer. During normal writes, the controller logs FTL changes to a journal before committing them. The 24H2 driver bug caused the controller to shut down mid-commit, leaving a partial transaction in the journal. PC-3000 reads the journal checkpoint data and rolls back the incomplete transaction to the last known-good FTL state. This restores the logical-to-physical mapping without touching user data blocks.
Drive Imaging
With the FTL restored, the drive presents its real capacity and partition structure through PC-3000. We image the full drive to a known-good destination at a reduced NVMe link speed to keep the controller stable. Files are verified against the original directory structure and transferred to your return media.
WD SN770/SN580 Recovery: Different Controller, Same Outcome
WD's proprietary SanDisk Polaris controller does not have a dedicated PC-3000 Active Utility the way Phison controllers do. Recovery on these drives uses PC-3000's NVMe Universal Utility for initial access, followed by lower-level NAND reading techniques when the controller will not cooperate. The FTL corruption from HMB overallocation is structurally similar to a power-loss FTL failure: the mapping tables in system RAM were lost when the controller stalled, and the on-NAND backup copy was left in an inconsistent state. Rebuilding the FTL from NAND page analysis takes longer than a standard Phison journal rollback because of the proprietary controller architecture, which is why WD SN770/SN580 recoveries typically fall in the upper firmware recovery tier ($900 to $1,200).
This Is Not the Windows 11 Encryption Problem
Windows 11 version 24H2 also expanded automatic Device Encryption to more hardware configurations. That is a separate issue. If your SSD is detected but asking for a 48-digit BitLocker recovery key, the drive hardware is fine and the problem is encryption, not firmware. Read the encryption recovery page for that scenario.
The firmware bug covered on this page causes the drive to vanish entirely. No encryption prompt, no BitLocker key request. The drive simply is not there. These are two different failure modes that both got worse with 24H2, but they require different recovery approaches.
Pricing
Windows 11 24H2 SSD firmware recovery: $200 to $1,200. Free evaluation, firm quote before paid work, no data recovered = no charge.
| Service Tier | Price | Description |
|---|---|---|
| Simple CopyLow complexity | $200 | Your drive works, you just need the data moved off it Functional drive; data transfer to new media Rush available: +$100 |
| File System RecoveryLow complexity | From $250 | Your drive isn't showing up, but it's not physically damaged File system corruption. Visible to recovery software but not to OS Starting price; final depends on complexity |
| Circuit Board RepairMedium complexity – PC-3000 required | $600–$900 | Your drive won't power on or has shorted components PCB issues: failed voltage regulators, dead PMICs, shorted capacitors May require a donor drive (additional cost) |
| Firmware RecoveryMedium complexity – PC-3000 required | $900–$1,200 | Your drive is detected but shows the wrong name, wrong size, or no data Firmware corruption: ROM, modules, or system files corrupted Price depends on extent of bad areas in NAND |
| Advanced Board RebuildHigh complexity – precision microsoldering and BGA rework | $1,200–$1,500 | Your drive's circuit board is severely damaged and requires advanced micro-soldering Advanced component repair. Micro-soldering to revive native logic board or utilize specialized vendor protocols 50% deposit required upfront; donor drive cost additional |
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
All tiers: Free evaluation and firm quote before any paid work. No data, no fee on all tiers (advanced board rebuild requires a 50% deposit because donor parts are consumed in the attempt).
Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost. All prices are plus applicable tax.
Most 24H2-related failures fall in the file system recovery tier ($250) or firmware recovery tier ($900 to $1,200), depending on whether the FTL corruption is limited to the journal or extends to the main mapping table. Cases where the controller also suffered electrical damage (rare with this specific bug) reach the advanced board rebuild tier. Call (512) 212-9111 for a free evaluation.
Data Recovery Standards & Verification
Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to make sure your hard drive is handled safely and properly. This approach allows us to serve clients nationwide with consistent technical standards.
Open-drive work is performed in a ULPA-filtered laminar-flow bench, validated to 0.02 µm particle count, verified using TSI P-Trak instrumentation.
Transparent History
Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.
Media Coverage
Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.
Aligned Incentives
Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.
Technical Oversight
Louis Rossmann
Louis Rossmann's well trained staff review our lab protocols to ensure technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.
We believe in proving standards rather than just stating them. We use TSI P-Trak instrumentation to verify that clean-air benchmarks are met before any drive is opened.
See our clean bench validation data and particle test videoFrequently Asked Questions
Why did my SSD disappear after the Windows 11 24H2 update?
Microsoft changed the NVMe driver behavior in Windows 11 version 24H2. The modified command timing triggers a dormant firmware bug in certain Phison-based NVMe controllers. Under sustained write load, the controller enters a protection mode and drops offline. In mild cases, the drive reappears after a cold reboot. In severe cases, the flash translation layer corrupts and the drive stays invisible to both BIOS and the operating system.
Which SSDs are affected by the Windows 11 24H2 bug?
Two groups. Drives using Phison controllers are affected by the NVMe driver timing bug: the E16 (Corsair Force MP600, Silicon Power US70), E18 (Seagate FireCuda 530, Corsair MP600 Pro, Kingston KC3000), and E26 (Corsair MP700, Crucial T700, Inland TD510). Separately, WD and SanDisk DRAM-less NVMe 2TB models are affected by an HMB overallocation bug: WD Black SN770 2TB, WD Blue SN580 2TB, WD Blue SN5000 2TB, and SanDisk Extreme M.2 2TB. The WD Blue SA510 (SATA) was also reported as affected through a third, unrelated mechanism.
Why are only 2TB WD drives affected?
The HMB overallocation bug is specific to the firmware on 2TB capacity models. Windows 11 24H2 increased Host Memory Buffer allocation from 64MB to 200MB. The WD Black SN770 2TB firmware only supports 64MB of HMB; allocating triple that amount causes the controller to stall. The WD Blue SN580 2TB and SN5000 2TB had firmware that could not handle the new allocation on 2TB models specifically. 1TB and 4TB variants of the same drives use different firmware revisions that handle the allocation correctly. Western Digital released updated firmware (SN770: 731130WD, SN580: 281050WD, SN5000: 291020WD) that fixes the HMB handling on drives that have not yet been damaged.
Will rolling back the Windows update fix my SSD?
Rolling back the update prevents the trigger from firing again, but it does not repair a drive whose firmware already corrupted. If your SSD disappeared during a write operation and does not come back after a cold reboot (power off for 30 seconds, then power on), the flash translation layer is damaged. Rolling back Windows at that point changes nothing on the drive itself. The controller firmware needs to be repaired with PC-3000 SSD.
My SSD shows 0 bytes in Disk Management. Is the data gone?
A drive reporting 0 bytes or wrong capacity after this update is showing a firmware panic state, not actual data loss. The NAND flash cells still hold your files. The controller lost its flash translation layer mapping, so it reports no usable capacity. PC-3000 SSD bypasses the corrupted firmware and rebuilds the FTL to restore the correct capacity and file system.
How much does recovery cost for an SSD bricked by a Windows update?
If the drive still partially responds (detected in BIOS but shows wrong capacity), recovery falls in the file system or firmware tier: $250 to $1,200. If the controller is completely unresponsive and requires board-level intervention, the price reaches $1,200 to $1,500. Free evaluation, firm quote before paid work, no charge if we cannot recover the data.
Did Microsoft fix this bug?
Microsoft released KB5064081 in late August 2025 to address the NVMe driver trigger. Installing that update prevents the bug from firing on drives that have not yet been affected. It does not repair drives already damaged by the earlier KB5063878 update. If your SSD was already bricked before the fix, the firmware damage on the drive itself still needs professional repair.
Sources
- 1.Microsoft Support KB5063878, "August 12, 2025 cumulative update for Windows 11 version 24H2," and KB5064081, "August 2025 NVMe driver fix for Windows 11 version 24H2." Microsoft Learn documentation.
- 2.@Necoru_cat community stress test across 21 SSDs from 10+ manufacturers. Documented SSD disappearance under sustained writes following the Windows 11 24H2 NVMe driver change. Phison-controller drives overrepresented in failure group.
- 3.Phison / PCDIY! joint investigation report on E16 controller failures. Findings: failures isolated to drives running pre-production engineering firmware, not retail production firmware.
- 4.Western Digital / SanDisk support article: "Internal SSD Critical Firmware Update Available for Solving BSOD on Windows 11 24H2 Update." Lists affected 2TB models: WD_BLACK SN770 (731130WD), WD Blue SN580 (281050WD), WD Blue SN5000 (291020WD), SanDisk Extreme M.2 (731130WD). Published on SanDisk support portal.
- 5.Microsoft Q&A threads and community reports documenting HMB allocation change from 64MB (Windows 11 23H2) to 200MB (24H2) as root cause for WD SN770/SN580 BSODs. Registry workaround to limit HMB to 64MB confirmed effective prior to firmware patch.
- 6.Community reports from r/Windows11 and r/datarecovery documenting WD Blue SA510 (SATA) failures following the same 24H2 update, indicating the issue extends beyond NVMe Phison controllers.
Related Recovery Services
Full SSD recovery service overview
Thermal failure recovery for Gen5 NVMe
BitLocker/TPM lockout after motherboard failure
Firmware panic and capacity reporting errors
FTL encryption blocks consumer software tools
Firmware-level drive access hardware
SSD vanished after a Windows update?
Free evaluation. Firm quote. No data, no fee. Ship from anywhere in the U.S.