- There are reports of an error with the August update for Windows 11
- Apparently you can make the SSD fail in a small number of cases reported.
- We cannot get to conclusions that this is Microsoft’s fault yet, but this is a worrying sound situation that carries monitoring
Windows 11 may have had problems with your last update possibly breaking some SSD, but at this point, we must be very cautious, since there are only dispersed reports of this problem.
This comes from Wccftech, who noticed a publication of a Japanese Windows 11 (Necoru_cat) in X marking the problem.
To summarize the informed error, they tell us that it is 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 the Microsoft operating system.
Apparently, this “occurs during heavy writing operations”, which means a large installation or patch, with the report that suggests that the error can be activated by 50 GB of continuous writing activity in the unit. Necoru_cat found the problem by applying a great patch for Cyberpunk 2077.
User X points out the finger of suspicion that this is a problem with the unit cache, and apparently has performed a lot of tests, which suggests that SSDs with Phison Nand controllers can be more prone to this error.
As mentioned, if an SSD is affected by this fault, it no longer recognizes it by Windows 11, and the partition of the unit disappears. Oblutingly, we are told that if this happens, there is a “high probability of file corruption”, but again, the season, and this whole report, liberally.
ANALYSIS: Do not be alarmed, yet, but be careful
As I have already indicated, we must be very careful by jumping to the conclusions here. Is this really a problem that can be blamed for the last Windows 11 update? We do not know, and we cannot certainly make a single error report (although apparently it was an integral immersion in the failure).
However, I have been looking for other reports of this problem, and I have presented some bewildered people who have apparently found it. There are several people in this Reddit thread that say they have been affected by this error, including a report by an SSD Adata SP580 that falls into flames.
As for the affected models, according to a list of Nichepcgamer that WCCFTECH pointed out, as well as the 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 – We can add the Adat.
We are saying that there may also be “similar symptoms” with hard drives, but all reports seem to be related to SSD for what I can see.
In any case, although this still seems to be a niche problem, there is enough here for my insect senses to be anthilling, so to speak. And given how unpleasant this technical problem sounds, I think it is worth informing people. In fact, I think it is a right caution, perhaps not to perform large facilities or patches for the moment, if you are running the last Windows 11 update, if you can avoid it, at least until we hear more about what could be happening here, or some official Microsoft word.
Some have raised the theory that, instead of a real defect in the Windows 11 update for August, it is a case of what the update does, in terms of its writing activity to the system unit, which triggers an error in some SSD (Western digital models to be precise). But that does not explain why different types of SSD would be affected (or in fact hard discs, apparently).
We need to hear more from Microsoft about this and, hopefully, the company will be in the case and investigate these reports. I have contacted Microsoft about this error, and I will update this story if I receive news.
