Just throwing this out there for users of WIndows 11, who have updated to the latest version.
Prolonged writing of 50 gb or more can cause your SSD to become corrupted and unreadable by your OS. It’s confirmed across multiple SSD brands, and includes NVMe drives.
Be very careful with this new update, and I hope you aren’t affected.
http s://www.youtube .com/watch?v=mlY2QjP_-9s
does microsoft have it in their TOS they cannot be sued due to damage done by windows software?
if not, i could see a class action lawsuit happening
I do not know, but probably, they have teams of lawyer’s write their TOS and EULA.
i could imagine, “ssd dies to windows update”
buys new ssd installs windows “ssd dies installing windows”
furious screaming insues
I’d just jump to Linux at that point.
inb4 Linux folx tell everyone to switch to Arch
Jokes aside, this is actually insane. Is this with 2025-08 B or any other versions of 24H2?
I’d imagine with Windows 10 end of life just under 2 months away a LOT of users and companies are updating right now (I’m personally managing multiple 100-250 user companies going from Windows 10 to Windows 11 at the moment)
They’re known as KB5063878 and KB5062660. Both are confirmed to be causing the issue.
Cheers legend, will keep an eye out.
From what I had reviewed of the issue (learning of it today) it doesn’t affect every drive. Kingston wasn’t among the listed ones that I saw so far.
However.
I have encountered recently two different systems, both with Intel SSDs that have corrupted themselves… One was an Acer, the other is an Asus. I replaced both with a Kingston. But this was before finding out about this. And my system gets sustained heavy writes a lot. Currently has over 21TB written.
My system here runs a Kingston Fury model, those other two got standard 6k Kingston drives. No issues with mine, but now I’m watching my laptop, as it has a Samsung.
Sadly, both of those Intel drives were completely unusable. Couldn’t access them from various external bay readers, or internally mounted.
lol
People didn’t even look/read what the problem is, but they blame windows right away…
It’s entirely and only the fault of some SSD manufacturers, windows didn’t do anything wrong here
If Windows pushes an update, and it bricks SSDs… It’s on the SSD manufacturer… When it was perfectly fine before the update… but Windows isn’t at fault.
(Microsoft even admitted it’s part of the update causing issues)
It doesn’t, a Japanese site has gone through and tested a lot of drives, and compiled a list of affected drives.
Samsung isn’t one that’s been affected from what I’ve seen, and I’m glad… I’d be PISSED if this 4 tb 990 Pro bricked.
My laptop has the 1TB version of that drive I think.
As I recall, it was centered around specifics, like the SSD onboard controller used too (Phison). I haven’t read the full report, I was getting an overview from one of the youtube sources I follow.
While specific updates may have triggered the event, that doesn’t mean its directly MS’s fault. But I would highly recommend uninstalling those updates if any of you have a worry for now, and keep checking for any firmware updates for your drive that may resolve this issue. (you will have to download the drive’s diag tool from the manufacturer website for your SSD to do update checks)
On further examination, I’m still running on 23H2… I don’t even have this update in my system yet. But I know the laptop is on 24H2.
I got one of them installed on 8/13. Don’t have the other as far as I can tell.
Anyone remember how to remove them from Windows 11’s control panel?
Sony NVME’s affected?
Go to your Windows update page.
Update History
Uninstall updates (scroll down to find it)
Find the update and uninstall.
Thank you for letting me know.
I almost did their Upgrade to windows 11.
Seams like it is all too convenient that they are closing out 10 and pushing to 11.
Okay, same method as before, they just… sub-divided everything.
That’s why all the reported disks have phison controllers and phison is already investigating this.
Because windows is at fault. Right.
There is such a possibility, but I highly doubt it.
Aside from some UI complaints, 11 is pretty much better than 10 in every way – and I say this as a very long time holdout from 10. In cases like this people see 10 as more stable only because it’s not really being updated aside from critical security patches. 10 had it’s share of issues back in the day as well, but obviously if you only use something that’s been stabilized, then you’ll have fewer issues than bleeding edge. Win11 22H2 is probably also going to appear stable compared to the latest updates.
That said, this particular issue actually isn’t the fault of Windows 11, the new update simply pushed a change that exposes a hardware/firmware level bug in certain drives.
Yeah I think he is confusing “cause” with “fault” – The update was the cause of the issue by exposing an underlying hardware issue, which is not the same as being at fault.
So I downloaded GTA5, right?
Does that mean I’m safe?