Microsoft has confirmed that the August 2025 Windows security update did not cause SSD failures or data corruption, despite user reports of issues during heavy write operations on drives over 60% full. The company is investigating the reports and working with storage partners to identify the root cause, advising affected users to avoid large file operations until resolved.
Phison conducted extensive testing on SSDs affected by Windows 11 updates KB5063878 and KB5062660 but was unable to reproduce the corruption issues reported by users. The company suggests that the problem may be on the user side, related to thermal management during sustained workloads, and recommends using heatsinks or heat spreaders to prevent potential damage.
Recent Windows 11 updates (KB5063878 and KB5062660) are causing data corruption and SSD failures, especially on drives with Phison NAND controllers, prompting Microsoft and Phison to work on a fix. Users are advised to avoid large, rapid file writes until the issue is resolved.
The latest Windows 11 24H2 update has caused storage failures, especially during heavy write operations on SSDs and HDDs, leading to drive disappearance and potential data corruption, with certain NAND controllers and HDDs being more affected. Microsoft has addressed some installation errors, but the storage issues remain a concern for affected users.
Players of Modern Warfare 3 and Warzone have been encountering the Niamey Logan error, which informs them that their data is corrupt. However, developers have assured players that their rank, unlocks, and purchases are not lost, although loadouts, customization, and certain settings may be reset. Clicking "Yes" to reset is safe, and Activision is aware of the issue and working on a fix.
The Linux kernel has received a patch to mitigate the "Zenbleed" vulnerability affecting older AMD CPUs, which manifests as a data corruption issue when executing VZEROUPPER under certain microarchitectural conditions. While the Linux kernel patch provides a mitigation, the most effective solution is to run the latest AMD processor microcode. The vulnerability was discovered by Tavis Ormandy from Google Information Security.
