Right now, confirmed reports are only in the hundreds — but given Phison’s market share (40–50% of consumer SSD controllers), the real number could climb fast. If even 0.01% of affected systems hit that ~50GB write/60% load trigger, you’re looking at tens of thousands of failures worldwide. If the patch stays live and more users unknowingly stress their drives, worst-case it could creep into the hundreds of thousands. This isn’t just a niche bug — it’s hitting one of the biggest controller suppliers out there.

M$ and their "updates" destroying hardware not the 1st time and neither will be the last. Either they change their ways or consumers will change their ways(switching to Macs or Linux) which will end up like so many other giants who thought they were too big to fail.

inexistent QA, i dont even know what they have insider for

Mass lawsuit? Lately it seems that everything is a joke (see Crowdstrike flop) and companies losing a ton of money due to other's stupidity have nothing against it ...

MS now means Major Screwup

in the meantime, what are people to do without an avenue to replace bricks?

vibe coding should have never been a thing...

and oh, even disabling updates on a hardware firewall level doesn't block a lot of updates sadly. I dual boot on 3 laptops w Linux and w11 and I'm afraid to go into w11 now. Watch MS throw Phison under the bus like they always blame the hardware manufacturers when it's their friggin screwups!

Not just Phison there's a megathread on reddit where samsung users have this going on too and AFAIK samsung uses their own controllers and there's a few innogrit based drives also failing due to this.

WHAT A FRICKIN MESS!!!

Forget 11, I’m still hung up on MS pulling the plug on Windows 10. I know its around 10 years old now but it still feels fresh, solid and familiar.

Hope this lawsuit grows legs and kicks them in the teeth: www.techradar.com/computing/windows/microsoft-is-being-sued-for-killing-windows-10-here-are-5-reasons-why-the-lawsuit-could-actually-force-its-hand-to-extend-support-further?utm_source=chatgpt.com

Apologies for going off-topic - is MS keeping Extended Security Updates (ESU) strictly for business/enterprise or can regular users still get in? With certainty, not long ago they opened it up for personal users too. Thing is, I’ve seen the consumer ESU option appear and vanish from MS's own support page a couple of times now. Have the silly beans finally decided who’s actually allowed to subscribe or are they still faffing about?

wheresmycarForget 11, I’m still hung up on MS pulling the plug on Windows 10. I know its around 10 years old now but it still feels fresh, solid and familiar.

Win10 is trash. Win11 is by far the best OS Microsoft has made. Until the dream comes true for it to a be a Linux distro when Hell freezes over maybe 12 will be even better.

sooo make backups but only to files smaller than 50GB got it. Dreamcatcher on standby if things get really serious.

Its unrelated I think, but I had a file that became 0 bytes after a weird Windows issue, a cli binary was being blocked by Windows, saying its incompatible (when it isnt), I tried to restart the application info service, which wouldnt stop, I then killed its pid manually and restarted the service, the binary was after all this zero bytes. Reinstalled the binary and issue was gone, never thought something like that could corrupt files. I guess it can.

phintsWin11 is by far the best OS Microsoft has made.

I really don’t know if you’re serious because as much as I don’t have major issues with Windows 11, it’s far from being the best Microsoft has put out.

Windows 7 is, as the kids say, the GOAT.

Samsung too? 😰

I’ll admit when I’m wrong and this time, I’m definitely wrong. This is going to be a mess—a bigger mess than the Crowdstrike mess.

Windows 10 by far was more usable than W11, didn't shove AI copilot in your face, or break hardware with too many forced updates. But my favorite is Windows 7, and it had the best UI design.

Unfortunately Phison is probably going to get the blame for Microsoft's mess, but Samsung SSD's are failing too? Does it affect all Samsung SSD's or just the DRAM-less ones?

Hecate91Windows 10 by far was more usable than W11, didn't shove AI copilot in your face, or break hardware with too many forced updates. But my favorite is Windows 7, and it had the best UI design.

Unfortunately Phison is probably going to get the blame for Microsoft's mess, but Samsung SSD's are failing too? Does it affect all Samsung SSD's or just the DRAM-less ones?

990 pros are a lot of the complaints i think those have dram,

wheresmycarHope this lawsuit grows legs and kicks them in the teeth: www.techradar.com/computing/windows/microsoft-is-being-sued-for-killing-windows-10-here-are-5-reasons-why-the-lawsuit-could-actually-force-its-hand-to-extend-support-further?utm_source=chatgpt.com

Now that's one of those less sensible lawsuit of the US...
Real guestion is why there isn't class action lawsuit ripping MS new one for all the untested/known to be buggy updates forced on users.

