What looked like yet another Windows 11 update nightmare may actually be rooted in SSD firmware rather than Microsoft’s code. Since the release of the August 2025 update KB5063878, some users reported that their SSDs would suddenly vanish from File Explorer and even the BIOS, leaving PCs unable to detect the drives entirely. The reports quickly sparked speculation that Microsoft’s update had introduced a major compatibility bug. Yet last week, both Microsoft and Phison stated that they could not reproduce the issue and insisted the patch was not at fault.
Fresh insights from the enthusiast group PCDIY! suggest that the truth is a bit more complicated. According to their findings, the vanishing SSDs can be traced back to preliminary or engineering firmware versions running on some drives. These early-stage firmwares, which were never designed for end-user deployment, appear to have been triggered by the changes in KB5063878, leading to the storage failures. Phison engineers have since corroborated this explanation, confirming that tests showed affected SSDs were running firmware that was never intended for mass consumer release.
The discovery helps explain the confusion. In normal supply chains, SSDs with Phison controllers are flashed with stable, official firmware before being shipped out in bulk by manufacturers. Those firmwares undergo extensive testing to weed out anomalies, meaning the overwhelming majority of users are unaffected. However, drives that slipped into circulation with preliminary firmware—whether through unconventional distribution or early production runs—were vulnerable, and the Windows update was simply the trigger that exposed the problem.
For affected users, there’s now a potential fix: updating to the latest firmware from the SSD maker. But this step should be taken carefully, as firmware updates can sometimes wipe or corrupt data if something goes wrong. Experts recommend fully backing up your SSD before applying the update to avoid data loss. While frustrating, the silver lining is that the issue doesn’t appear to be widespread and doesn’t point to a fundamental flaw in Windows 11. Instead, it’s a reminder of how unfinished hardware software can cause unpredictable problems once it collides with a major OS update.