Microsoft Says Recent Windows Update Didn't Kill Your SSD (bleepingcomputer.com) 28
Microsoft has found no link between the August 2025 KB5063878 security update and customer reports of failure and data corruption issues affecting solid-state drives (SSDs) and hard disk drives (HDDs). From a report: Redmond first told BleepingComputer last week that it is aware of users reporting SSD failures after installing this month's Windows 11 24H2 security update. In a subsequent service alert seen by BleepingComputer, Redmond said that it was unable to reproduce the issue on up-to-date systems and began collecting user reports with additional details from those affected.
"After thorough investigation, Microsoft has found no connection between the August 2025 Windows security update and the types of hard drive failures reported on social media," Microsoft said in an update to the service alert this week. "As always, we continue to monitor feedback after the release of every Windows update, and will investigate any future reports."
"After thorough investigation, Microsoft has found no connection between the August 2025 Windows security update and the types of hard drive failures reported on social media," Microsoft said in an update to the service alert this week. "As always, we continue to monitor feedback after the release of every Windows update, and will investigate any future reports."
Nothing to see here, just move along? (Score:5, Informative)
Re: (Score:1, Offtopic)
Hopefully. Whenever you amplify the rancor indiscriminately you dilute its power. Be angry about things worthy of anger, and preserve the integrity of it.
Reserving judgment is a dying practice, which makes me sad. Rushing to it, on the other hand, is the giddy happy place for fools. And the retraction is always far less noisy than the accusation.
Re: (Score:2)
Well, sure. But how often has M$ hidden or delayed reporting their guilt until it no longer mattered. When your track record for destroying working installs with an OS update makes you the obvious culprit, you've got to expect some conclusion "hopping." I won't call it a leap or even a jump. I'll wait on further reports, but my money is on MS being st fault.
Re: (Score:2)
Re: (Score:2)
Re: Nothing to see here, just move along? (Score:2)
Name a time Microsoft has not been terrible.
Re: Nothing to see here, just move along? (Score:4, Funny)
1974
Re: (Score:2)
I wouldn't be surprised if the issue is caused by something like the Windows Search service that runs in the background indexing whatever you have.
Re: (Score:2)
Nope. The issue would be caused by a defective SSD being unable to handle the edge case scenario of *checks notes* reading and writing data. Since that's all that Windows Search does. Reads shouldn't affect SSDs ever. Writes depend on volume and wear levelling. Windows Search very little writing in updating its database (just like slocate on Linux doesn't either), the database simply isn't very big. Sounds like someone's SSD controller has a bug.
Re: (Score:2)
And still it wastes a lot of energy doing the indexing and the usefulness is marginal for most people. It has never helped me finding my documents but in many cases caused an unwanted result to pop over the wanted result right before I clicked the wanted result.
Re: (Score:2)
As much as it is uncomfortable to hear, sometimes correlated failures of hardware are simply related to manufacturing QA/QC and unrelated to any specific external change.
Correlation != Causation. The former is easy to assume, the latter hard to prove.
What? (Score:3)
If your OS is able to kill your SSD then I'd say the problem is the SSD.
Re: (Score:2)
Re: (Score:3)
Linux MD raid had a spat of random issues were it appeared that multiple disks without a partition suddenly got partitioned (on a boot). And at least some of those people NEVER dual booted (so no windows). The leading theory was that a bios/EFI update decided that disks that it did not identify as having data needed to get "fixed" and have a GPT partition table on it. There were 3-4 different people that reported this in a 2-3 month window with none since then, with a wide variety of controllers, but a n
Technically possible but not here (Score:2)
If your OS is able to kill your SSD then I'd say the problem is the SSD.
SSDs have limited write cycles. Any OS could, in theory, just send repeated unnecessary write requests until the SSD starts to fail although that would take considerable time since the SSD firmware spreads out the writes across the physical locations and it is hard to see how this could happen by accident. However, technically it is possible for your OS to kill your SSD if it tries really hard!
It works on my machine (Score:2)
So obviously, there isn't a problem.
Re: (Score:2)
It depends on how full they are and also how much additional space they have that they don't tell you about. If the volume is very full and there is not much additional space (and some drives have very little) then you can rewrite the same block fairly quickly, or a group of them anyway.
Re: (Score:2)
Your sample size of one concerns me.
And yes, one can easily be a coincidence. Often the person who wins the lottery thinks it's a miracle, but it's mundane.
Re: (Score:1)
I didn't have any NVME SSD failures until after 9/11!!!1!!
Re: (Score:3)
Spoken like someone who doesn't collect telemetry from 1 billion machines around the world. I think you and Microsoft do not have the same level of information.