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

#151
efikkan
cvaldesAgain you continue to ignore the fact these SSDs were working on Monday the 11th. And last month. And the month before that.
You can't even get basic facts right.
The drives have a defect, they were defective products from the moment they were made, you just didn't know it yet. Defective products should be handled by the manufacturer.
(And big fonts doesn't change the facts either…)
remixedcatIt was fine before the update... again it's not on the drive mfrs or controller mfrs !!!
When the drive locks up and have corrupted its internal state, then the flaw is in the drive itself. It's always the device's responsibility to validate commands. If some sequence of commands (valid or invalid) causes a product to malfunction, then the product is 100% defective. You show a complete lack of technical knowledge of the subject matter.
Posted on Reply
#152
remixedcat
efikkanYou can't even get basic facts right.
The drives have a defect, they were defective products from the moment they were made, you just didn't know it yet. Defective products should be handled by the manufacturer.
(And big fonts doesn't change the facts either…)


When the drive locks up and have corrupted its internal state, then the flaw is in the drive itself. It's always the device's responsibility to validate commands. If some sequence of commands (valid or invalid) causes a product to malfunction, then the product is 100% defective. You show a complete lack of technical knowledge of the subject matter.
SMH. If everything was fine till they dropped this code then it's on MS than it's on them. Case closed.
Posted on Reply
#153
wNotyarD
efikkanThe drives have a defect, they were defective products from the moment they were made, you just didn't know it yet. Defective products should be handled by the manufacturer.

When the drive locks up and have corrupted its internal state, then the flaw is in the drive itself. It's always the device's responsibility to validate commands. If some sequence of commands (valid or invalid) causes a product to malfunction, then the product is 100% defective.
Are you seriously suggesting THE WHOLE SSD industry is in the wrong and Microsoft is somehow innocent in all this clusterfuck?
Posted on Reply
#154
Hecate91
wNotyarDAre you seriously suggesting THE WHOLE SSD industry is in the wrong and Microsoft is somehow innocent in all this clusterfuck?
Not only SSD's, there are reports of HDD's failing or requiring a reformat as well, so it must be the whole storage industry if Microsoft is somehow free of any blame with this update.
Posted on Reply
#155
remixedcat
Hecate91Not only SSD's, there are reports of HDD's failing or requiring a reformat as well, so it must be the whole storage industry if Microsoft is somehow free of any blame with this update.
Yup tons of enterprise and even consumer HDDs from WD blues, reds, greens, and ultrastars, to Toshibas to Seagate ironwolf and exos HDDs regardless of sector size too! Some of those you can't change that so... only the ultrastars and exos and select toshibas can you change from 512 to 4kn sector size.
Posted on Reply
#156
unwind-protect
Can you imagine the outcry if this had happened to Linux first?
Posted on Reply
#157
remixedcat
unwind-protectCan you imagine the outcry if this had happened to Linux first?
Would be worse but at least in Linux land there's more QA and stuff is open sourced...

Think of all the servers that run Linux. Yeah.
Posted on Reply
#158
_roman_
remixedcatWould be worse but at least in Linux land there's more QA and stuff is open sourced...
I disagree. When I changed to the ntfs linux kernel module I had issues. Lots of issues. I talk about the linux kernel, not a distro, not the userspace. Just the kernel.

Feel free to check the command line output. You can ignore the german text there:
www.computerbase.de/forum/threads/erzeugt-der-neue-linux-ntfs-treiber-korrupte-dateien.2145812/

The issue was solved by reverting back to the long term fuse module ntfs-3g

Anyway. I think some people would like when we keep the topic on microsoft windows only.

It's interesting to see that microsoft did nothing so far. I'm very interested in such topics when it is about data safety.
Posted on Reply
#159
unwind-protect
_roman_I disagree. When I changed to the ntfs linux kernel module I had issues. Lots of issues. I talk about the linux kernel, not a distro, not the userspace. Just the kernel.
NTFS is a Windows thing. Nobody should expect it to work in Linux.
Posted on Reply
#160
R-T-B
cvaldesOne everlasting problem with tech dorkwads is many of them are so close to the topic that they are completely detached with reality, what happens in the real world. They can't see the forest for the trees.

99.9% of consumers rely on Windows Update for all of their system updates including device drivers, security patches, etc. Joe Consumer isn't reading BleepingComputer, TheRegister, WindowsLatest, whatever to see how barfy this month's Redmond Dogchow is. They eventually drink whatever Kool-Aid Microshaft pours in their cup.

What if this bug wiped out 10 years of your mom's photo library?

And I bet this bug got past many corporate IT groups as well.

These Phison-based SSDs were working fine on Monday August 11th, weren't they? And then problems started after the only thing that changed was a Patch Tuesday update? And there are people here who say that this is not Microsloth's fault? Releasing an OS change that destroys user data? Like I wrote before, that's software universe's biggest possible sin. Do this enough and you are just begging for a class-action lawsuit.

And yet some of you are saying, "Well, maybe the Phison drives are out of spec, noncompliant, etc." TOO FLIPPING LATE. There are tens of thousands (if not hundreds of thousands of them) on the market or already deployed in regular production systems, which aren't just those run by professional enterprise sysadmins. This also means your auntie's home PC.

For fun go ask your relatives what drive controllers their SSDs are using. Go ahead.

And yet some of you seem to think this is not really that big of a deal. Go apply for a job at Microsoft. You will fit RIGHT IN. It's people like you who are running Windows Release Engineering in 2025. Absolutely appalling.
Hard agree. Keep in mind when I say comments like "the fault lies in firmware" (this is an example as I'm not sure of anything), that is me performing a root cause anaylsis. That does not excuse Microsoft for shipping this update, which due to the situation, whatever it is, should obviously have never shipped.

Both things can be true, people. The fault can lie with the drive controller firmware, and Microsoft still should never have shipped this.
unwind-protectNTFS is a Windows thing. Nobody should expect it to work in Linux.
Why not? The kernel supports it. The key difference is if your vendor for the drive is the linux kernel, don't blame MS for bugs, obviously.
_roman_I disagree. When I changed to the ntfs linux kernel module I had issues. Lots of issues. I talk about the linux kernel, not a distro, not the userspace. Just the kernel.

Feel free to check the command line output. You can ignore the german text there:
www.computerbase.de/forum/threads/erzeugt-der-neue-linux-ntfs-treiber-korrupte-dateien.2145812/

The issue was solved by reverting back to the long term fuse module ntfs-3g

Anyway. I think some people would like when we keep the topic on microsoft windows only.

It's interesting to see that microsoft did nothing so far. I'm very interested in such topics when it is about data safety.
The linux kernel NTFS module was donated by Paradox software and is of iffy quality btw. They are trying to bring it up to speed, but it's been slow. NTFS-3G is far more mature.
SoraEveryone reporting an issue is in a northern hemisphere location where heatwaves are currently occuring.
Also an interesting thing to note, although I will say this trend of accepting every drive that fails right now on social media as being "affected" is stupid and has to stop.
Posted on Reply
#161
A Computer Guy
R-T-BAlso an interesting thing to note, although I will say this trend of accepting every drive that fails right now on social media as being "affected" is stupid and has to stop.
I agree. Also I think somehow with the news in general it's oddly quiet out there. I would have expected more noise around this issue. It's been a week already and Tech Jesus hasn't hopped on this yet. Probably preoccupied with the fallout with is prior video involving Nvidia smuggling. It's possible this issues is just overblown.

There could very well be multiple ramifications at play with the Microsoft Update with storage devices but no matter the case it would probably be a good idea for MS to pull the update if there is any positive correlation at all with certain drive failures even if the reasons for the failure are not 100% certain yet. The idea they haven't yet makes me think 1) They don't think it's their problem, 2) They don't care about users or their data, or 3) They update management is grossly incompetent right now. The very fact Phison had to get involved to go out defend themselves does make me think there is some real issue going on but either nobody knows the root cause just yet or perhaps the root cause needs some kind of secrecy like it might reveal some zero day exploit or perhaps was the result of industrial espionage.
Posted on Reply
#162
xorbe
unwind-protectCan you imagine the outcry if this had happened to Linux first?
It has happened with ext2/3/4 bugs eating data, but they are fixed quickly, because "well it wasn't broken last week", and the source code bisect is fast.
Posted on Reply
#163
Sora
OrodruinSo, regardless of make or model, all drivers are at risk? Am I understanding correctly?
ignore that person, they are deep in the coolaid.
wNotyarDAre you seriously suggesting THE WHOLE SSD industry is in the wrong and Microsoft is somehow innocent in all this clusterfuck?
The affected vendors are known for playing loose, and fast, and cheap with specs, Yes. the entire ssd industry can be and often is wrong.

To deny this is to deny who these vendors are, and what they have tried pulling beneath our noses.
Posted on Reply
#164
Orodruin
What exactly do you recommend I do?
I completely uninstalled the problematic update on my laptop and postponed updates.

No matter what I do on my desktop computer, I can't uninstall KB5063878.
Everything gives me an error code.
My last resort is restoring a backup I made in June with Acronis. But before I do that, I want to ask again: is there another solution I can do?
That is, to uninstall KB5063878 again.
It won't uninstall with a DOS command either. I can't uninstall it from there by booting into safe boot. It always gives an error code.

Besides this, I can't think of anything else. I don't want to reinstall windows from scratch. Reinstalling a ton of programs and customizing them is a very long and tedious process.

@Sora
@remixedcat
@Youseethis
Posted on Reply
#165
AleXXX666
FreedomEclipseJokes on M$. My main PC is still on 23H2.
LMFAO 23H2 gets still same updates. 22H2 is out of support=rock solid by far.:)
Posted on Reply
#166
Sora
AleXXX666LMFAO 23H2 gets still same updates. 22H2 is out of support=rock solid by far.:)
22h2 gets the same updates 23h2 does.
Posted on Reply
#167
DaemonForce
unwind-protectNTFS is a Windows thing. Nobody should expect it to work in Linux.
Well it does and has for a very long time, reaching as far back as the Knoppix 3.x days.
Somebody put support for Microsoft's ridiculous heap in there and many others adopted it.
Just another joyous horror of open source, usually the moment someone needs disk recovery.
Sora22h2 gets the same updates 23h2 does.
And that is mildly terrifying as 22H2 is still Win10 territory, including my Win10ProWS environments.
I already have issues with updates randomly destroying performance, uptime and general system stability.
I don't need Microsoft retroactively reaching back into the ether and causing problems for older builds too.
If this claws back into the Windows Server world, specifically 2016/2019 flavors, there will be a global problem.
Posted on Reply
#168
unwind-protect
R-T-BWhy not? The kernel supports it. The key difference is if your vendor for the drive is the linux kernel, don't blame MS for bugs, obviously.


