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

#251
Hecate91
I don't see what a guy did nearly 20 years ago, and hasn't worked for MS in 30 years, has to do with Microsoft as a company. I think it's sad people are trying to discredit him because he does have a lot of good info.
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.
Posted on Reply
#252
remixedcat
Hecate91I don't see what a guy did nearly 20 years ago, and hasn't worked for MS in 30 years, has to do with Microsoft as a company. I think it's sad people are trying to discredit him because he does have a lot of good info.
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.
He is biased towards microsoft... he will make excuses for them at every point that's why I question him and he's a scammer and made his millions from scamming people so he , in a sense, cheated to get money and influence. That's why I can't trust any of his info.
Posted on Reply
#253
trparky
Slack space? I believe you’re referring to what’s called cluster sizes.
Posted on Reply
#254
xorbe
So what became of this? Was there any root cause? Actual Windows software issue sending bad commands? Or Windows triggering some lurking SSD hw issues?
Posted on Reply
#255
chrcoluk
xorbeSo what became of this? Was there any root cause? Actual Windows software issue sending bad commands? Or Windows triggering some lurking SSD hw issues?
Nothing, looks like Microsoft are in a "no comment" mode.

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.
Posted on Reply
#256
RJARRRPCGP
A Computer Guy*(7B2QJXD7) To address the intermittent non-recognition and blue screen issue. (Release: September 2025)
Just confirmed receiving the update.
SoraThey could always be formatted with third party UI's (using the same format api) and command line tools to FAT32.
Windows 98 allows more than 32 GB for FAT32. So those restrictions in NT5 and later, were added, to push NTFS. So people won't put FAT32 on their OS partition, which appears to be the main reason, back in the NT5 days. This means NT5 and later. At least since Windows XP, if not for also Windows 2000.

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.
chrcolukThe slack space is largely moot these days, especially on modern file systems. First that the average file size has shot up, but also that the smaller the cluster size, the larger the metadata overhead.

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.
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.
jnv11JayzTwoCents released a new video showing that a BIOS update killed the bug that caused his SSD to fail. His SSD is now working. He thinks that an AGESA bug might be the root cause:

9:06=Was JayzTwoCents trying to mimic the Windows 3.1x ding sound?
Posted on Reply
#257
chrcoluk
I think directstorage doesnt require 4k, in my VM I tested the command and it reports directstorage as enabled on a partition with 16k clusters.

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.
Posted on Reply
#258
RJARRRPCGP
chrcolukI think directstorage doesnt require 4k, in my VM I tested the command and it reports directstorage as enabled on a partition with 16k clusters.

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.
A person reported Microsoft Store not letting you install with >4KiB clusters. (or some game installers) That made me suspect Microsoft put that limitation in DirectStorage as well.
Posted on Reply
#259
trparky
Why would anyone want to run a system with cluster sizes bigger than 4 KB? With a whole lot of small files, you could stand to lose a lot of disk space.
Posted on Reply
#260
RJARRRPCGP
trparkyWhy would anyone want to run a system with cluster sizes bigger than 4 KB? With a whole lot of small files, you could stand to lose a lot of disk space.
I would have thought the same thing, too, as that's the de-facto for small random accesses. But, there are use cases where a drive can be used for mostly large files.
Posted on Reply
#261
chrcoluk
RJARRRPCGPA person reported Microsoft Store not letting you install with >4KiB clusters. (or some game installers) That made me suspect Microsoft put that limitation in DirectStorage as well.
That sounds really odd, but you can still use 4k on C: to make sure that has no compatibility issues for apps, and just change on other partitions.
trparkyWhy would anyone want to run a system with cluster sizes bigger than 4 KB? With a whole lot of small files, you could stand to lose a lot of disk space.
Files that small are rare these days (in large numbers), and metadata overhead is larger with smaller cluster sizes. On my SA510 it tripled read performance.
Posted on Reply
#262
RJARRRPCGP
chrcolukThat sounds really odd
I agree with you there, as the 4KiB limit is from the pre-XP days.
Posted on Reply
#263
pf100
trparkySlack space? I believe you’re referring to what’s called cluster sizes.
Slack space is the amount of space wasted because of inefficient cluster sizes in relation to file sizes.
trparkyWhy would anyone want to run a system with cluster sizes bigger than 4 KB? With a whole lot of small files, you could stand to lose a lot of disk space.
Exactly. But if you know only large files will be on the partition, like with a camera, then >4k sectors is okay because not much space will be wasted.
RJARRRPCGPI would have thought the same thing, too, as that's the de-facto for small random accesses. But, there are use cases where a drive can be used for mostly large files.
And when you have mostly large files, like with a camera, slack space doesn't matter as much. That's when it's okay to have a 128gb fat32 partition.

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.
Posted on Reply
#264
RJARRRPCGP
Slack space=When a file is smaller than a cluster.
Posted on Reply
#265
chrcoluk
pf100Slack space is the amount of space wasted because of inefficient cluster sizes in relation to file sizes.


