Windows 11 Drive issue with KB5063878

[Teksonik]

This is the second video I've seen on this issue so I thought I would pass it along. Apparently there is a bug in Windows 11 update KB5063878 than can cause SSD drive corruption. My WD Blue SSD is not on the list but I am uninstalling KB5063878 as we speak out of an abundance of caution. Make sure to pause updates or you'll just get it back.

*Disclaimer* I'm not telling anyone what to do, this is for information purposes only.

https://www.google.com/search?client=fi ... ive+issues




This guy used to work for Microsoft:

[legendCNCD]

As usual with updates, wait for a while, never update immediately.

[uOpt]

As usual with updates, wait for a while, never update immediately.

Expose yourself to security risks, especially on Windows.

[Teksonik]

Yes it's a tricky proposition. Pass on security updates until you're sure they're bug free or update whenever they're offered to increase security and risk a buggy update.

I did have my updates paused for 1 week but KB5063878 still installed on August 13th the day after update Tuesday.

I've got it set to pause updates for five weeks but I'm going to keep an eye out just to make sure the KB doesn't sneak back in. They should have a fix by then. Phison is supposedly working on firmware updates.

My studio system never surfs the net or checks emails etc. It's connected just for copy protection handshakes and Plugin/DAW updates. So I should be safe for now.

[legendCNCD]

As usual with updates, wait for a while, never update immediately.

Expose yourself to security risks, especially on Windows.

Depends a lot on the nature of the update, and it is how we used to do things in IT department. Test the updates before letting them on the workstations. Now I'd rather let others test before updating _immediately_ - especially when the workstation is audio machine.

[uOpt]

As usual with updates, wait for a while, never update immediately.

Expose yourself to security risks, especially on Windows.

Depends a lot on the nature of the update, and it is how we used to do things in IT department. Test the updates before letting them on the workstations. Now I'd rather let others test before updating _immediately_ - especially when the workstation is audio machine.

The bad SSD update wasn't an isolated update, it was part of a tuesday patch. There is a donkeyton of security and other changes in there.

Delaying such an update is bad, especially for IT departments that don't want breakins. Testing these large updates is also impractical.

[Pictus]

Phison Posts Latest Update on SSD Controller Stability
https://www.techpowerup.com/340376/phis ... -stability
As stated on August 18, Phison was made aware of the KB5063878 and KB5062660 updates on
Windows 11 that potentially impacted several storage devices, including some supported by Phison.
In response, Phison dedicated over 4,500 cumulative testing hours to the drives reported as potentially
impacted and conducted more than 2,200 test cycles. We were unable to reproduce the reported
issue, and no partners or customers have reported that the issue affected their drives at this time.

[Pictus]

Root cause for why Windows 11 is breaking or corrupting SSDs may have been found
https://www.neowin.net/news/root-cause- ... ound/PCDIY!
"Testing has revealed that the SSDs crashing and crashing due to the Windows 11 update were using
pre-release, pre-final versions of the engineering firmware."