The linux kernel NTFS module was donated by Paradox software and is of iffy quality btw. They are trying to bring it up to speed, but it's been slow. NTFS-3G is far more mature.
MS can be blamed for NTFS bugs in other OSes because they didn't document it.

What I'm saying is that expecting "windows stuff" to work perfectly is not realistic. I am glad that Wine has caught up to Windows games as much as it has now, but it is still a game of bug-hunting.
xorbeIt has happened with ext2/3/4 bugs eating data, but they are fixed quickly, because "well it wasn't broken last week", and the source code bisect is fast.
IIRC those bugs didn't live long enough in the mainline kernel to make it to common distributions, no?

Heck, even ZFS had to fix a long standing corruption bug that was probably in it since its beginnings at Sun.
Posted on Reply
#169
AleXXX666
Sora22h2 gets the same updates 23h2 does.
endoflife.date/windows

Enterprise, right. I ended up in using Pro editions of both 10 and 11 on all machines I maintain.:) Happy life without constant Minesweeper gameplay (will it break? lol),;):D

Posted on Reply
#170
efikkan
unwind-protectCan you imagine the outcry if this had happened to Linux first?
Well it already has, several times as a matter of fact.
Multiple Samsung SSD models had some firmware issues around a decade ago which lead to wear and corruption, which only happened in Linux, and it was covered but no outcry. And back then Samsung and Intel were known as the "good" consumer SSDs for Linux, as the vast majority of them were misbehaving, especially with the trim command. I don't remember anyone being foolish enough to call for lawsuits against the Linux community for defective hardware…
It's sad to see how far the competence in tech forums have fallen.
R-T-BAlso an interesting thing to note, although I will say this trend of accepting every drive that fails right now on social media as being "affected" is stupid and has to stop.
Storage issues are so common that if everyone looks for a problem (or something to explain whatever strange symptoms they've experienced), we will get a lot of noise data.
Posted on Reply
#171
remixedcat
efikkanWell it already has, several times as a matter of fact.
Multiple Samsung SSD models had some firmware issues around a decade ago which lead to wear and corruption, which only happened in Linux, and it was covered but no outcry. And back then Samsung and Intel were known as the "good" consumer SSDs for Linux, as the vast majority of them were misbehaving, especially with the trim command. I don't remember anyone being foolish enough to call for lawsuits against the Linux community for defective hardware…
It's sad to see how far the competence in tech forums have fallen.


Storage issues are so common that if everyone looks for a problem (or something to explain whatever strange symptoms they've experienced), we will get a lot of noise data.
there yah go blaming everyone and everything else but microsoft....again!

That was a truly isolated firmware incident while this recent windows 11 thing affects all ssds regardless of controller/firmware/etc.
Posted on Reply
#172
Event Horizon
Why simp for Microsoft? Just stop. People are losing data. What is wrong with some people?
Posted on Reply
#173
R-T-B
SoraThe affected vendors are known for playing loose, and fast, and cheap with specs, Yes. the entire ssd industry can be and often is wrong.
And in that scenario, it would still be wrong to release this update, so please don't try to make MS an innocent party here.

Anyways, a really big question I haven't seen answered is if disabling defender makes you immune to issues... because I do disable it on a few of my workstations, so that is certainly a datapoint, considering this update was designed to "address a new ransomware variant."
unwind-protectMS can be blamed for NTFS bugs in other OSes because they didn't document it.
Not really. NTFS is a patent nightmare. It is derived from HPFS which was coded by IBM and they likely would not consent to documentation either. So many other parties were involved at some point too... I think it's safe to say its probably easier to reverse engineer it than navigate the legal hurdles in the modern NTFS's case.
Posted on Reply
#174
remixedcat
R-T-B"address a new ransomware variant."
I guess their AI coder decided to kill everyone's SSDs "for their protection" I guess and actually ransomwared everyone's SSD/HDDs.
Posted on Reply
#175
R-T-B
remixedcatI guess their AI coder decided to kill everyone's SSDs "for their protection" I guess and actually ransomwared everyone's SSD/HDDs.
The question I pose though is if disabling defender can act as a temporary protection against... whatever? At least until the firmware or update is modified in such a way that this ceases.

Note, that has a lot of its own drawbacks that should be obvious, but its something I have to ask.
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