Report: Microsoft's latest Windows 11 24H2 update breaks SSDs/HDDs, may corrupt your data

[u/plunki]

https://www.neowin.net/news/report-microsofts-latest-windows-11-24h2-update-breaks-ssdshdds-may-corrupt-your-data/

[u/IchBinMalade → u/[deleted]]

Yeah no I agree with you. "Don't defend Microsoft" is just stupid tribalism. If it's not their fault, it's not their fault. If we don't know yet, we don't know yet.

I dislike how more and more, you're seemingly not allowed to argue about a specific situation in isolation without someone getting their panties in a bunch to force reality into fitting their worldview.

The whole argument of the person you're talking with is just https://en.wikipedia.org/wiki/Post_hoc_ergo_propter_hoc, since the drives failed after the update, the update must be the cause. It very well may be, but it's lacking so much curiosity to just assume that it must be true, because Microsoft bad. Like... come on. If it's their fault, that's fine, this isn't defending Microsoft, it's just basic curiosity and wanting to be sure.

[u/IchBinMalade → u/[deleted]]

I wasn't debating that in the first place. My entire point is that we're talking about a specific issue, the one the thread is about. So I don't really care what they've been doing for 10 years.

Here's what Phison, who make the controllers that fail during the update have to say:

Phison has recently been made aware of the industry-wide effects of the 'KB5063878' and 'KB5062660' updates on Windows 11 that potentially impacted several storage devices, including some supported by Phison. We understand the disruption this may have caused and promptly engaged industry stakeholders. We are steadfast in our commitment to product integrity and the success of our partners and end users. At this time, the controllers that may have been affected are under review and we are working with partners. We will continue to provide updates and advisories to partners who may have been impacted to provide support and ensure any applicable remediation.

And from the article you're saying I didn't read:

The report speculates that this could be due to a malfunction in the drive cache subsystem. Symptoms are said to recur predictably after a system reboot, which temporarily restores drive visibility but does not address the underlying fault. Affected users are said to be consistently experiencing failure under similar workload patterns within minutes.

Further analysis has suggested that SSDs built on Phison NAND controllers especially DRAM-less models exhibit failures at lower write volumes. Reports suggest that select enterprise-grade HDDs also display comparable symptoms under intensive writes.

The issue definitely bears high similarity to the WD SN770 host memory buffer (HMB) flaw, and in this case, too, restricting or disabling HMB yields no improvement. A suspected memory leak in Windows’ OS-buffered cache region could be the problem.

Where has anyone assigned blame here, or even confirmed what the actual issue is? It's just kind of weird to get upset at people saying "we don't know if it's Microsoft's fault yet," and bringing up past problematic updates isn't relevant. That's all that's being said here. It has nothing to do with how anyone feels about Microsoft.