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

#101
trparky
tugrul_LordOfDrinksHow can windows physically damage an ssd?
Easy. If Windows gives the SSD a command that it can't handle it and the firmware chokes, the SSD dies.
Posted on Reply
#102
A Computer Guy
trparkyEasy. If Windows gives the SSD a command that it can't handle it and the firmware chokes, the SSD dies.
That makes sense. Other than anecdotal screenshots I haven't seen any corroborating evidence of HDD's getting killed in the past few days either. I'm eager to see how this works out and if we start seeing a lot of firmware updates rollout because of it. I'm not entirely opposed to moving to Windows 11 but I'm not looking forward to the possible hours or days of cherry picking the Window 11 "fixes" for usability and privacy from the many forum posts.
Posted on Reply
#103
ARF
mb194dcAnother day on the unpaid Microsoft QA team for anyone in the latest consumer update channel...
I thought Microsoft no longer pays humans, but only AI writes the software ?!
AquilinoIt's ok people, they're still beta testing.
It will be ready to release at any moment. Incoming... be ready!! any time!!

Windows 10 22H2 in here. No problems whatsoever.
Wise man, wise man. Me, too, on Windows 10 22H2 and it is indeed the last Windows ever, until there is a miracle and Mиcrosoft starts listening to humans, makes OS for humans, and pays software engineers - humans to write the OS.
Posted on Reply
#104
efikkan
It would be interesting if any of you who experience issues, or better yet want to reproduce the issue, try to dump whatever you can about the internal state of the device. There most certainly are tools that can dump internal state and firmware etc. I find the cases where people have downgraded speeds the most interesting.
Posted on Reply
#105
chrcoluk
I did find some link to ZFS discussions in the Windows discussions on reddit, and there was a common link between the cases, the vast majority of people reporting non responding drives had previously modified the LBA behaviour of the drive.

From my perspective I am keeping the update not installed on my testing VM, and am waiting for Microsoft to either confirm and fix or deny the update is broken.
Posted on Reply
#106
windwhirl
chrcolukthe vast majority of people reporting non responding drives had previously modified the LBA behaviour of the drive.
LBA behavior? What exactly do you mean?
Posted on Reply
#107
A Computer Guy
windwhirlLBA behavior? What exactly do you mean?
I suspect this means changing the drives operation from 512e to 4K sector size for example.

It's an interesting idea. If Microsoft did change some aspect of HMB allocation perhaps they inadvertently triggered a corner case among HMB drives that have had their LBA's changed from their factory defaults. Maybe the controller freaks out and can't handle it because there was some assumption or expectation that the OS would only do something a certain way in how HMB is setup and used. This is all speculation on my part.

I wonder if anyone in this threadattempting to modify their drives was effected by the Windows 11 issue.
Posted on Reply
#108
remixedcat
A Computer GuyI suspect this means changing the drives operation from 512e to 4K sector size for example.

It's an interesting idea. If Microsoft did change some aspect of HMB allocation perhaps they inadvertently triggered a corner case among HMB drives that have had their LBA's changed from their factory defaults. Maybe the controller freaks out and can't handle it because there was some assumption or expectation that the OS would only do something a certain way in how HMB is setup and used. This is all speculation on my part.

I wonder if anyone in this threadattempting to modify their drives was effected by the Windows 11 issue.
this doesn't explain the drives with DRAM cache also having issues too like the 990/980 pros, SN850X, etc that also USE THEIR OWN CONTROLLERS
Posted on Reply
#109
A Computer Guy
remixedcatthis doesn't explain the drives with DRAM cache also having issues too like the 990/980 pros, SN850X, etc
In my eyes there seems to be conflicting reports. But lets say for the sake of argument those drives could have their LBA changed and they were effected then it means somewhere else other than HMB there were repercussions in conjunction with whatever Microsoft changed on their end. Who knows somewhere deep in the NVMe driver I suppose. Which brings up another question. What driver were those drives using at the time? From what I have seen these days NVMe's just seems to use Microsoft Standard NVMe driver.

