PSA Aug 19 2025 - Windows 11 Update KB5063878 may corrupt data or make drive disappear

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:

3 Likes

I have two of those exact SSDs in that links picture but I don’t see them listed. Am I in the clear?

Not sure, but if your SSD is one of the ones listed, I suggest checking your Windows Update history for KB5063878, and if it’s there, roll it back.

It’s pretty messed up when the OS corrupts the storage media.

1 Like

Thanks for sharing. We already have a thread discussing Windows 11, including its bugs, issues, and other shortcomings.

https://forums.flightsimulator.com/t/windows-11-24h2-and-msfs-observations-insights-issues-and-tips/657704

If possible, please add information like this one in the linked thread instead. Having one main topic is much better than 50 separate ones :smiley:

1 Like

Yes, but it’s kind of an urgent and very specific PSA notice - which I fear would not get noticed in a general thread.

4 Likes

Ok it looks like it was installed and I uninstalled it. I really appreciate the heads up!

1 Like

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.

1 Like

I for one disagree. Would have never noticed this buried in the other thread. Having uninstalled this update … thanks to the original poster.

10 Likes

I similarly believe this kind of thing warrants a separate thread.

5 Likes

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.

3 Likes

I’m unable to uninstall it. I get an uninstall failure error.

If you are comfortable with command line, you could try the following. I suggest making a restore point first:

  1. Click Start Menu and type CMD
  2. Right Click on Command Prompt to open it with Administrator Privileges
  3. 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.

1 Like

I reset my PC four days ago. It shows four security updates on that day. And that’s one of them. I’ve got the Corsair SSD. Hmmm

Got it. I’m good. tks

1 Like

No, some people only look for new and unread tracked threads. I would not have noted it otherwise.

3 Likes

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.

If you set the forum as I suggested, you won’t miss any new topic or posts.


As mentioned earlier, it’s best to add posts about Windows 11 in the linked thread.
https://forums.flightsimulator.com/t/windows-11-24h2-and-msfs-observations-insights-issues-and-tips/657704

Let’s keep the forum organized :slightly_smiling_face:

Fly safe.

2 Likes

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.

yikes. I’d still recommend rolling back this new KB, especially if you have one of the WD drives listed.

I expect there would be updates coming from Microsoft and possibly new firmware from some vendors, depending on what the root cause is.

Thanks for sharing this. I also have a WD Black 2TB drive. I’ll be updating the firmware.
I’m on Win 11 23H2, so maybe it doesn’t affect me. Still…

Just check Update History for KB5063878 … not sure if it only gets installed for 24H2 or not.

Some new reporting on the issue: