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 heard that this solved the problem, so I posted this, but looking at it now, it seems that it still hasn't been solved. I'm sorry.
However, it seems that you're also having trouble reproducing the problem, so I don't think you need to worry about it.
In this test, there were no problems in a clean install environment, regardless of whether KB5063878 was installed or not.
chimolog.co/ssd-vs-kb5063878/
For the SSD problem the fact that the system was stable before doesn't mean that he didn't had some particular component failing just when he made that update, for example some cap could had went bad on that SSD and while the SSD works fine in most cases in some particular rare cases when that cap should actually do its job he just has the failure or he always had a lose connector there and in time it degrated to the the point that the SSD is no longer getting the proper voltage and well while initially it worked in time components degrated to the point it's no longer stable with that lower voltage, also the mb might be faulty to begin with and push lower voltage into that ssd...
(Heck i had a pc that worked fine for 4 years in a row without anything being touched inside it or the pc being moved and one day it just started to no longer boot anything and it turned out to be 1 dimm not staying properly in the slot so the argument that it worked fine before the update and not after so it must the the update is just silly.)
Again I don't say it's not the update, I just say that saying that it's 100% the update while there can be other reasons it's just bad.
He even admits of using a beta Bios on a motherboard made by a manufacturer that well it's know for having mb that in some cases are malfunctioning with the cpu (to say it nicely here and not to say destroying the cpu). And in this case he might just see a prefailure behaviour of the cpu...
The are so many variables that he is not taking into consideration or he just dismissed them without real arguments that makes him no better in reasoning than some flat earth believers that refuse to understand that with their models u should be able to see some high peaks but u don't.
And the behaviour he is experiencing later when he is actually putting the SSD back into the test machine (where ports and connectors will wear faster than in a normal pc) is more of a bad SSD or bad connection in the port than a Windows update failure.
Also he is just... when asking if someone on Intel is experiencing it. He is so poor that he can't afford to build a cheap Intel system and test it himself?!?
I'm not attacking him at all, just poiting to how badly he is failing in this video. He say in this video about the journalist not doing the homework properly but in this video he also didn't do his homework properly...
He obvious doesn't have experience with what is inside the bios for a mb or gpu, else he would had knew how buggy some of them can be, while the mb or gpu actually works with that buggy bios...
Wonder if he is expanding that theory regarding bios updates "if it's not broken why fix it" to other things like android updates, software updates because well it works so why would u need update. He should be consistent and well disable windows updates for the same reason as he is not updating the bios because well same as a bios update an os update can cause him not get consistent testing results, he should do the same with all the software running on the machine used for testing actually he should fully disable any security software because that might be updated and make him get inconsistent results. I'm not serious here, just using his own words to prove that he is not consistent with the reasoning.
L.E.: if he was so sure that it is windows causing the problem and he is so poor that he can't afford to build a cheap intel system just to test the SSD there then well why he didn't tried to test this sdd in Linux?!? I would had loved to see a dmesg log after the SSD vanished, just a reset (not a power off / power on) and boot from a live usb stick and a dmesg log. In term of actually trying to debug the problem he has done nothing: no attempt to boot in another OS after the SSD vanished, no attempt to run the SSD in another machine to try to replicate it. After the bios update all he knows is that now he can't trigger it and he is assuming it's the agesa update when it can be some voltages/power adjustment done in the new bios that fixed it (something that asrock might had actually done in the attempt to prevent the malfunctioning with particular cpus).
Also i fail to understand why he didn't updated that bios to the latest stable. It makes no sense to just upgrade it to next version and just stop there.
Maybe this video will help explain why 32GB was the biggest FAT32 partition size you wanted on Windows *at the time*, and why a 128GB FAT32 partitrion was fine with your camera. Remember that small files wastes half of the space on your 128GB CF card but large files (video) won't.
128GB USB drives are also wrong formatted in windows 11 pro with ntfs.
My workaround is mkfs.???? /??? (i translate the binary to make filesystem =mkfs) for e.g. 16GB / 4GB fat32 usb sticks or 128GB NTFS sticks.
Microsoft should fix the format dialog background software stack or fix the stuff shown in the format dialog. They are both broken. EXFAT is not FAT32 - it can not be read my my devices.
~2 Weeks or less, w11 pro refurbisher license, all updates done: Two partitions are not a single NTFS partition in the size of 128GB for my USB transfer stick.
Stuff formated with e.g. www.man7.org/linux/man-pages/man8/mkfs.vfat.8.html or the other filesystem familes are all readable in w10 pro, w11 pro or any other device so far. Definitely a windows 10 pro and 11 pro issue with the bad build in format dialog.
Seems wikipedia but no other valid source for max file system limits: en.wikipedia.org/wiki/File_Allocation_Table#Types
Edit: I will use my ignore list and not engange. The issue was explained for someone who knows the core basics of computers. Which are still the same since windows 3.11 afaik / linux kernel 2.0.0.
Crucial
Seagate
Sandisk/WD
And I trust ssd manufacturers way more than I would ever trust microsoft.
Who in their right mind would release a product with beta firmware and risk their whole brand for what?? No decent company would.
I wish ppl would stop standing up for one of the most vile companies in existence
There is a few niche cases where it may matter such as maildir email storage, or something like a git which has a ton of tiny sized files. But for your typical end user it's moot.
Even more so on larger drives, as using small clusters the overhead starts to become extreme affecting performance. A 4tb 4k ntfs has nearly a billion records to manage.
My odd performing SA510 throughput tripled (and i/o delay) moving from 4k to 16k clusters, the overhead on 4k was really harming that drive. It went from 560/150 reads (pSLC/native) to 560/450. A few testers have started to suggest 32k as optimal for SSD's and 64k to a couple of megabytes for spindles.To be fair one company did use experimental features as they wanted an edge in the market, and in the end it destroyed their rep and brand, remember the old OCZ SSDs?
I assume this is the right box for windows 11 pro.
geizhals.at/microsoft-windows-11-pro-64bit-deutsch-pc-fqc-10534-a2611704.html
Edit: Windows 10 home oem / pro did format usb sticks correctly with ntfs several years ago. Formatting bigger usb sticks with fat is broken for a very long time.
Since it seems nobody has any answers for the problem I'm inclined to believe the scenario for the problem is a very corner case scenario or it's just way overblown and people are learning consumer based flash just isn't as reliable as everyone thinks it is. ( I haven't kept up with current events in the past weeks so I might be missing something. )I've installed this update and so far so good but I'm also running Windows 10 so I wasn't having the issue anyway.
semiconductor.samsung.com/consumer-storage/support/tools/
*(7B2QJXD7) To address the intermittent non-recognition and blue screen issue. (Release: September 2025)
adding this too from my screenshot archives (ssd_data phison rep deleted their reddit account sadly)
phison would be pissed if any partners did this with their controllers
www.atg.wa.gov/news/news-releases/attorney-general-s-office-sues-settles-washington-based-softwareonlinecomYou keep saying broken, but you're wrong.
The Format GUI intentionally limits itself to ntfs and exFAT because of the expectations of what high capacity removable drives are to be used for.
They could always be formatted with third party UI's (using the same format api) and command line tools to FAT32.