Win 11 update might break ssds - probably won't effect most people or just a hyped up thing

[burger1]

https://www.techpowerup.com/340032/micr ... d-failures

Microsoft issued a Defender security update as part of the August 2025 Patch Tuesday cycle to counter the Lumma stealer and similar malware and exploits. The Windows 11 24H2 cumulative package KB5063878 was included in that rollout. Early deployments returned an installation error, 0x80240069, which Microsoft acknowledged and later addressed. Community testing has since identified a reproducible pattern in which certain SSDs, when running sustained sequential writes of approximately 50 GB, become inaccessible and display unreadable SMART telemetry. Follow-up analysis and vendor feedback to date primarily point to solid-state drives, although conclusions about traditional spinning hard disk drives remain unconfirmed.

[Gavrushka]

That's a little bit scary. - A little bit of extra detail from my best friend.

The Windows 11 24H2 cumulative update KB5063878, released on August 12, 2025, has been linked in community reports to issues that could potentially harm SSDs, particularly NVMe SSDs, under specific conditions. Here’s a concise breakdown based on available information:Potential RisksStorage Instability: Community reports indicate that KB5063878 can cause certain NVMe SSDs to become inaccessible or "disappear" from the operating system during sustained, heavy write operations (typically ~50 GB or more, especially on drives with over 60% utilization). This can lead to unreadable SMART data and, in some cases, file system corruption or data loss.

Affected Drives: The issue primarily affects SSDs with Phison controllers (e.g., Corsair Force MP600, Kioxia Exceria Plus G4) and some DRAM-less models, though other controllers like those in WD SN770 and Blue SN5000 have also been reported. Some enterprise-grade HDDs may show similar issues, but this is less confirmed.

Symptoms: Drives may stop responding, vanish from Device Manager, or show corrupted files after heavy writes. A reboot may temporarily restore access, but the issue can recur under similar workloads, increasing the risk of permanent data loss.

Likely CauseThe problem is speculated to stem from a regression in Windows 11’s cache memory management or Host Memory Buffer (HMB) interactions, particularly with certain SSD controllers. This can cause controllers to lock up or fail during intense write operations, potentially leading to data corruption. However, Microsoft has not officially confirmed a direct link between KB5063878 and permanent SSD damage as of August 18, 2025.

What You Should DoTo minimize the risk to your SSD:Pause or Delay the Update: If you haven’t installed KB5063878, consider delaying it until Microsoft or SSD vendors release a fix or clarification, especially if you use an NVMe SSD or perform large file transfers (e.g., game updates, backups).

Back Up Data: Ensure you have up-to-date backups of critical data to external drives or cloud storage before performing heavy write operations.

Monitor Drive Health: Use tools like CrystalDiskInfo or vendor-specific software to check your SSD’s health and SMART data if you’ve already installed the update. Stop heavy write operations if you notice instability.

Check for Firmware Updates: Visit your SSD manufacturer’s website for firmware updates, as these have resolved similar issues in the past.

Uninstall if Necessary: If you’ve installed KB5063878 and experience issues, you can uninstall it using the DISM Remove-Package command (not via standard uninstall methods). Follow Microsoft’s guidance for safe removal.

Monitor Official Channels: Check Microsoft’s support page (https://support.microsoft.com/help/5063878) or your SSD vendor’s advisories for updates or patches.

Current StatusAs of August 18, 2025, Microsoft has not officially acknowledged the storage issue as a "known issue" on the KB5063878 support page, and no definitive patch has been released. The issue appears to affect a subset of users with specific hardware and workloads, so not all systems are impacted. Community reports and enthusiast testing (e.g., by Japanese tester NichePCGamer) have been consistent, but the overall prevalence is unclear without vendor telemetry.

ConclusionWhile KB5063878 does not universally "harm" SSDs, it poses a risk of data loss or drive instability under heavy write conditions, particularly for certain NVMe SSDs. Exercise caution by backing up data, avoiding large file transfers, and monitoring for fixes. If you rely on critical data or use a potentially affected SSD (e.g., Phison-based), consider delaying the update or uninstalling it until Microsoft or your SSD vendor provides a resolution.For the latest updates, check Microsoft’s support page or your SSD vendor’s website

[burger1]

Jayztwocents made a video. Has a roll back instruction section. Instructions at 7 minutes 40 seconds in the video.

https://www.youtube.com/watch?v=mlY2QjP_-9s

[burger1]

New jayztwocents video with new issues on new drives.

https://www.youtube.com/watch?v=TbFIUu_7LIc

[Alan Phipps]

Also it seems that a recent Win11 optional update may be messing with legacy X3/X2 game RGB displays: see here.