Microsoft has conducted a thorough investigation into reports of solid-state drive (SSD) and hard disk drive (HDD) failures following the August 2025 KB5063878 security update. The tech giant initially acknowledged the concerns raised by users, particularly those who experienced issues after installing the Windows 11 24H2 update. However, after extensive testing and collaboration with storage device partners, Microsoft has concluded that there is no direct link between the security update and the reported drive failures.
In a recent service alert, Microsoft stated, “After thorough investigation, we have found no connection between the August 2025 Windows security update and the types of hard drive failures reported on social media.” The company emphasized its commitment to monitoring user feedback and investigating any future reports that may arise.
Multiple hard drive models reportedly impacted
The issue first emerged among Japanese users, who reported SSD problems during intensive write operations, particularly when their drives were over 60% full. Affected users noted difficulties with various models, including the Corsair Force MP600, Maxio SSD, SanDisk Extreme Pro, and Kioxia Exceria Plus G4, among others that utilize InnoGrit and Phison controllers.
While some users found that their drives were accessible again after a simple restart, others faced persistent inaccessibility even after rebooting their systems. A representative from Phison, a NAND controller manufacturer, confirmed their collaboration with Microsoft to address the situation. “We understand the disruption this may have caused and promptly engaged industry stakeholders. At this time, the controllers that may have been affected are under review, and we are working with partners,” the spokesperson remarked.
In light of these developments, Microsoft has advised Windows 11 users with drives exceeding 60% capacity to exercise caution. Specifically, they should refrain from downloading, copying, or writing large files—particularly those in the tens of gigabytes—until the underlying cause of the issue is identified and resolved.
