Link: https://youtu.be/TbFIUu_7LIc
Briefing: Windows Update and SSD Instability Issues
This briefing summarizes critical information regarding widespread SSD instability problems stemming from recent Windows updates, specifically focusing on the Faison controller issue and its broader implications.
- Widespread and Evolving Problem: The initial reports of SSD issues with Faison controllers caused by Windows updates (KB3878 and associated preview/cumulative updates) are significantly understated. The problem is affecting a wider range of Faison controllers (E12, E18, E21T, and now E25) and, critically, is now known to impact SSDs with controllers from at least four different manufacturers, not just Faison.
- Diverse and Unexpected Trigger Scenarios: The problem manifests in user scenarios "way different than what was reported." Initial reports suggested high data transfers (e.g., moving 50GB files on a 60% full drive) as the trigger. However, the demonstrated issue occurred during game benchmarking (F1 2024), where the drive would gradually decay in stability and eventually disappear, without large file transfers. This indicates a more complex and unpredictable trigger mechanism.
- Persistent Issue Even After Partial Update Removal: Uninstalling the KB3878 security update does not fully resolve the problem if a related cumulative update (also KB3878) remains installed. The cumulative update, being a feature install, cannot be uninstalled, only rolled back in its security portion, leading to continued instability.
- Hardware-Level Disconnection and Power Cycling Requirement: When the SSD fails, it completely disappears from the system BIOS, rendering it unbootable. A simple software restart (soft restart) is insufficient to bring the drive back online; a full power cycle (complete power-off and then power-on of the system) is required. This suggests a firmware or controller-level failure where "the voltage needs to be severed to the controller so that the controller can like go into this full restart state."
- Misdiagnosis and User Frustration: The problem can easily be misdiagnosed as GPU driver issues, overclocking instability, or general system instability, leading users to undertake extensive and fruitless troubleshooting. The subtle nature of the failure (a "slow crash" or data reading error before complete disappearance) further complicates diagnosis.
- Lack of Official Acknowledgment and Workaround: While Faison has acknowledged the problem (though struggling to recreate all scenarios), Microsoft has not. There is "literally no workaround right now" other than replacing the affected SSD with one that does not use the problematic controllers.
