New Windows Update could brick your SSD

mrk said:
This further lends ammo to the notion that an engineering FW as per above is the likely cause.
Click to expand...
Kind of, the question is why are people reporting that once the update is removed they can't recreate the issue.

While the update may not be the cause it does seem, from report, to trigger the issue.
 
Nothing is ever 0%, and the sake pf probability vs correlation and all that has to be factored in as well.
 
Losing all faith in the human race these days. If it's not the lowest IQ engineering on bicycle internal cable routing and no limit screw mechs, it's £6000 interconnects to listen to a recording made in the 60's with bell wire, or operating systems that brick something every few months, to feautures on motherboards too limited to have the features, like paying for beans on toast but you can only have beans or toast, not both, despite paying the premium, cheese! forget it pal!

How can people be losing NVMe's in this day and age yet no one knows why?

Still got a PC to finish the basic build on, running Linux from a Sata drive, with three NVMe and a GPU sitting in their boxes, and an unused Windows 10 license that now seems like a gamble to update to 11.
 
Windows says it's not their fault, they blame poor quality firmware on the affected storage drives, says manufacturer needs to fix or update your firmware
 
Last edited:
www.neowin.net

Phison confirms potential real reason for "Windows 11 SSD killing and corruption" bug

It looks like the actual cause of the SSD failure issues that were blamed on Microsoft's Windows 11 24H2 has been confirmed by Phison.
www.neowin.net www.neowin.net

In response to the recent PCDIY! Facebook post, Phison engaged the PCDIY! contact to investigate.

The results shown in the link below detail that Phison examined the exact SSDs used in the PCDIY! testing and determined PCDIY! was utilizing an engineering preview firmware, which is not the final firmware used in the CORSAIR FORCE SERIES MP600 SSD 2TB and other drives with the E16 controller available for sale to consumers on the market. Phison also replicated the PCDIY! tests on-site with the same SSD models and the same stress tests (100GB/1TB writes) utilizing consumer-available SSDs and found no failures or crashes.
Click to expand...

Phison tested the same SSDs with same engineering firmware used in PCDIY! test ran same stress tests but found no failures, crashes or BSODs. They probably used different motherboards in tests.

SSDs failures in PCDIY! tests probably caused by bugged BIOS or outdated drivers or third party apps they installed on Windows 11.
 
www.techradar.com

Windows 11 SSD failure saga takes another twist with a suggestion that glitchy firmware is to blame

Is pre-release firmware to blame?
www.techradar.com www.techradar.com

Update: Phison's US GM and President, Michael Wu, provided a statement to The Verge which explains that the SSD issue appears to be related to 'preview drives' provided to reviewers.

Wu said: "Many of the reports [of vanishing SSDs] originate from media testing conducted on hardware running early versions of firmware and BIOS. These versions are performance preview drives and are not identical to those provided to end users through official distribution channels. We have observed that outdated firmware is still being used on some SSDs and we encourage any reviewers facing this to leverage updated channel firmware readily available through manufacturer-provided update utilities."
Click to expand...

If Jay2Cent used preview Crucial T500 SSD sample for reviewers with engineering firmware then Jay is an idiot not updated SSD firmware and Asrock motherboard BIOS to latest version.
 
Last edited:
CuriousTomCat said:
This issue is real. I've dealt with it on two separate customer machines this week.

Gaming PC – 4TB Samsung 980 Pro (Elpis Controller)

- Stable in Windows until writing large chunks of data
- Crashes with WHEA_UNCORRECTABLE_ERROR
- No event logs captured
- SSD disappears from BIOS post-crash
- Requires full power cycle to restore visibility
- Issue reproducible consistently

Gaming Laptop – 1TB Kingston NV2 (Phison E21T Controller)

- Crashes with - INACCESSIBLE_BOOT_DEVICE
- No event logs captured
- SSD disappears from BIOS post-crash
- Requires full power cycle to restore visibility
- Issue reproducible consistently

KB5063878 couldn’t be uninstalled, and there were no restore points available.

Workaround:

