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
Add your own comment

278 Comments on Microsoft Windows 11 24H2 Update May Cause SSD Failures

#26
remixedcat
trparkyThis issue seems to be limited to SSDs that use Phison controller chips. What gets me is that this issue seems to be bricking the actual firmware of the SSD to the point where you can’t reinitialize the SSD and it even makes it so that the SSD no longer shows up in UEFI.

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.
Nope, some silicon motion ones are effected to, per some reddit posts.

I am kinda worried for my sk hynix drive in my dell inspiron 3525 -_- dunno what controller it uses it's a bc901.
Posted on Reply
#27
trparky
@_roman_ , I was just basing my post on what I’ve seen on Reddit. Most people were reporting only Phison issues, not devices with other controllers like Samsung.

People with Samsung SSDs seem to have no issues.
Posted on Reply
#28
TheEndIsNear
Are they trying to tank windows on purpose. Windows is like the worst it's ever been well there was windows me. But damn once steam comes out with an os that plays games windows is dead to me. I do have a linux machine that works fairly well maybe I'll just use that from now on. My guess is windows updates are done by a.i. now
Posted on Reply
#29
xorbe
Is this the OS trashing the drive logically (NVME just obeying OS writes) giving fs corruption, or is the NVME suffering internal confusion despite logically correct OS writes?
Posted on Reply
#30
R-T-B
xorbeIs this the OS trashing the drive logically (NVME just obeying OS writes) giving fs corruption, or is the NVME suffering internal confusion despite logically correct OS writes?
It sounds honestly like it is hitting dramless drives the hardest.

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.
remixedcatNope, some silicon motion ones are effected to, per some reddit posts.
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...
Posted on Reply
#31
remixedcat
TheEndIsNearAre they trying to tank windows on purpose. Windows is like the worst it's ever been well there was windows me. But damn once steam comes out with an os that plays games windows is dead to me. I do have a linux machine that works fairly well maybe I'll just use that from now on. My guess is windows updates are done by a.i. now
They prolly are all "vibe coding" everything rn. And even more samsung SSDs are effected by this and other windows updates too. I was going to get the 990 pro for my inspiron and I dual boot that and use windows 1/3rd of the time on that laptop and a few windows updates bricked that drive even. hardware/comments/1mtcgkg/report_microsofts_latest_windows_11_24h2_update here's one that also mentions some WD drives omg -_-
R-T-BIt sounds honestly like it is hitting dramless drives the hardest.

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...
that was the last update I think I gotta dig thru my history which is quite huge from SSD and enterpise HDD research I've been doing for me, hubby and sis cuz like everyone wants storage rn lol
Posted on Reply
#32
Macro Device
EsaTNo need to guess
Consequences of being taught British English xD
My "I guess" usually means "it's apparent that..."
Posted on Reply
#33
maxli86
Here we go again, wasn't there a issue with WD SSD when running Windows 11.
Now this issue yet Microsoft want to end Windows 10 in about 1 month time.
Posted on Reply
#34
Niceumemu
Another reason I'll stay on 23H2 as long as possible
Thanks for continuing to justify my lack of faith in you M$
Posted on Reply
#35
Youseethis
The oldest report I found on that, also mentions KB5062660 (preview), so if you are on the latest KB5063878 can you go back? Can you uninstall 2 cumulative updates? Also I think the bug exists on older versions as well, I had a weird data corruption twice on a large virtual drive (1tb actual size) twice last month (July 2025) when I tried to reclaim unused space from vmware. This never happened before, I thought I lost the ssd which contained the vm.

www.nichepcgamer.com/archives/windows11-24h2-issue-with-writing-to-the-ssd-is-this-caused-by-kb5063878-kb5062660.html
Posted on Reply
#36
mechtech
Hopefully win10 doesn't have the same defender update. 4TB nvmes aren't cheap.
Posted on Reply
#37
windwhirl
YouseethisCan you uninstall 2 cumulative updates?
Probably not.
Posted on Reply
#38
Youseethis
mechtechHopefully win10 doesn't have the same defender update. 4TB nvmes aren't cheap.
I don't think the ssds get damaged, you just loose all your data.
Posted on Reply
#39
DeathtoGnomes
Hooray for, not just delaying, but blocking m$ updates. :D

its always "fixed" on the "next" update, yea the need for QA is a thing.
Posted on Reply
#40
R-T-B
YouseethisI don't think the ssds get damaged, you just loose all your data.
If they go completely read-only as described, that's damage.

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.
Posted on Reply
#41
freeagent
I have 3 AMD rigs with WD Black drives as OS, and the laptop is SK-Hynix.. I think.. all updated no problems.

My drives that have no DRAM are not boot drives.. there are 3 and they are all in my rig lol.. 🫣
Posted on Reply
#42
PowerBuilder
The prophecy that Windows 10 would be the last Windows has been fulfilled. Or, perhaps a more appropriate solution would be a stripped-down, fully patched, and fully functional Windows XP relaunch. Why force users to use an operating system (Windows 11) so corrupted by excessive updates? TLC and QLC SSDs without buffers are highly vulnerable to the constant stress of Windows 11.
Posted on Reply
#43
matar
Another reason to stay on windows 10
Posted on Reply
#44
AusWolf
Users should monitor the situation? What about recalling the update until the cause is found? This is unacceptable!
Posted on Reply
#45
trparky
AusWolfUsers should monitor the situation? What about recalling the update until the cause is found? This is unacceptable!
They wouldn't recall the update, there's too many security exploits that the update fixed. They can, however, release what is known in Microsoft parlance as a KIR or Known Issue Rollback. We just have to wait until Microsoft does their research and eventually issues a KIR to roll systems back to use the older, non-buggy code paths.
Posted on Reply
#46
Sora
All of the drives on the chart suffer these exact issues on Linux, they are not unique to the windows update

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.
remixedcathere's one that also mentions some WD drives omg -_-
There are no affected WD drives, there are affected Sandisk drives with WD branding.
Posted on Reply
#47
Youseethis
Phison reported that there is a problem with KB5063878 and KB5062660. They are investigating.
Posted on Reply
#48
STORMComponents
I have a customer with 2x workstations, both using 2x 2TB Crucial P3 drives in RAID. As soon as the update completed they threw up a BSOD, and now blue-screen on boot. After testing the drives, it appears all 4 have had their partition table destroyed. I've managed to reinstate the table via TestDisk and have recovered data, but the machines still refuse to boot, and no amount of repair or correcting the table or BCD has helped.

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.
Posted on Reply
#49
STORMComponents
This is how one of the 2TB P3 drives is testing after the update. It's been removed from the tower and placed into my offline testbench which is on an older copy of Windows 10 so the OS isn't affected by this update, but the drive's performance is now ruined. The drive was new in March.
Posted on Reply
#50
Sora
YouseethisPhison reported that there is a problem with KB5063878 and KB5062660. They are investigating.
Phison has reported no such thing, their only media release has been to say they are investigating.
Posted on Reply
Add your own comment
Nov 19th, 2026 14:49 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts