Important warning about the latest Windows Update - do not install!

Summary

A recent Windows 11 update (KB5063878) has caused significant issues with Faison controller-based SSDs, leading to data loss and drive disappearances during large file transfers. While Microsoft has not yet officially acknowledged the problem, Faison has confirmed they are in talks to resolve it. Affected users may experience blue screens and data corruption, particularly when installing large programs or moving files. The video provides solutions, such as rolling back the update, turning off automatic updates, and checking if your drive is on the affected list. The issue appears to impact many popular SSD models, with recovery often possible after reboot.

Takeaways

• 😀 Windows 11 updates (KB5063878 and KB5062660) are causing Faison-based NVMe SSDs to disappear during heavy file transfers, leading to data corruption and crashes.
• 😀 The issue affects SSDs under heavy write loads, such as when installing large games or moving big files (over 50GB).
• 😀 Some SSDs may recover after a reboot, but others may fail permanently, risking data corruption.
• 😀 Microsoft has not officially acknowledged the problem, though Faison has confirmed they are working with Microsoft to address it.
• 😀 Affected SSD models include Western Digital, Corsair, Crucial, ADATA, HP, SanDisk, and others using Faison PS5012-E12 controllers.
• 😀 Not all drives with these controllers are affected. Some models, like the Corsair MP510 and Western Digital Blue 500GB, recover after reboot.
• 😀 Users experiencing crashes or disappearing drives should uninstall the problematic Windows updates (KB5063878 or KB5062660) to avoid further damage.
• 😀 It's recommended to turn off automatic updates to prevent the updates from being reinstalled after rollback.
• 😀 Unaffected drives, like the Samsung 990 Pro and Seagate FireCuda 530, do not experience these issues under the same conditions.
• 😀 To roll back the update, go to 'Settings > Windows Update > Update History' and uninstall the specific KB update causing the issue.
• 😀 Until a patch is released, avoid installing large programs or moving large files to prevent data corruption or crashes.

Q & A

What issue is being discussed in the video?

The video discusses a problem with certain Windows 11 updates (KB5063878 and KB50626606) that cause some SSDs, especially those with Fison controllers, to disappear from Windows under heavy data loads, potentially leading to data corruption.

Which SSD controller brand is primarily affected by this issue?

The primary SSD controller brand affected is Fison, specifically the PS5012-E12 controller.

Are only NVMe SSDs affected by this issue?

No, while most affected SSDs are NVMe, some SATA drives using affected controllers can also experience issues.

What conditions increase the likelihood of an SSD disappearing?

Heavy write loads, transferring large amounts of data (around 50 GB or more), and drives being more than 60% full increase the likelihood of an SSD disappearing.

Does the SSD always disappear permanently when this issue occurs?

Not always. In many cases, the drive reappears after a Windows restart, but there are instances where it does not recover, which can risk data corruption.

Can you name some SSD models that have been reported as affected?

Affected models include Western Digital Blue 5000 2TB, WD Red SA500 2TB, Corsair MP510 960GB, Corsair Force MP600 2TB, Skinx Platinum P41 NVMe, Crucial P3 Plus NVMe, Data Legend 8002TB, HP FX70002TB, and XPG SX8200 Pro 2TB.

Which SSDs have been reported as unaffected by this issue?

Reported unaffected SSDs include Samsung 990 Pro, Samsung 980 Pro, Samsung 870 EVO, Western Digital Black SN7100, WD Blue SA510 1TB, Seagate FireCuda 530 1TB and 2TB, Solid GM P44 Pro, Crucial T700, and SanDisk SSD 240GB.

What is the recommended immediate solution for users concerned about this issue?

Users are advised to uninstall the problematic Windows update (KB5063878 or KB50626606) through Windows Update history and turn off automatic updates to prevent reinstallation.

Why should users consider rolling back the update even if their SSD is not listed as affected?

Because the issue is still early and not all drives have been tested, other SSDs could be affected, and leaving the update installed risks potential data corruption or drive failure.

Has Microsoft officially acknowledged the problem?

No, Microsoft has not officially confirmed the issue yet, but Fison has acknowledged it and is in talks with Microsoft.

What common user experiences might indicate this SSD problem?

Users may experience blue screens during heavy file transfers or game installations, drives temporarily disappearing from Windows, or repeated crashes that might be mistakenly attributed to RAM, CPU, or overclocking issues.

What precaution should users take while Microsoft issues a fix?

Users should avoid installing large programs or transferring large amounts of data to affected SSDs until the issue is resolved or the problematic update is removed.