- There are reports of a bug with the August update for Windows 11
- It can seemingly cause SSDs to fail in a small number of reported cases
- We can’t jump to conclusions that this is Microsoft’s fault yet – but this is a worrying-sounding situation that bears monitoring
Update: Microsoft has contacted us about this bug, and a spokesperson said: “We’re aware of these reports and are investigating with our partners.” So, we’ll hopefully hear the results of that investigation sooner rather than later.
Original story follows below…
This comes from Wccftech, which noticed a post from a Japanese Windows 11 user (Necoru_cat) on X flagging the problem.
To summarize the reported bug, we’re told that it’s caused by KB5063878 (the Windows 11 update for August, which has been out for a week), and that an affected SSD will disappear completely from Microsoft’s OS.
This “occurs during heavy write operations,” apparently, meaning a large installation or patch, with the report suggesting that the bug can be triggered by 50GB of continuous write activity on the drive. Necoru_cat encountered the issue when applying a big patch for Cyberpunk 2077.
The X user points the finger of suspicion at this being a problem with the drive cache, and has seemingly carried out a bunch of testing, which suggests that SSDs with Phison NAND controllers may be more prone to this bug.
As mentioned, if an SSD is affected by this glitch, it’s no longer recognized by Windows 11, and the drive partition disappears. Worryingly, we are told that if this happens, there is a “high likelihood of file corruption,” but again, season that – and this whole report – liberally.
Analysis: don’t be alarmed – yet – but do be cautious
As I’ve already indicated, we need to be very careful jumping to conclusions here. Is this really a problem that can be blamed on the latest Windows 11 update? We don’t know that, and we certainly can’t go by a single report of the bug (albeit it was seemingly a comprehensive dive into the glitch).
However, I’ve been doing some searching for other reports of this problem, and I’ve turned up some bewildered folks who’ve seemingly run into it. There are multiple people in this Reddit thread who say they have been affected by this bug, including a report of an Adata SP580 SSD going down in flames.
As far as affected models go, according to a list from NichePCGamer that Wccftech pointed out, as well as SSDs with the Phison PS5012-E12 controller, the following models could be affected: Corsair Force MP600, Kioxia Exceria Plus G4, Fikwot FN955, and the SanDisk Extreme Pro M.2 3D SSD – so we can add the Adata SP580 to that list.
There may be “similar symptoms” with hard drives as well, we’re told, but all reports seem to be SSD-related as far as I can see.
At any rate, while this still appears to be a niche problem, there’s enough here that my bug senses are tingling, as it were. And given how nasty this glitch sounds, I think it’s worth making people aware of it. Indeed, I think it’s a wise precaution to perhaps not perform any big installations or patches for the time being, if you’re running the latest Windows 11 update – if you can avoid it – at least until we hear more about what might be going on here, or some official word from Microsoft.
Some have raised the theory that, rather than an actual flaw in the Windows 11 update for August, it’s a case of what the update does – in terms of its writing activity to the system drive – that triggers a bug in some SSDs (Western Digital models to be precise). But that doesn’t explain why different SSD types would be affected (or indeed hard drives, apparently).
We need to hear more from Microsoft on this, and hopefully, the company will be on the case and investigating these reports. I’ve contacted Microsoft about this bug, and I’ll update this story if I hear back.