Exactly. But if you know only large files will be on the partition, like with a camera, then >4k sectors is okay because not much space will be wasted.


And when you have mostly large files, like with a camera, slack space doesn't matter as much. That's when it's okay to have a 128gb fat32 partition.

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.
It was important in that era, and am glad you mention your experience is from those days when it mattered.

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.
Posted on Reply
#266
RJARRRPCGP
pf100I'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.
Before Windows 95 OSR2, (late-1996, IIRC) (which a bunch weren't even allowed to install, LOL) it was FAT16, which has 2 GB partition size limit. And that likely wasn't even 2 GiB!
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)
Posted on Reply
#267
chrcoluk
Something of interest, this cache folder has a bunch of small cache files ranging from about 15kB up to 1000s of kB.

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.
Posted on Reply
#268
Sora
chrcolukSomething of interest, this cache folder has a bunch of small cache files ranging from about 15kB up to 1000s of kB.

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.
if size on disk is lower than size some form of compression is active or its using ntfs sparse files. (manual Compact with xpress 4k perhaps?)
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.
Posted on Reply
#269
chrcoluk
Soraif size on disk is lower than size some form of compression is active or its using ntfs sparse files. (manual Compact with xpress 4k perhaps?)
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.
As I said no compression so no compact, maybe sparse detection is done natively, dont know.
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.
Posted on Reply
#270
Sora
chrcolukFile properties are part of metadata that is stored.
File properties does not include the size of the ntfs objects for that file
chrcolukThis page confirms 4k is required for compression. It also correctly reports fragmentation problems can be a problem on 4k clustered drives, and that there is a fragment limit in NTFS.
The checkboxes will grey out for compression and encryption in this case, rather than hiding the advanced panel button.
It's still used to toggle the indexing and content toggles after all, which are not restricted by the clusters size.
Posted on Reply
#271
xorbe
Checks Win11 version. Whew, luckily I have 25H2 and not 24H2! /s
Posted on Reply
#272
chr0nos
Im on "latest" update and the drive where the game is installed just went offline, Forza Horizon 5 was "optimizing for my pc" had to do a power cycle, as a restart didnt bring it back.

NVME Predator SSD GM7000 4TB

Edit: using latest drivers/bios/etc

should i be afraid of windows killing off the drive bug?
Posted on Reply
#273
remixedcat
chr0nosIm on "latest" update and the drive where the game is installed just went offline, Forza Horizon 5 was "optimizing for my pc" had to do a power cycle, as a restart didnt bring it back.

NVME Predator SSD GM7000 4TB

Edit: using latest drivers/bios/etc

should i be afraid of windows killing off the drive bug?
so it's still killing drives now... ugh. and that's not a cheap nvme either that's around 300 bucks!
Posted on Reply
#274
chr0nos
remixedcatso it's still killing drives now... ugh. and that's not a cheap nvme either that's around 300 bucks!
Its not dead, but it did dissapear and had to do a full power down for it to show up again. Smart Data says no errors 100% health
Posted on Reply
#275
remixedcat
chr0nosIts not dead, but it did dissapear and had to do a full power down for it to show up again. Smart Data says no errors 100% health
i'd do a little more tests on it and I would let the manufacturer know as well, so they can keep track. please do so.
Posted on Reply
Add your own comment
Nov 19th, 2026 14:59 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts