Monday, August 18th 2025
Microsoft Windows 11 24H2 Update May Cause SSD Failures
Microsoft issued an OS security update as part of the August 2025 Patch Tuesday cycle to counter the Lumma stealer and similar malware and exploits. The Windows 11 24H2 cumulative package KB5063878 was included in that rollout. Early deployments returned an installation error, 0x80240069, which Microsoft acknowledged and later addressed. Community testing has since identified a reproducible pattern in which certain SSDs, when running sustained sequential writes of approximately 50 GB, become inaccessible and display unreadable SMART telemetry. Follow-up analysis and vendor feedback to date primarily point to solid-state drives, although conclusions about traditional spinning hard disk drives remain unconfirmed.
A Japanese tester NichePCGamer published a 21-drive matrix and a repeatable procedure: copy a large game folder, write an approximately 62 GB archive composed of many video files to the target SSD, then decompress that archive on the same device. Failures were reported most frequently when controller utilization exceeded 60% during continuous writes. Reported devices include several Phison-based NVMe models and other drives using different controllers. Symptoms reportedly recur after a reboot, which often restores visibility temporarily but does not eliminate the underlying fault, creating a risk of file corruption if the same workload is repeated. Microsoft and SSD vendors are investigating and have not yet published a definitive root-cause report. Until vendors and Microsoft publish formal guidance, users with SSDs should back up important data, avoid long sequential transfers on systems updated to KB5063878, and monitor vendor and Microsoft advisories for SSD-specific firmware, driver, or OS fixes.Update 14:02 UTC: Phison has posted an update, acknowledging the issue.
Update Aug 21st: Phison has reached out to us to let us know that some documents about this issue are fake.
Sources:
via Neowin, Notebookcheck
A Japanese tester NichePCGamer published a 21-drive matrix and a repeatable procedure: copy a large game folder, write an approximately 62 GB archive composed of many video files to the target SSD, then decompress that archive on the same device. Failures were reported most frequently when controller utilization exceeded 60% during continuous writes. Reported devices include several Phison-based NVMe models and other drives using different controllers. Symptoms reportedly recur after a reboot, which often restores visibility temporarily but does not eliminate the underlying fault, creating a risk of file corruption if the same workload is repeated. Microsoft and SSD vendors are investigating and have not yet published a definitive root-cause report. Until vendors and Microsoft publish formal guidance, users with SSDs should back up important data, avoid long sequential transfers on systems updated to KB5063878, and monitor vendor and Microsoft advisories for SSD-specific firmware, driver, or OS fixes.Update 14:02 UTC: Phison has posted an update, acknowledging the issue.
Update Aug 21st: Phison has reached out to us to let us know that some documents about this issue are fake.


278 Comments on Microsoft Windows 11 24H2 Update May Cause SSD Failures
I am kinda worried for my sk hynix drive in my dell inspiron 3525 -_- dunno what controller it uses it's a bc901.
People with Samsung SSDs seem to have no issues.
I suspect it is exposing some kind of deep rooted common vendor firmware flaw in the drive mapping tables, or perhaps just making the drive abusively regenerate them until those hardcoded sectors fail, hard to say.
Either way, MS needs to rehire it's Q&A team pronto. Even if it's a firmware bug outside it's control, you just can't ship shit that trips it willfully like this.I've been unable to find a list, links would be wonderful...
Also, does this effect those of us who have disabled Defender?
Questions abound...
My "I guess" usually means "it's apparent that..."
Now this issue yet Microsoft want to end Windows 10 in about 1 month time.
Thanks for continuing to justify my lack of faith in you M$
www.nichepcgamer.com/archives/windows11-24h2-issue-with-writing-to-the-ssd-is-this-caused-by-kb5063878-kb5062660.html
its always "fixed" on the "next" update, yea the need for QA is a thing.
FWIW, I am having no issues with my systems, but nearly all my systems are either Optane or Crucial P5 Plus NVME's (DRAM backed flash essentially), so probably not a good sample for controllers if it really is hitting dramless the hardest.
My drives that have no DRAM are not boot drives.. there are 3 and they are all in my rig lol.. 🫣
The single source (the twitter user) had a WD Sandisk drive die sporadically (which they are known to do), then tested a bunch of drives, provoking them to bus reset and crash in the ways they are already known to.
Nothing to report here.There are no affected WD drives, there are affected Sandisk drives with WD branding.
Upon further testing, the drives are now not performing as they should do either, with HDTune reporting as low as 12MB/s for sustained periods before eventually getting up to expected speeds.
About to open RMAs on all 4 drives. Luckily they're under warranty, but an absolute disaster to have to replace 4 drives and reinstall Windows on two machines because of a single dodgy update.