The latest security update for Windows 11 (KB5063878, corresponding to version 24H2) is causing serious headaches for users: under certain conditions, it can disable SSD drives, rendering entire partitions inaccessible and risking data loss.
The issue has been identified by the Japanese technical community NichePCGamer and is already circulating on forums like Reddit and X (formerly Twitter). Reports indicate that the error occurs during long, continuous write operations—such as loading 50 GB or more at once—after which some SSDs stop being recognized by the operating system. In more severe cases, even a reboot cannot recover them.
Affected SSDs and risk factors
Initial analyses suggest a correlation with models that include Phison controllers, especially Corsair Force MP600 (PS5012-E12), Kioxia Exceria Plus G4, Fikwot FN955, and SanDisk Extreme PRO. Incidents have also been reported with WD, Crucial, and ADATA units in similar environments.
The risk increases when the SSD has more than 60% usage and in models without dedicated DRAM memory—those that rely on the system RAM to manage cache.
In contrast, units like Samsung 980, 990 Pro, or Solidigm P44 Pro have not shown failures, indicating that the problem depends on specific firmware and architecture.
Microsoft remains silent
So far, Microsoft has not officially confirmed the fault. The only acknowledgment has been of another error stemming from the same update: code 0x80240069, related to deployments via WSUS/SCCM, which was fixed on August 14.
However, the lack of mention regarding the SSD failure is concerning for users, as this is a cumulative security patch. Uninstalling it could leave the system vulnerable, while keeping it active increases the risk of data corruption in sensitive environments.
Advice for users
In the absence of an official fix, recommendations from the technical community include:
- Avoid massive write operations (individual files or sets over 50 GB).
- Break up loads into smaller chunks to reduce write stress.
- Do not install the update on critical systems until Microsoft confirms and resolves the issue.
- As a last resort, uninstall KB5063878 / KB5062660, weighing the security risks involved.
A recurring pattern in Windows 11
This new setback adds to a list of recurring issues that have accompanied Windows 11 updates since its launch. While Microsoft insists on keeping systems up-to-date, incidents like this reinforce the perception among users that “updating blindly” can be as risky as not updating at all.
Meanwhile, these difficulties have reopened debates about dependence on the Windows ecosystem and have shifted focus toward alternatives like Linux, which offers increasing migration tools—including initiatives like Winux to facilitate smoother transitions.
Frequently Asked Questions (FAQ)
Are all SSDs affected by this failure?
No. It has been mainly identified in models with Phison controllers and no DRAM. Samsung and Solidigm appear unaffected.
What happens if I uninstall the KB5063878 update?
The issue disappears, but the system becomes vulnerable to security threats. It’s a risky decision that should be considered on a case-by-case basis.
Has Microsoft issued a patch to fix this?
As of now, no. They’ve acknowledged another installation issue (0x80240069) but have not confirmed the SSD problem.
Are there alternatives to Windows 11 to avoid such problems?
Yes. Many users consider migrating to Linux, which increasingly offers compatibility solutions for running Windows applications. Projects like Winux aim to make the transition smoother with fewer hurdles.