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 trust SSD manufacturers more than Microsoft, but it's weird neither SSD manufacturers nor Microsoft have come up with any solution to this issue.
J2C claimed after his video Microsoft contacted him, and were acting in a way his video was the first they heard about it, but he hasnt mentioned anything since on follow ups etc.
I had a 78 GiB partition with Windows 98 SE in 2002. (Maxtor 4D080H4) ( 80 GB, 5K RPM)
I admit, NTFS is superior, being a journalling file system. You don't want FAT32 except for on UEFI partitions and small external drives where file changes don't occur as often in a short time span.But, did Microsoft make it so that we are banned from using >4 KiB clusters for DirectStorage?
The 4 KiB limit, reminds me of Windows 2000, where the defrag API refuses to defrag if there is a cluster size greater than 4 KiB. Windows XP removed that limit, IIRC.9:06=Was JayzTwoCents trying to mimic the Windows 3.1x ding sound?
According to this link BypassIO with NTFS it wont work with either encryption or compression enabled, but it doesnt say anything about cluster sizes, so with my test and that link, I believe it doesnt matter.
I've honestly been baffled that seemingly everyone has no idea what I'm talking about when I mention slack space and how it relates to disk and file sizes. I used to repair corrupted partition tables on fat32 drives in the 1980's and 90's and I had to know this stuff and the question I'm asking myself is why is everyone talking to me like I don't know what I'm saying? I think I know why: it's because we haven't had to deal with these problems or concern ourselves with slack space in the last 20 years or so, therefore no one knows what the hell I'm saying.
Metadata overhead isnt just related to performance, metadata also consumes storage space, It can actually exceed the "slack" you mention.
I understand what you saying, its just not important in 2025 except for niche cases. The benefits of larger cluster sizes comfortably outweigh it.
Because Microsoft at that time, preferred that we get a brand new PC, LOL. PCs got obsolete even faster in the late-1990s! Especially if you had less than a Pentium CPU/586!
On a 486, Duke Nukem 3D was a slide show, even at 320x200! 3 year old PCs were often considered obsolete! LOL! Same with the early-first-decade-of-the-new-century! (especially 2000-2002)
The window on the right is a 16k cluster drive, the one on the left is 4k.
There seems to be savings on metadata that have easily overcame the slack overhead. Although not quite sure how it has ended up as a negative amount, there is no compression of the files. Aside from the savings from the lower amount of NTFS records, there looks to be a simplified metadata setup, notice the properties box on the right is lacking an advanced options button. That button hosts options for encryption and compression, as well as indexing, presumably all not available on the other drive. Both are NTFS.
ntfs metadata does not reflect in file properties, you need to use other level tools to view the object properties.
The advanced button is missing because your relocated user folder has an incorrect access control list setup, and you don't properly own the folder.
File properties are part of metadata that is stored.
I just checked a bunch of random folders on partitions using larger clusters, not a single one has an advanced button, I then created a partition with 16k clusters and made a folder, no advanced button, I then created a 4k cluster partition and made a folder, advanced button is there.
So either you are right and an extraordinary run of events has happened that just by coincidence all of my folders on larger clusters have incorrect ACL, or yeah its a thing with larger cluster partitions.
I did some checks on the ownership, there is a few folders with a long numerical ID set as owner instead of account name, however it seems to be unrelated, as all the folders with correct owner, and ones I manually create which also have correct owner exhibit the same behaviour.
This page confirms 4k (or lower) is required for legacy compression. It also correctly reports fragmentation problems can be a problem on 4k clustered drives, and that there is a fragment limit in NTFS.
techcommunity.microsoft.com/blog/filecab/cluster-size-recommendations-for-refs-and-ntfs/425960
I also found documentation albeit from 3rd party sites that sparse detection does work on uncompressed files, but was unable to find anything about cluster size limitations for ntfs efs encryption.
So you could be right on the reason for the missing advanced button, but if you are the question is, am I hitting some bug that whatever folder is generated has this ACL error you speak off. The folder I presented a reallocated folder (although not the entire user folder, just discord, and the folder itself was native), however all other folders I checked and verified on are not part of any relocation, not junctions or symlinks.
It's still used to toggle the indexing and content toggles after all, which are not restricted by the clusters size.
NVME Predator SSD GM7000 4TB
Edit: using latest drivers/bios/etc
should i be afraid of windows killing off the drive bug?