- There are reports of a bug with the August update for Windows 11
- This can apparently lead to the failure of the SSDs in a small number of cases reported
- We cannot draw conclusions that it is still Microsoft’s fault – but it is a disturbing situation that carries monitoring
Windows 11 may have encountered problems with its last update which can possibly break some SSDs, but at this stage, we must be very cautious, because there are just scattered reports on this problem.
This comes from WCCFTECH, who noticed a message from a Japanese Windows 11 user (Nocoru_Cat) on X signaling the problem.
To summarize the reported bug, we are told that it is caused by KB5063878 (the Windows 11 update for August, which has been released for a week), and that an affected SSD will completely disappear from the Microsoft operating system.
This “occurs during heavy writing operations”, apparently, which means a large installation or a patch, the report suggesting that the bug can be triggered by 50 GB of continuous writing activity on the reader. Necoru_Cat encountered the problem when applying a big patch for Cyberpunk 2077.
The user X points to the suspicion finger on this subject being a problem with the drive cover, and apparently carried out a lot of tests, which suggests that the SSDs with the NAND phison controllers can be more prone to this bug.
As mentioned, if an SSD is affected by this problem, it is no longer recognized by Windows 11 and that the reader’s score disappears. In a disturbing way, we are told that if this happens, there is a “high probability of files of files”, but again, season – and all this report – generously.
Analysis: don’t be alarmed – but be careful
As I have already indicated, we must be very cautious to conclusions here. Is this really a problem that can be attributed to the last update of Windows 11? We do not know it, and we certainly cannot go through a single report on the bug (although it was apparently a complete dive in the problem).
However, I made a few other reports of this problem, and I revealed disconcerted people who apparently encountered him. There are several people in this Reddit wire who say they were affected by this bug, including a report by an SSD Adata SP580 while descending in flames.
As far as affected models go, According to a list from nichepcgame that wccftech tipped out, as well as ssds with the ps5012-e12-control, 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 also be “similar symptoms” with hard drives, we are told, but all reports seem to be linked to the SSD as far as I can see.
In any case, although it still seems to be a niche problem, there is enough here for my senses of insects to spray, so to speak. And given what extent this problem sounds bad, I think it is worth informing them. Indeed, I think it is a wise precaution not to make large installations or corrective for the moment, if you run the last update of Windows 11 – if you can avoid it – at least until we hear more about what could happen here, or an official word from Microsoft.
Some have raised the theory according to which, rather than a real defect in the update of Windows 11 for August, this is a case of what the update does – in terms of its writing activity to the system reader – which triggers a bug in certain SSDs (Western digital models to be precise). But that does not explain why different types of SSD would be assigned (or even hard drives, apparently).
We must know more about Microsoft on this subject, and I hope that the company will be in the case and will investigate these reports. I contacted Microsoft about this bug, and I will update this story if I hear.
