On Sun, 8/31/2025 3:37 PM, J. P. Gilliver wrote:

On 2025/8/31 5:21:6, anon wrote:

[]

they had experienced similar issues. But, there was little evidence to
suggest it was widespread and it’s entirely possible that this is a
localized problem related to a bad batch of drives. So it seems there’s >> little reason to believe the August 2025 Windows security update is going >> to fry your hard drive, no matter what some dude on TikTok says.

[]

Unless you happen to have one of that "bad batch of drives", which has
been working fine until this "up"date?

If there _is_ such a "bad batch", we need a way of identifying whether a drive is from it.

I don't know about you, but until the parties actually do some
work (the right kind of work), I would:

1) Boot Linux (not hearing Linux users squealing about this).
2) Clone NVMe to SATA SSD (clonezllla).
3) Shut down Linux. Boot off SATA SSD. Enjoy my day.

If the lab people at the guilty companies can get a
"reproducible test case" from the hobby community,
that will go a good distance to getting this fixed.

And rest assured, while the P.R. departments have dropped poo
on this report, there are definitely people working in labs
this afternoon on it. It's 70 hour work weeks until you find
the root cause. No time off for labor day.

And no, it's not a bad batch. Bad batches are much more likely
on HDD (with lots of mechanical parts). NAND storage has changed
the distribution of where the flaws will be. First generation
SSDs were a shit-show on firmware. Look at the progress they made.

The NAND chips are screened. They put the bad chips in your USB stick :-/

Paul

--- MBSE BBS v1.1.2 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

For the last week or two, reports have been circulating that recent
Windows 11 updates (specifically KB5063878 and KB5062660) were causing
some SSDs using Phison controllers to fail. Tech influencers on YouTube
and TikTok were quick to jump on the reports of corrupted data and disappearing drives, laying the blame squarely at Microsoft’s feet. We’re
not saying any company is above lying to the public, and Microsoft has a history of rocky update rollouts, but both Microsoft and Phison claim
they’ve been unable to recreate the issue.

Phison said it was made aware of reports that the Windows update was
causing drives to fail on August 18th and began investigating the issue.
Then it issued a statement on August 27th saying that after running over
2,200 test cycles totaling more than 4,500 hours it was, “unable to
reproduce the reported issue, and no partners or customers have reported
that the issue affected their drives at this time.”

Microsoft followed up just a few days later by saying that, “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.”

This isn’t terribly surprising since the reports were fairly limited. A Japanese user on Twitter appears to be the first to suggest the Windows
update was bricking SSDs and there were some in the comments claiming that they had experienced similar issues. But, there was little evidence to
suggest it was widespread and it’s entirely possible that this is a
localized problem related to a bad batch of drives. So it seems there’s
little reason to believe the August 2025 Windows security update is going
to fry your hard drive, no matter what some dude on TikTok says.

https://www.theverge.com/news/768431/windows-update-didnt-brick-your-ssd


--- MBSE BBS v1.1.2 (Linux-x86_64)
* Origin: dizum.com - The Internet Problem Provider (3:633/280.2@fidonet)

On 1/09/2025 7:33 am, Paul wrote:

On Sun, 8/31/2025 3:37 PM, J. P. Gilliver wrote:

On 2025/8/31 5:21:6, anon wrote:

[]

they had experienced similar issues. But, there was little evidence to
suggest it was widespread and it’s entirely possible that this is a
localized problem related to a bad batch of drives. So it seems there’s >>> little reason to believe the August 2025 Windows security update is going >>> to fry your hard drive, no matter what some dude on TikTok says.

[]

Unless you happen to have one of that "bad batch of drives", which has
been working fine until this "up"date?

If there _is_ such a "bad batch", we need a way of identifying whether a
drive is from it.

I don't know about you, but until the parties actually do some
work (the right kind of work), I would:

1) Boot Linux (not hearing Linux users squealing about this).

Hmm!! I knew there was a reason I hadn't gotten around to installing
Linux on this Desktop over the last six months or so!! ;-)

2) Clone NVMe to SATA SSD (clonezllla).
3) Shut down Linux. Boot off SATA SSD. Enjoy my day.

If the lab people at the guilty companies can get a
"reproducible test case" from the hobby community,
that will go a good distance to getting this fixed.

And rest assured, while the P.R. departments have dropped poo
on this report, there are definitely people working in labs
this afternoon on it. It's 70 hour work weeks until you find
the root cause. No time off for labor day.

And no, it's not a bad batch. Bad batches are much more likely
on HDD (with lots of mechanical parts). NAND storage has changed
the distribution of where the flaws will be. First generation
SSDs were a shit-show on firmware. Look at the progress they made.

The NAND chips are screened. They put the bad chips in your USB stick :-/

Paul

--
Daniel70

--- MBSE BBS v1.1.2 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)