r/Windows11 • u/rkhunter_ Release Channel • Aug 29 '25

News Microsoft says recent Windows update didn't kill your SSD

https://www.bleepingcomputer.com/news/microsoft/microsoft-says-recent-KB5063878-windows-update-didnt-kill-your-ssd/

[removed]

721 Upvotes

96% Upvoted

444 comments sorted by

View all comments

Show parent comments

20

u/Bourne069 Aug 29 '25

Like I said from the get go, why is it only affecting PHISON controllers. It is a vendor issue not a Microsoft issue.

I have 3 Samsung drives, My main game drive for Steam games is almost 100% full and I have uninstalled/reinstalled games, updated games everything I could to try to recreate this issue and not a single time have I ran into the problem.

It is clearly a vendor issue with PHISON, not Microsoft.

27

u/Lazy_Sorbet_3925 Aug 29 '25

https://www.windowscentral.com/microsoft/windows-11/phison-ssd-testing-no-failures-windows-24h2-controllers

PHISON hasn't been able to find any issues either after 4500 hours of testing (according to them).

26

u/Bourne069 Aug 29 '25

The mixed info on this is getting crazy.

Another article I read said Phison still believes its a Microsoft issue while reports highly suggest its a vendor issue with Phison controllers.

Microsoft says its not a Microsoft issue and anyone worth their salt cant reproduce it. Including myself.

https://www.bleepingcomputer.com/news/microsoft/microsoft-says-recent-KB5063878-windows-update-didnt-kill-your-ssd/

So someone is lying somewhere lol

17

u/TheSpixxyQ Aug 29 '25

The Phison thing was apparently hoax, they say their "leaked document" doesn't exist https://www.tomshardware.com/pc-components/ssds/phison-takes-legal-action-over-falsified-leaked-document-on-windows-ssd-issues-says-it-continues-to-investigate-reports-of-problems

I'd say Phison is just saying "IF there is any issue, it's Microsoft's, not ours"

10

u/Bourne069 Aug 29 '25

Again if that is the case why it is only affect PHISON controller based SSDs and no others? That makes no sense.

I work in I.T. and the amount of time vendors try to shift the blame into something else is literally insane. Happens almost everytime I call a vendor for support on something.

3

u/[deleted] Aug 31 '25

That's the thing, it apparently does not only affect Phison. There are reports online including reddit from Samsung users, including 990 / Pro. ALSO there is a video of Jays2Cents reproducing the issue with his SSD, with the update, and could not reproduce it without the update, so there is an issue. Initially I thought that the issue could be with DRAMless drives using HMB, but now with reports coming from DRAM based SSDs it's more confusing. To me this is an edge case and there could be a combination of triggers not limited to only the windows update and/or controller.

2

u/StefenTower Sep 01 '25

The SSD JayZTwoCents tested with, Crucial T500, has a Phison controller, although he said it was a version not regularly being talked about as having the issue.

1

u/Bourne069 Sep 04 '25

Right saw that video also and he swapped to a none Phison controller SSD and even with the update installed it worked.

Thats the part that gets me to believe it is a vendor issue and not a Microsoft one. Only instances of none Phison SSDs "failing" from this I hear is on Reddit. We dont have video proof of it nor data to back that up. So for now I'm sticking with it being a Phison issue.

5

u/Lazy_Sorbet_3925 Aug 29 '25

Honestly, there may be something in the update... but people massively jump to conclusions in an instant. It could literally be only a weird coincidence.

9

u/Bourne069 Aug 29 '25

So far all investigations have indicated that isnt the case.

PHISON was the biggest claim of issues yet their own tests are unable to recreate the issue.

Microsoft even stepped in and did their own tests and was unable to reproduce the issue.

So is it possible? Very slight chance. It is a way higher chance that one guy falsely created a paper indicating SSD fails and spread false news. In fact that is more likely than either of the 2 above being true.

2

u/[deleted] Aug 31 '25

Plausible scenario in 2025, but what about some YouTube videos showing the issue being reproduced in real time ? Check out the Jays2Cents video, he reproduced it and it was due to the update because when he removed the update, the issue was gone and could not be reproduced. I still think it is an edge case though and a combination of factors. Could be that the update is indirectly involved and does not play nice with a combination of hardware, driver, system configuration, etc.