I cloned the NV2 to a 1TB Kingston NV3 (different controller). That allowed me to boot into Windows. It eventually blue screened again with INACCESSIBLE_BOOT_DEVICE but at least I had a working environment to troubleshoot. To reduce disk I/O, I disabled all non-essential services and startup programs. After hitting a brick wall, I downloaded the Windows 11 ISO from Microsoft and installed it over the top while preserving the customer’s programs and files. Unfortunately, KB5063878 had been slipstreamed into the ISO, so the issue persisted. Luckily, I had a June ISO without KB5063878. I installed it over the top, while again, retaining the customer’s programs and files. After that, I carefully installed updates and used WuShowhide.diagcab to block KB5063878 as soon as it appeared. I also blocked the follow-up update it tried to push. I then cloned it back to the original 1 TB Kingston NV2 SSD and it worked.
No issues since.

This isn’t anecdotal - it’s repeatable, controller-specific, and disruptive. If you’re seeing similar symptoms, check your SSD controller and block KB5063878 before it takes your system down. Happy to share more details or logs if it helps others confirm the pattern.
Click to expand...

Hey man, I'm sorry that you've had it happen to you; but thank you for sharing this in my thread, hands on experience with the issue, definitely helps!
 
Last edited:
My Crucial T705 4TB drive has been affected, thought I'd paused Windoww updates, but on shut down updates applied and my drive was gone. Fortunately, it's only my game drive, and only 3 months old so still well within warranty.

It showed back up only after a full power cycle, and discharge of the capacitors. (PSU off, power button pressed until lights go off).

So I understand this will keep happening, until they issue a proper fix, but is the drive actually borked?
 
Vidar said:
My Crucial T705 4TB drive has been affected, thought I'd paused Windoww updates, but on shut down updates applied and my drive was gone. Fortunately, it's only my game drive, and only 3 months old so still well within warranty.

It showed back up only after a full power cycle, and discharge of the capacitors. (PSU off, power button pressed until lights go off).

So I understand this will keep happening, until they issue a proper fix, but is the drive actually borked?
Click to expand...
Do you have an Intel or AMD system?
 
Vidar said:
My Crucial T705 4TB drive has been affected, thought I'd paused Windoww updates, but on shut down updates applied and my drive was gone. Fortunately, it's only my game drive, and only 3 months old so still well within warranty.

It showed back up only after a full power cycle, and discharge of the capacitors. (PSU off, power button pressed until lights go off).

So I understand this will keep happening, until they issue a proper fix, but is the drive actually borked?
Click to expand...
Your drive not borked.

Phison president said it not Windows update KB5063878 fault, the only proper fix is to update both your SSD firmware and motherboard BIOS to latest version.

You will need to download Crucial Storage Executive to update your Crucial T705 firmware.
 
I'm afraid I don't believe that firmware thing is the problem. Physon may have found a problem that can occur in some circumstances, but this is not limited to drives with their controllers.
 
jaybee said:
This thread is like Borris Johnson's speech about COVID and staying at home. What a bunch of muddled information.

Might be a bug not a bug.
Might be Phison not Phison.
Might affect certain drives but can affect all drives.
Affects AMD but doesn't affect AMD.
Caused by Microsoft update not caused by Microsoft update.

Please all take the relevant precautions and ensure you are up to date with updates, but of course, use due diligence and avoid all updates.
Click to expand...


Is this still offering the greatest clarity on this situation, putting aside Jay's 1000% assurity of it being a kb update on his system..?
 
Rogueywon said:
I'm afraid I don't believe that firmware thing is the problem. Physon may have found a problem that can occur in some circumstances, but this is not limited to drives with their controllers.
Click to expand...
I believed old SSD firmware caused the problem. Many people had SSDs disappeared been gone on for years and in all cases only new firmware fixed it.

So you got 2 Samsung 990 Pro SSDs, it odd that 1 disappeared but the other one not disappeared.

I think your case are unrelated to Windows update KB5063878. Samsung 990 Pro owners reported SSD disappeared had been gone on since around 2023.


1 Samsung 990 Pro owner reported on Samsung forum in July 2025 about drive disappeared problem with old firmware 4B2QJXD7 and later confirmed 2 weeks later in August that new firmware 6B2QJXD7 fixed drive disappeared bug issue.


Have you updated your 2 Samsung 990 Pro to latest firmware 6B2QJXD7 yet?
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom