Microsoft Says Recent Windows Update Didn't Kill Your SSD (bleepingcomputer.com)
- Reference: 0178932042
- News link: https://hardware.slashdot.org/story/25/08/29/1824219/microsoft-says-recent-windows-update-didnt-kill-your-ssd
- Source link: https://www.bleepingcomputer.com/news/microsoft/microsoft-says-recent-KB5063878-windows-update-didnt-kill-your-ssd/
> 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."
[1] https://www.bleepingcomputer.com/news/microsoft/microsoft-says-recent-KB5063878-windows-update-didnt-kill-your-ssd/
What? (Score:2)
If your OS is able to kill your SSD then I'd say the problem is the SSD.
Re: (Score:2)
The assertion that the update is killing disks may be exaggerated. Many people believe that the bug corrupts the partition, which prevents the "drive" from being available to Windows. If that's the case, it may be repairable by booting into a real operating system and running some tools to correct the partition metadata.
Re: (Score:2)
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)
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.
Nothing to see here, just move along? (Score:5, Informative)
The controller manufacturer that was reportedly most commonly involved (Phison) also released a statement saying they can't reproduce the reported failures.
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)
Maybe dual or multi boots is the connection MS is trying to kill? "As always, we continue to monitor feedback after the release of every Windows update, and will investigate any future reports" Sounds like recall/co-poilot/AI/whatever are doing the monitoring while MS is oppressing their users.
Re: Nothing to see here, just move along? (Score:2)
Name a time Microsoft has not been terrible.
Re: (Score:2)
1974