7 min read
7 min read

Microsoft’s latest Windows 11 update, part of the August 2025 Patch Tuesday rollout, has introduced serious concerns among users. Many are reporting drive failures following the installation of update KB5063878.
This issue affects both SSDs and HDDs under certain usage conditions. Although not every system is impacted, reports suggest specific patterns. The situation is being closely monitored by users, tech forums, and vendors.
Microsoft says it has investigated user reports but has found no evidence linking the update to drive failures. However, the company continues to monitor feedback.

The update in question is KB5063878, released on August 12, 2025. It was intended to address several security vulnerabilities in Windows 11 systems. However, shortly after release, users began reporting issues related to disappearing or corrupted storage drives.
While the update has been generally stable in many systems, a subset of users has experienced severe data loss. This has prompted increased scrutiny from the tech community. Microsoft has since updated its documentation and support responses.

Numerous users have taken to forums and social media to report sudden drive failures. In most cases, these occurred shortly after installing the KB5063878 update. Reports include inaccessible partitions, failed boot drives, and data corruption.
While it is not a universal issue, the failures are consistent enough to raise an alarm. Affected users have found that system restore or drive formatting does not resolve the issue. The growing number of cases has led to deeper investigation by hardware vendors.

One independent tester, Nekorusukii, reported failures during file transfers over 50 GB or with drives more than 60 percent full. This points to a correlation between write intensity and vulnerability.
Some drives disappeared entirely from the operating system while in use. After a reboot, the drive may be partially visible or permanently inaccessible. This behavior has been confirmed through repeated testing by independent reviewers.

Many affected drives use Phison-based SSD controllers. Phison is a common manufacturer of NAND flash controllers used in a wide range of SSD models. The correlation does not imply all Phison SSDs are impacted, but a pattern has emerged.
This includes models from Kingston, Gigabyte, and others using Phison E16 or E18 controllers. Analysts suggest the problem may lie in how the Windows update interacts with these specific controller firmware settings.
Initial speculation focused on Phison‑based SSD controllers, but after extensive testing, Phison reported no failures and said its hardware was not at fault.

The issue is not limited to Phison-based drives. Users have reported failures on SanDisk Extreme Pro, Corsair MP600, and WD Blue models.
There are anecdotal mentions of other brands (e.g., SanDisk, Corsair, WD), but these lack verification, and Microsoft has not corroborated widespread failures across different models.

In one test, a 2 TB Western Digital SA510 drive became permanently unreadable. The drive failed after a single large file transfer on a system running the updated Windows version. Attempts to recover or reformat the drive failed.
Other drives tested under the same conditions remained intact but showed signs of degradation. The unrecoverable drive suggests the potential for complete data loss under certain triggers. WD has not yet released a formal statement on this case.

Not all affected drives fail in the same way. Some drives disappear from Windows Disk Management and later reappear after a full shutdown. Others remain hidden or corrupted permanently. Users report intermittent recognition of drives that may function for a time before failing again.
This inconsistency makes troubleshooting difficult. Some drives display SMART errors, while others show no warnings before failing. The inconsistent behavior suggests a complex underlying issue.

Experts suspect multiple contributing factors may be at play. Some believe the Windows cache manager is handling large write operations improperly. Others point to potential memory leaks or improper flush commands to SSDs.
Drive firmware may also be misinterpreting queued commands under the updated kernel. These errors may result in sudden loss of drive mapping or file system corruption. No single fix has yet been identified due to the complexity of affected systems.

Although SSDs are most commonly affected, a small number of hard disk drive failures have been reported. HDD users have noted similar symptoms, including drive disappearance and corrupted data. The failures mostly occur during backup or disk-intensive tasks.
This indicates the issue may extend beyond SSD controller firmware. Traditional drives may be impacted by the same storage stack bugs in Windows. Microsoft has not ruled out HDD vulnerabilities in its ongoing analysis.

Microsoft has acknowledged reports of drive issues related to KB5063878. The company is collaborating with drive manufacturers and OEM partners to identify the cause. So far, Microsoft has not released a public hotfix or patch.
Affected users are encouraged to submit feedback through Windows Feedback Hub. Microsoft has not recommended uninstalling the update at this stage. However, it is expected that a corrective update may be issued in the near future.

Experts recommend avoiding large file transfers until a solution is available. Transferring multiple gigabytes of data could trigger the bug in certain systems. If backup is necessary, users should split transfers into smaller batches.
Avoid exceeding 60 percent disk capacity where possible. Power cycling and drive reallocation may temporarily fix visibility issues. Users should stay updated via official Microsoft or vendor support pages.

All users running the affected Windows 11 update should back up important data immediately. Cloud backups and external storage drives are recommended. Users with Phison SSDs or other known affected models should be especially cautious.
Delaying backup may lead to unrecoverable data loss. Professional recovery services may be required if the drive becomes unreadable. Preventative action now can minimize future risk.

If your system has not yet installed the KB5063878 update, consider delaying it. Users on update hold or enterprise deployment schedules may wish to wait for a stable patch. For those already affected, rolling back the update may provide temporary stability.
Instructions for updating rollback are available on the Microsoft support site. Delaying installation allows time for a verified resolution. Microsoft has not mandated an emergency rollback, but has not discouraged it either.
Windows Security faces trust issues after the latest update. Explore: Can you trust Windows Security after this update?

Until a formal fix is released, users are advised to monitor system behavior carefully. Avoid unnecessary disk stress or performance benchmarks. Stay subscribed to Microsoft’s release notes for future updates. Watch for firmware updates from your SSD manufacturer.
Users may receive a future cumulative patch or hotfix addressing the issue. A coordinated response from both Microsoft and hardware vendors is expected.
Ready for what’s next in Windows 11? Explore why Microsoft works on the new Windows 11 update.
Have you experienced any drive-related issues after installing the August 2025 Windows 11 update? Share your thoughts.
Read More From This Brand:
Don’t forget to follow us for more exclusive content right here on MSN.
This slideshow was made with AI assistance and human editing.
This content is exclusive for our subscribers.
Get instant FREE access to ALL of our articles.
Dan Mitchell has been in the computer industry for more than 25 years, getting started with computers at age 7 on an Apple II.
We appreciate you taking the time to share your feedback about this page with us.
Whether it's praise for something good, or ideas to improve something that
isn't quite right, we're excited to hear from you.
Stay up to date on all the latest tech, computing and smarter living. 100% FREE
Unsubscribe at any time. We hate spam too, don't worry.

Lucky you! This thread is empty,
which means you've got dibs on the first comment.
Go for it!