- Microsoft has finished his study of reports of an SSD-Breaking Bug
- The company said the August update for Windows 11 is not blame
- However, there are still reports of drive errors filtering in and some people are not satisfied with Microsoft’s conclusion
Microsoft has investigated reports on the latest Windows 11 update that breaks some SSDs, and we now have the results of this endeavor – and the company found that August Patch for us is not to blame.
Bleeping Computer reports that Microsoft published a service alarm at its Administrator Center (a link that cannot be reached to normal Microsoft accounts, only business accounts) stating the following: “After thorough examination, Microsoft has found no connection between August 2025 Windows Security Update and the types of hard disk errors reported on social media.”
Microsoft added: “As always, we continue to monitor feedback after the release of each Windows update and will examine any future reports.”
Note that Microsoft mentions “hard disk errors” and this is because the problem has also hit hard drives, based on reports – although the majority of events have affected SSDs.
Microsoft has worked with its partners to investigate the problem, including SSD (and hard drive) manufacturers that you would expect, but in collaboration they have shown no evidence of a connection between the latest update to Windows 11 24H2 and the reported drive errors.
In fact, we have already heard directly from Phison, making controllers to SSDs that reports have suggested are more likely to be involved in these failures, refute this view, and state that it could not reproduce the error (across 4,500 hours of testing).
Microsoft also clarifies that its Windows 11 -telemetry – Diagnostic data taken from computers running its us – shows no evidence of an increase in drive errors, either.
Analysis: Coincidence and ‘natural’ drive errors – or something else?
In short: There is nothing to see here, move on. Based on Microsoft’s study – which took a while, so I assume I went into a depth (Phison’s definitely did) – Windows 11 August is not responsible for breaking SSDs or hard drives (nor phison controllers).
The problem is that there are still a few Windows 11 users who post across online forums, such as Reddit, insisting that they’ve got their SSD sunk at this latest update to Windows 11. Then there are others who put out of steering fleets of PCs and not seeing anything with this cumulative update used -not even a hint of a drives of these computers.
So what happens? A theory that is sent is that it could be coincidence – drive errors happen all the time, and then in a given week some Windows 11 PCs will see some breaches in this regard. And because there are reports that the August update is the problem, people assume it is to blame when it is not.
However, you can definitely claim that there are too many reports that this is a pleasant conclusion. Furthermore, if it was a case of incorrect to attach Natural Drive -Fiaskos to the problem, it would also point out that older hardware was affected – as errors are more likely to happen to older SSDs – but there are reports of new (or almost new) drives being affected by this error.
There is another option here that even given Microsoft’s statement that there is nothing obviously wrong with Windows 11, there may still be something about the August update – buried deeply, perhaps – somehow it is to make a hardware error in certain drives that occur more likely. In other words, this would not necessarily be Microsoft’s fault, but it can still be indirectly related to the update.
But with Microsoft and Phison, who are apparently unable to reproduce the error over a whole strain of testing, this seems rather unlikely. Which brings us back to: What happens to these reports still cheating out? There is no clear answer here, but there are clearly some unhappy people posting online about their SSD Fonde.
It is worth going back over the apparent cause of the error that begins, for example, a large file copy – like a game installation. As Bleeping Computer points out, Glitchen seems to be more likely to happen if your drive is over half full (60% or more). When you go for reports, the affected SSD disappears from the system – although in some cases it returns after a simple reboot (in others, it does not, which is obviously a big headache).
Windows 11 Home Users can only postpone the installation of a cumulative update for a short while, so they will eventually get it to their machine if they have tried to avoid it. At that time, it is up to the individual user how safe they feel if they want to perform a hefty file operation such as the installation of a thick game or app. If they are still paranoid and their drive is almost drunk, they might just play it for sure for now.
Microsoft notes that it can “investigate any future reports”, so we may hear even more from the company; But so far, it seems to want to draw a line during the case. And so far, we have to rely on the conclusions of Microsoft and Phison – although there are obviously people out there who remain skeptical and feel that we have still not come to the bottom of this episode.