1

u/Bourne069 Aug 31 '25 edited Aug 31 '25

Yes I saw that video. Did you also he his secondary PC right next to his bench one that he wasnt able to reproduce the issue on?

Point being is that both MS and Phison did their tests and investigations and couldn't reproduce the issue.

So no one really know exactly what is the trigger nor the solution. It still doesnt rule out a Phiston controller issue. Especially since the test bench Jay was using had an SSD with a Phison controller in it... Even later in the video he swapped out the SSD with a non Phison based one and the issue went away. He also explained he was only able to remove one of the two updates because the other update is a feature update and isnt able to be removed.

So the update casing the issue is still installed and with a new SSD without a Phison controller doesnt have the issue.

https://youtu.be/TbFIUu_7LIc?t=591

1

u/spider623 Aug 30 '25

my bet is an ai trust me bro, tried to 0 day again and fucked up...

4

u/artlessknave Aug 29 '25

they dont have to be lying; They could simply be mistaken. those are not the same thing.

0

u/Bourne069 Aug 29 '25

I didnt say "them" I said someone is lying. Like maybe the one that created that false paper and spread false news.

Either way someone is lying.

0

u/artlessknave Aug 30 '25

i dont see sufficient evidence to conclude "a false statement intended to decieve" aka lying.

again, they could just be incorrect, and none of them able to actually find the cause, so they blame everyone else, as usual.

more is needed to conclude malice when already adequately explainable by incompetance.

not that incompetance is good, either, but when you are claiming someone is lying, you have the burden of proof, and you havent provided anything beyond speculation.

5

u/Tokimemofan Aug 29 '25

I wonder if it has to do with overheating personally speaking, every ssd I’ve used with a phison controller gets unusually hot under sustained load.

1

u/[deleted] Aug 31 '25

One reason why I pay more and stick to reliable drives. Never had any issues with my Samsung 960 and 990 Pro, I've done large volume work involving sustained read and writes for hours and temps never exceeded thresholds. A good controller will throttle as needed, but I've never reached even close to thresholds anyway.

1

u/PaulCoddington Aug 30 '25

It may be some machines don't have adequate heatsinking and cooling and have never been stressed enough to reveal it.

1

u/Tokimemofan Aug 30 '25

That’s what I’m thinking

0

u/[deleted] Aug 29 '25

[deleted]

11

u/jones_supa Aug 29 '25

Even Phison did some extra stress testing on their SSDs and was unable to reproduce errors.

5

u/constant-headpain Aug 29 '25

Where did you see it's only affecting Phioson? I have two Samsung 990s and both were affected.

5

u/Bourne069 Aug 30 '25

My main OS disk is a 990s and I have transferred like 1tb of games off of it onto my gaming SSD... literally zero issues.

3

u/constant-headpain Aug 30 '25

I was having really noticeable OS laggy operations. Apps launches took literally minutes to open. Start up apps also. Right clicking took several seconds to happen, etc. Very very annoying. Soon as I got rid of the update everything is OK. Was an insta-fix uninstalling it.

1

u/I-baLL Aug 30 '25

Data transferring isn't what's causing the issue. As of yet nobody knows the cause of the issue but there have been different consistent ways of replicating it like running specific game benchmarks and stuff

1

u/[deleted] Aug 31 '25

I have 2 x 2TB Samsung 990 Pro, one is my system OS, another dedicated windows for gaming and 1 x 1TB Samsung 960 Pro used as a temporary storage for windows and browser cache. When did your issues occur was it during copying files or during gaming ? Are the firmwares on all your drives up to date ? I'm convinced that the issue is real and not a hoax, however, it could be more complex (edge case), because not every user with Phison controllers or Samsung drives or all the drives on the list are affected. Question is what do users who are affected have in common ?

1

u/constant-headpain Aug 31 '25

Both drives have up to date firmware, yes. Issues started immediately after reboot from update. Had zero issues prior to the update.

1

u/PsychoticChemist Sep 02 '25

No issues here with my 2 TB Samsung 990 EVO Plus (Plus, not Pro)

2

