Thank you for letting us know about this because I definitely wouldn’t have noticed if I hadn’t seen the title.
3 Likes
The bug that affected my drive seemed to affect only a few models - this article shows drive models which were affected. After updating the drive firmware, every one of my numerous stability issues in FS’24 went away (I have the sim installed on this drive).
I have just moved this drive over to my new system and jumped through all the usual Windows Update hoops last night. I haven’t flown the sim enough on the new system to know if Windows has mangled things for me yet again, though this article indciates that WD_Black SN770 models are not affected by the most-recent Windows foibles.
After reading the articles I think it’s all much ado about nothing. Having the scenarios play out that makes something happen to you SSD is super slim. In most cases it’s recoverable by a reboot. Worse that can happen is it does kill your SSD and in most cases would be covered by the manufacturer. Haven’t backed up would be your own fault. SSD aren’t that expensive these days. Though I did uninstall it I will probably resume updates.
I thought the earlier problem you solved with the firmware update was caused by the 24H2 update. Did I read that wrong?
Thank you @GimbalAxis for this PSA, I would never have seen this otherwise and I do own 2 of the affected SSDs (one of which, of course, holds my nearly 1TB MSFS install). I tip my hat to these astoundingly talented developers at Microsoft. Until next time!
1 Like
I didn’t solve anything. Dr Venkman said he has a WD SSD that had a very similar issue with a previous bug that became apparent with a previous update in Windows 24H2 earlier this year, addressed by a firmwre update.
You’re right. 
Wow! Causing CTD’s, data corruption, and possible data loss is ‘much ado about nothing’?
You are joking aren’t you?
1 Like
Read the articles. Chances of it happening to you are very very very slim. And it’s not even proven it’s the culprit. Even in the slim chance it does, don’t you back up your data? SSDs are cheap these days. What are you worried about?
“Read the articles. Chances of it happening to you are very very very slim. And it’s not even proven it’s the culprit.” True, slim chance, and true it may not be the culprit, although there does seem to be some degree of causal link and corroboration. I just think it needs jumping on with some urgency, which seems to be what they are doing now thankfully.
Backups? Yes, but as for the drive, my 4TB NVMe isn’t cheap. You must have a lot more money than me if you think it would be cheap to replace. 
1 Like
The Microsoft August update for Windows 11 (KB5063878) has more and more significant issues popping up. At least they are acknowledging them, and hopefully the data corruption / SSD disappearing issue is addressed soon.
After much testing, Phison (maker of controllers used in many SSDs) says issues related to KB5063878 may be “false alarm”.
PSA part 2 - JayzTwoCents reporting that this issue is not solved, and affects at least 4 controller types.
1 Like
Very interesting twist in this story, which I’ve been following with some interest:
- Microsoft issued KB5063878 in August, and a few people started reporting that it corrupted or disappeared their SSDs
- A pattern emerged that suggested it affected SSDs with Phison controllers - but not exclusively - on SSDs that were 60%+ full and writing large amounts (50GB+) at a time…
- Microsoft and Phison started doing a lot of testing, and both companies could not duplicate the errors.
- Phison then put out a note suggesting they WERE able to reproduce the problem but only on hardware with certain non-production pre-release test versions of BIOS - and concluded that the affected consumers, and Youtubers, must have somehow acquired non-sanctioned BIOS…
- Meanwhile, the number of people experiencing the problem continued to expand
- JayzTwoCents had a test rig that was affected, and demonstrated that his BIOS was an older version, but very much a public release version, and the problem affected his system.
- So just to see, he updated the BIOS on his computer, and the issue seemed to go away for the same hardware!
Conclusion, the KB5063878 update seemed to trigger the issue on (mostly) Phison controlled SSDs, on certain versions of older BIOS. But those versions of BIOS have been out there, working, solid for quite a while, and were only triggered by the Windows update.
His conclusion is that something perhaps in older AGESA versions did not play well with the new Windows update. And so the long-standing advice to not update BIOS when everything is working is now in question…
Lesson: Always have a backup!
Actually, that conclusion is a bit off.
You don’t always need a backup - what matters is not blindly following advice like “if your BIOS works, don’t update it”.
I’ve always recommended updating BIOS, and I still do, even here on the forum. Of course, there are exceptions, but they’re so rare that it’s generally worth having the latest BIOS version. Just keep an eye on your motherboard manufacturer’s forum - if there aren’t a dozen posts saying the new BIOS is causing problems, it’s safe to install it. For example, just a few hours ago I installed the latest BIOS on my motherboard without any issues
MSI X870E Carbon WIFI BIOS ver 1A64
- AGESA PI 1.2.0.3g updated.
- Improved compatibility of the Ryzen 8000 series CPU.
1 Like
Those same notes are listed for the newest BIOS available for my MSI MAG X870 Tomahawk, ver 1A68. I haven’t updated yet as I am at work, and I’m going out of town for 8 days starting tomorrow, so I’m likely to wait until I get back and see if there are any issues reported by then.
Not sure if this is related, but after the update today, some of my Quick Access links disappeared. Also, the update restored a copy of my Desktop, so I had copies of all my shortcuts.