I mean if you lose control of your car and crash into someones garden/house etc, or do it on purpose, you're going to pay for damages/the usual punishments for breaking law!
Now MS and Nadelle have been knowingly ***** up people's PCs for years with no repercussions.

Hecate91But my favorite is Windows 7, and it had the best UI design.

After that UI started going more backwards than forward with that Kool-Aid drinker of Ballmer.
And Nadelle is plain Kool-Aid factory.

We need Gates come out of retirement.

overclockedamdRight now, confirmed reports are only in the hundreds — but given Phison’s market share (40–50% of consumer SSD controllers), the real number could climb fast. If even 0.01% of affected systems hit that ~50GB write/60% load trigger, you’re looking at tens of thousands of failures worldwide. If the patch stays live and more users unknowingly stress their drives, worst-case it could creep into the hundreds of thousands. This isn’t just a niche bug — it’s hitting one of the biggest controller suppliers out there.

old ssd ..

remixedcat990 pros are a lot of the complaints i think those have dram,

I have a 980 pro 2TB, hopefully there is a fix soon, Samsung SSD's aren't cheap it would be really annoying to have the drive broken from an update.

EsaTAfter that UI started going more backwards than forward with that Kool-Aid drinker of Ballmer.
And Nadelle is plain Kool-Aid factory.

We need Gates come out of retirement.

I liked Ballmer more than Nadella, things started to really go downhill with Nadella and Windows 10, focusing on enterprise and getting rid of the QA team.
I assume MS is testing their updates with AI now given how many of them are causing issues.

I'm mildly worried about this... I can't rollback my update and so I'm just sitting here waiting for data corruption... SK Hynix P31 Gold SSD... Guess I should backup my new data? Worried a large read/write is going to screw things up...

Now that I know it’s not just Phison controllers and that it might affect Samsung and WD in-house controllers, I’m really worried now.

This is really going to blow up on Microsoft’s face and if you ask me, it needs to. Maybe (I hope) that this will be the wake-up call Microsoft needs to finally fix their shit.

This is a Phison issue, no need to stress about Microsoft being assholes (in cases like this, at least).

No, it isn’t. Ok sure, Phison controllers are showing up the radar more often when it comes to this issue but that’s only because a lot more budget SSDs feature Phison controllers.

There have been a few Samsung and WDC in-house controller SSDs mentioned as well.

I found this but I don't understand it fully. Can this protect from data loss? The message is from twitter:

There is a lot of ai involved in the original and the translation but here:
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Landmine Pattern 1: DRAM-less NVMe relying on HMB
In 24H2, the HMB allocation jumped from 64 MB to 200 MB → DMA fault → Controller went silent → OS detected "Surprise Removal" and SMART could no longer be read.

2. Old Phison FW
The E12 generation is prone to timeouts when rewriting the flash map, causing Storport to drop the entire bus → NG Lv.1.

3. SATA write cache outbursts. WD Blue SA510 2TB failed step 3. The drive experienced an NCQ timeout and went offline while the OS was forcing a cache flush.
In short, it's a trinity of "controller + presence/absence of DRAM + firmware generation."

Samsung Hynix is fine because they fixed the issue with their own firmware, while the cheaper DRAM-less ones are left behind by the Windows spec changes -- it's a blunt picture. (・ω・｀)

Solution: Disable HMB or set it to 64 MB. HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters HostMemoryBufferDisable=1 or HostMemoryBufferMax=40000

Many reports of BSOD and disk evaporation stopped on SN770/SN580

WD has improved this in the 2024/10 version and later, and the Phison E12/E16 series also has reduced timeouts in the 2025/05 version.

Currently, "low-cost" controllers such as Phison E19/E21, SanDisk G2, SM2269XT, and older Phison E12/E16/E18 series (older with DRAM)

There was an opinion that this was a high risk.
Also, it turns out that Nekoru is in favor of calling Samsung Electronics "Kanson" (cold village) (・ω・｀)
Well, rather than saying that the SSD manufacturer is to blame, it seems like this mysterious explosion is the result of Windows messing around with the cache specifications.

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Does someone here knows if it makes any sense?

HostMemoryBufferMax=40000

Can someone explain the 40000 setting?

Wouldn’t that make for a 40 MB buffer where it should be 64 MBs?

So this might be a situation that proves manually configuring HMB is the way to go vs trusting automatic behaviour?

Wow I just saw this. All my PC's just updated recently and I have a lot of Samsung drives and I do a lot of large file transfers daily Yikes!

JermelescuThis is a Phison issue, no need to stress about Microsoft being assholes (in cases like this, at least).

If the hardware works under windows 10 and Linux it most certainly is a MS issue.

It is hard to believe it is an accident with the MS"s resources.