Unlike the 970 series of NVMe's the 990/980 pros didn't have their own Samsung driver as far as I know. The 970's could would with either the Samsung driver or Microsoft Standard NVMe driver.
Posted on Reply
#110
remixedcat
A Computer GuyIn my eyes there seems to be conflicting reports. But lets say for the sake of argument those drives could have their LBA changed and they were effected then it means somewhere else other than HMB there were repercussions in conjunction with whatever Microsoft changed on their end. Who knows somewhere deep in the NVMe driver I suppose. Which brings up another question. What driver were those drives using at the time? From what I have seen these days NVMe's just seems to use Microsoft Standard NVMe driver.
this is so wierd and complicated. someone call avril.
Posted on Reply
#111
A Computer Guy
remixedcatthis is so wierd and complicated. someone call avril.
Maybe not so complicated. The NVMe driver probably has to some extent made some assumptions about drive capabilities and behaviors based on standards and/or knowledge of their manufacture. Likewise NVMe firmware. If one ends up changing something fundamental from known expectations on one or both sides of that coin without any coordination then wham you've got problems.
Posted on Reply
#112
remixedcat
A Computer GuyMaybe not so complicated. The NVMe driver probably has to some extent made some assumptions about drive capabilities and behaviors based on standards and/or knowledge of their manufacture. Likewise NVMe firmware. If one ends up changing something fundamental from known expectations on one or both sides of that coin without any coordination then wham you've got problems.
so somehow whatever microsoft did messed stuff up.... or just a typical day at redmond
Posted on Reply
#113
A Computer Guy
remixedcatso somehow whatever microsoft did messed stuff up.... or just a typical day at redmond
Who knows. It could be both and at the same time and NVMe manufacturers not fully completing something to spec.
Posted on Reply
#114
remixedcat
for some odd reason, I've seen the least complaints about seagate m.2 nvme drives (PHISON BASED) with this windows 11 update fiasco, unless it's the spinner types (exos and ironwolf) strange.

and this also doesn't explain a buncha other spinners having issues tons of ultrastars and toshiba SPINNING DISKS are also being killed by this. Somone lost 5 toshibas.

Is it the DRAM cache in those also affected... but it also fucks up DRAMLESS drives.
Posted on Reply
#115
A Computer Guy
remixedcatfor some odd reason, I've seen the least complaints about seagate m.2 nvme drives (PHISON BASED) with this windows 11 update fiasco, unless it's the spinner types (exos and ironwolf) strange.

and this also doesn't explain a buncha other spinners having issues tons of ultrastars and toshiba SPINNING DISKS are also being killed by this. Somone lost 5 toshibas.

Is it the DRAM cache in those also affected... but it also fucks up DRAMLESS drives.
Those are enterprise HDD's your referring to right? Are they also 4Kn drives?
Posted on Reply
#116
cvaldes
A Computer GuyWho knows. It could be both and at the same time and NVMe manufacturers not fully completing something to spec.
But these SSDs were working fine on August 11th, yes?

And it's not like SSDs with Phison controllers are some sort of drive unicorn. There's good chance that Microsoft did little testing other than the cursory install and reboot on a couple of employees' systems.

And this particular update also borked OBS (NDI traffic drops) and AutoCAD.

www.windowslatest.com/2025/08/23/microsoft-admits-windows-11-kb5063878-autocad-admin-request-issue-obs-ndi-audio-video-lag/

I know Microsoft HATES software QA in 2025. They have an impressive track record going back years of taking one step forward and two steps back with these Patch Tuesday dumpster fires.

And it's likely that Windows software QA will continue to drop. There's zero indication that Microsoft cares one whit about putting out something they can be proud of at the end of the day.
Posted on Reply
#117
remixedcat
A Computer GuyThose are enterprise HDD's your referring to right? Are they also 4Kn drives?
Yes, and those come in multiple sector sizes.
WD Ultrastar

Seagate Exos
Posted on Reply
#118
A Computer Guy
cvaldesBut these SSDs were working fine on August 11th, yes?