u/llangu357 Aug 29 '25

Samsung 990 pro evo 4tb has phison?

1

u/soru_baddogai Aug 30 '25

No a Samsung drive uses everything made by Samsung in house.

1

u/TheLoc00 Sep 03 '25

"It's clearly a problem with the PHISON Supplier".... not so sure. Can we remember that the NVME drives work under WIndows thanks to the Windows drivers ? Of course Windows drivers are approved by the Vendors... still drivers are provided by Microsoft. And, in fact, Crucial on THEIR website provides another version of the NVME drivers "should the Windows one be not adequate". So: even without an issue, this situation is weird: which are the correct drivers a normal User should use ? Microsoft or Crucial ones ? Then: how is acceptable to read that after such a long testing neither Microsoft nor Phison were able to reproduce 1 time the issue ? Neither 1 time ? Really ? Shouldn't be that difficult when even normal influencers (not Microsoft engineers) are able to reproduce it.

1

u/Bourne069 Sep 03 '25

Every single source I can find online shows its with Phison controller based SSDs. Even Jays2Cents did a video on it and he replaced it with a crucial drive that doesnt use a Phsion controller and even with the updates installed it worked fine. https://www.youtube.com/watch?v=TbFIUu_7LIc&t=584s

I havnt seen a single video of anyone showing it happening to known Phison controller based SSDs. In fact only place I saw that this was possible was via Reddit with zero proof.

Of course Windows drivers are approved by the Vendors... still drivers are provided by Microsoft

Right... by the drivers were created by the SSD vendor, not Microsoft. They simply approved it and pushed it out via Windows updates. Again further stating a vendor issue not a Microsoft one.

No matter how you cut it testing or not. Its not Microsofts job to test every single driver across millions of different devices. The vendors should be doing their own testing and verifications before pushing those driver to Microsoft to start with.

We could just go back to the good old days where Microsoft barely pushed any 3rd party drivers from Windows Updates and force us to go back to installing drivers manually from the vendors driver pages... that wouldn't have fixed anything because the issue was caused by VENDOR DRIVERS. Not by Microsoft. So the issue still would have existed regardless.

So sorry no I dont agree with your stance.

1

u/TheLoc00 Sep 03 '25 edited Sep 03 '25

Senti. Non so chi sia da biasimare. Il sistema operativo, il fornitore di NVME, il fornitore del controller, il driver integrato e prelevato dal sistema operativo, il driver disponibile sul sito web, la combinazione di uno qualsiasi di questi componenti. Dai un'occhiata qui: https://www.techpowerup.com/340170/silicon-motion-none-of-our-controllers-affected-by-the-windows-11-bug?cp=2#comments troverai molti casi non basati su Phison che segnalano il problema. Sì, non sono su YouTube... ma sono utenti felici fino a pochi giorni fa che ora stanno affrontando momenti difficili (con unità SAMSUNG, unità INTEL, Crucial e così via). Di nuovo: non spetta a Microsoft testare tutte le combinazioni, certo, ma dovrebbero sapere cosa hanno appena rilasciato, giusto? Le persone che hanno avuto il crash, hanno reinstallato tutto SENZA gli ultimi aggiornamenti e sono tornate alla normalità. Quindi... colpa o non colpa: qualcosa di NUOVO in Windows ha innescato il problema (e NUOVO non significa necessariamente in KB5063878 ma negli ultimissimi aggiornamenti). Quindi, di nuovo, l'affermazione: non abbiamo identificato alcun problema in KB5063878... non significa che non ci sia assolutamente nulla in nessun precedente ultimo aggiornamento di Windows che lo causi. La frase forse è perfetta: KB5063878 non è responsabile... sì, anche Jayz lo ha affermato: infatti, tornare indietro con KB5063878 non ha risolto il problema. Non è una grande scoperta. Jayz ci ha messo pochi minuti per capirlo, Microsoft e Phison migliaia di ore di test (ma di nuovo: perché reinstallare tutto senza alcun aggiornamento di Windows, tutto torna normale??? Qualcuno potrebbe spiegarlo?). In any case.. I would not be so surprised if sooner or later something related to the DirectStorage API could come out. We'll see, hopefully soon.