Just a PSA about the latest Windows 11 update KB5063878 or Insider Preview KB5062660 causing possible data corruption or drive loss when writing large amounts of data (as games like MSFS do).
According to Phison (maker of SSD controllers), on certain Phison based NVMe or SATA SSDs, when writing large amounts of data (or installing large games) Windows can lose or corrupt the data or even the drive itself, especially if the drive is over 60% full.
I can only imagine that Microsoft is aware and working on a fix, but if your SSD is one of the affected ones, might want to roll back the update for now. Screenshot from JayzTwoCents video below:
I get what you mean, but honestly, if we started making a new thread for every Windows 11 flaw or bug that could affect hardware, we’d already have 500+ separate topics by now - because Windows 11 has that many (and more) issues. That’s exactly why it’s better to keep one main thread instead of dozens of new ones.
Your PSA is important, but if you post it in the main thread it will still get noticed.
Yes, as it will be short lived (hopefully a fix is issued soon) and can then disappear. Since potential data and even hardware loss is pretty serious so thought I’d post. Most people would never see this news, but I tend to follow IT news and saw it.
If you are comfortable with command line, you could try the following. I suggest making a restore point first:
Click Start Menu and type CMD
Right Click on Command Prompt to open it with Administrator Privileges
In the Command Prompt, type the following:
wusa /uninstall /kb:5063878 /quiet /norestart
Translated: Windows Update will uninstall KB5063878, the Quiet flag suppresses prompts, the Norestart flag prevents automatic restart when it completes… but you would want to restart after this.
You should probably delay Windows Update for a while to prevent it from re-installing the update.
I’m not here to teach how to use the forum, but since I like to help: some threads are worth monitoring. Just set them to Watching at the end of it to get all notifications.
Another useful option is to set the forum to show threads with new posts first. Just click Latest at the top to stay up to date with topics that interest you.
This bug seems very much like a similar bug which was introduced with the release of 24H2 around late October/early November 2024, which affected a number of WD_Black 2TB nVME SSDs (ask me how I know). After finally stumbling across an article about the particular bug from 24H2 in a tech blog, I tracked down a firmware update for my drive and all my problems were resolved.
EDIT: Fortunately, none of the three m.2 drives in my recently-built system appear to be affected by this new bug.