And it's not like SSDs with Phison controllers are some sort of drive unicorn. There's good chance that Microsoft did little testing other than the cursory install and reboot on a couple of employees' systems.
I would agree. Also if somehow users changing LBA's was involved -I would also say 99% of people won't bother changing any factory settings of their devices in the first place so there wouldn't be any priority for Microsoft to test for that anyway. As for native 4Kn devices that is something I would say they should have tested for assuming they made some changes to the storage subsystem or drivers.
cvaldesAnd this particular update also borked OBS (NDI traffic drops) and AutoCAD.
www.windowslatest.com/2025/08/23/microsoft-admits-windows-11-kb5063878-autocad-admin-request-issue-obs-ndi-audio-video-lag/
Didn't know about that but I also read recently they also borked System Reset System Recovery too. Perfect timing for EOL windows 10 installations I guess.
cvaldesI know Microsoft HATES software QA in 2025. They have an impressive track record going back years of taking one step forward and two steps back with these Patch Tuesday dumpster fires.
And it's likely that Windows software QA will continue to drop. There's zero indication that Microsoft cares one whit about putting out something they can be proud of at the end of the day.
I think they eventually want everything in the cloud and everyone on subscriptions. You will own nothing and be happy with PC gaming also being driven into oblivion.
remixedcatYes, and those come in multiple sector sizes.
WD Ultrastar

Seagate Exos
If we expand my speculation then perhaps Microsoft changed something in the area of 4Kn compatibility in the update and that might explain how so many different drives got involved.
Posted on Reply
#119
529th
I wonder if this will effect any of the Intel Optane drives
Posted on Reply
#120
unwind-protect
trparkyEasy. If Windows gives the SSD a command that it can't handle it and the firmware chokes, the SSD dies.
Uh. That's exactly what shouldn't be possible with "normal" commands (not counting commands to write firmware and the like).
Posted on Reply
#121
A Computer Guy
529thI wonder if this will effect any of the Intel Optane drives
Please don't send me into a panic. :fear:
Posted on Reply
#122
Hecate91
A Computer GuyI think they eventually want everything in the cloud and everyone on subscriptions. You will own nothing and be happy with PC gaming also being driven into oblivion.
I could see Microsoft charging a subscription fee for a gaming OS something like Windows on handhelds with an Xbox console like UI. But hopefully Steam OS & Linux will be a viable option for more games before everything goes fully into the cloud.
It's very disappointing to still not see some kind of statement from Microsoft on this, although not surprising as they haven't even pulled the update yet. They clearly don't care about their users enough to even have any sort of damage control about this update breaking drives.
Posted on Reply
#123
A Computer Guy
Hecate91I could see Microsoft charging a subscription fee for a gaming OS something like Windows on handhelds with an Xbox console like UI. But hopefully Steam OS & Linux will be a viable option for more games before everything goes fully into the cloud.
It's very disappointing to still not see some kind of statement from Microsoft on this, although not surprising as they haven't even pulled the update yet. They clearly don't care about their users enough to even have any sort of damage control about this update breaking drives.
They haven't? If that's that case I was curious what happens in a VM with NVMe configured virtual disk.
Posted on Reply
#124
efikkan
cvaldesI know Microsoft HATES software QA in 2025. They have an impressive track record going back years of taking one step forward and two steps back with these Patch Tuesday dumpster fires.

And it's likely that Windows software QA will continue to drop. There's zero indication that Microsoft cares one whit about putting out something they can be proud of at the end of the day.
In later years, MS have made a tradition out of screwing up major updates (feature updates) and even some Patch Tuesdays. And as you are saying, it's a lack of proper QA. And whenever you're building "critical infrastructure"; operating systems, drivers, BIOSes, even some APIs, etc., extensive long-term testing is a necessity to look for adverse effects.

I don't know what their QA routines are, and I don't know whether they are doing "less QA", but it's evident that whatever they are doing isn't working. It is very possible to use a tremendous amount of man power and still do a bad job due to lack of proper routines, training, etc.
Posted on Reply
#125
thesmokingman
Let's go Macrohard lol. Anything but Miroscoft!

The current SSD issue and now them pushing Recall when they said they wouldn't.
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