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
Windows 11 pro annoys me to update every 5 weeks or less.
My update package was downloaded according to the file stamp at 6th of august. Luckily it seems the update file orgins to 22th of july 2025.
As always two weeks later, far too late we see issues.
I really wish microsoft would allow to pause updates for 20 weeks and not only 5 weeks.
-- The worst are data loss. Happens quite "sometimes" with Microsoft Windows.
What does "HOURS" mean under connection?
I have a WD SN740 OEM, not listed, no clue what kind of controller it has but it looks like Sandisk.
Guess it'll only become worse for M$ overtime. They paced up from two steps forward, one and a half steps back (2005) to one step forward, seventeen steps back (2025). Feels like we're gonna run out of two-digit ratio numbers by 2030.
timesofindia.indiatimes.com/technology/tech-news/microsoft-ceo-satya-nadella-to-employees-its-no-longer-enough-to-be-software-factory-must-become/articleshow/123230971.cms
I say we should start replacing all these CEOs with AI.
At least AIs wouldn't demand excessive salaries for screwing things up...
Thank god I only use this pos only as a thin client!Stochastic parrots.
The Do Kwons and Elizabeth Holmes are outliers that probably won't even make it to the training dataset.
Have fun dealing with the Koticks, the Musks, and the Atlmans...
With that being said, my theory is that Windows is sending an NVMe command to the device that the firmware is choking on. If true, we have a much bigger problem on our hands.
techpowerup says it is not only Phision Controller based.
I saw here some sort of spreadsheet which was missing in the german language mediaI can not pause w11 pro updates longer as 5 weeks. And those 5 weeks just starts when i decide to. So even with waiting i am hit with bad updates when I am unlucky.
I downloaded the update file on the bad update day of 6th of august. Luckily the update file seems when I understood correctly, the file does not says it from 22nd of july 2025.
--
It is not Windows bashing.
Show me a single 2 or 3 months news window without a news of broken Windows 11. Pcgameshardware.de has those news kinda regularly.
It is a fact, windows 11 is broken. A fact it is kinda often broken. An update causes issues this is a fact and not bashing.
Yeah, no thanks then.
It will be ready to release at any moment. Incoming... be ready!! any time!!
Windows 10 22H2 in here. No problems whatsoever.