Following the publication of the cumulative Security updates KB5063878 for Windows 11 in August 2025 Reports of serious SSD problems Users from all over the world reported that their solid-state drives (SSDs) suddenly became unreadable or even disappeared completely from the system after installing the update. This disturbing phenomenon, which in some cases led to irretrievable data loss, puzzled the technology community. The search for the cause led to Microsoft and the SSD manufacturers, but the truth turned out to be far more complex than simply assigning blame.
The symptoms: From blue screen to invisibility
The symptoms described in the user reports were severe. The primary problem was the sudden disappearance of the storage device from the system. Affected users often experienced a blue screen, followed by a reboot, during which the drive was no longer recognized in the Windows file system or Device Manager, and in the most severe cases, even in the system's UEFI or BIOS.
The problems typically occurred under specific conditions:
- Sustained, large writes: The error often occurred when transferring large amounts of data of over 50 GB, for example when installing games or unpacking large archives.
- High capacity utilization: Many reports indicated that the problems primarily occurred on drives that were already over 60% to 80% full.
The search for the cause
The initial suspicion immediately fell on the Windows 11 update itself. Uninstalling the updates KB5063878 and KB5062660 was able to resolve the issue for some users. Nevertheless, both Microsoft and SSD controller manufacturer Phison denied finding a direct connection between the updates and the failures. Neither company was able to reproduce the problem in their extensive internal testing. This discrepancy suggested that the Windows update merely uncovered a deeper hardware flaw.
Latest findings: A firmware bug as the true cause
The latest and most well-founded findings come from a Chinese PC enthusiast group called PCDIY, whose tests were verified by Phison engineers. According to the report, the problems were not caused by a bug in the Windows Update itself, but by an unfortunate combination of the update and unofficial, Pre-release firmware on certain SSDs.
The affected drives were running with so-called “Engineering firmware", which is used for internal testing and validation purposes before mass production. These builds may contain bugs that were fixed in the final version. The theory is that a small number of these drives may have been released with this faulty firmware for unknown reasons. The case is therefore a chain of events. The Windows update changed communication with the SSD controller, which, combined with the faulty firmware, caused the drive to crash under heavy load.
Affected SSD manufacturers and models
Based on the reports and community tests, a list of potentially affected SSDs has been compiled. It is important to emphasize that this list is unofficial and likely only affects certain batches or firmware versions. Most reports focus on drives with Phison controllers, but there were also reports of models with controllers from InnoGrit and Maxio.
Overview of affected SSD manufacturers and models
The following table shows all currently discussed models based on community reports.
Important: Most problems only occurred with certain firmware versions.
| Production | Reported models | Remark |
|---|---|---|
| Needle | SP580 | Reported with SSD issues. |
| Corsair | Force MP600, MP510 | Several reports of problems with these models. |
| Crucial | P2 series | Reports of compatibility issues. |
| Fikwot | FN955 | Reports of failures with this model. |
| KIOXIA | Exceria Plus G4 | Affected models mentioned in user reports. |
| Kingston | NVMe SSDs | Individual reports of problems. |
| SanDisk | Extreme Pro M.2 NVMe 3D | Problems reported with this model. |
| Samsung | 990 Pro | Possible confusion with a previous firmware bug. |
| Western Digital | WD Blue SA510 2TB, WD Blue | In one case completely unreadable. |
🛠 Solutions & recommendations for those affected
First aid for a failed SSD:
-
Uninstall updates: KB5063878 & KB5062660
-
Check SSD externally (via USB enclosure)
-
BIOS reset and test alternative ports
-
Read firmware version & contact manufacturer
Long-term protection:
-
Only use firmware from the manufacturer (no pre-release)
-
Pay attention to the firmware version when purchasing an SSD
-
Regular backups to cloud or external media
❓ FAQs about SSD issues after KB5063878
1. Is the update KB5063878 dangerous for my SSD?
Only in rare cases with faulty firmware – but caution is still advised.
2. Which SSDs are affected?
Especially models with older Phison, InnoGrit or Maxio controllers.
3. How can I find out if my SSD has faulty firmware?
Tools like CrystalDiskInfo or manufacturer support can help.
4. Is my data lost?
Not necessarily – professional data recovery is often possible.
Conclusion: SSD problems
The SSD failures following the KB5063878 update aren't a simple Microsoft bug, but rather the result of an interaction between the software update and unofficial SSD firmware. Those affected should take immediate action—and rely on tested firmware, good backup strategies, and up-to-date system images for the future.
| Transparency: | This article may contain affiliate links. These lead directly to the provider. If a purchase is made through this, we receive a commission. There are no additional costs for you! These links help us to refinance the operation of win-tipps-tweaks.de. |
See also the article
Windows 11 24H2: The August Update KB5063878 – everything you need to know at a glance
___________________________________________________
This tip comes from www.win-tipps-tweaks.de
© Copyright Michael Hille
Warning:
Using Registry Editor or its tips incorrectly can cause serious system problems that may require you to reinstall your operating system. Tampering with the registry files and using the tips is at your own risk.
