![\"Windows](\"https:\/\/www.newsbeep.com\/ca\/wp-content\/uploads\/2025\/08\/1755474368_830_960x0.jpg\")
<\/p>\n<\/p>\n
More bad news for Windows 11 users.<\/p>\n
NurPhoto via Getty Images<\/p>\n
Microsoft has already confirmed<\/a> that its latest Windows 11 update \u201cmight fail to install<\/a>,\u201d with an emergency update already released. Not a good look for a mandatory security update. But now a new report suggests an even nastier surprise for some users.<\/p>\n First picked up by WccfTech<\/a>, August\u2019s update appears to \u201ccause several SSD failures,\u201d with the drives becoming \u201cnon-functional after a large data write.\u201d It seems \u201cstorage drives reportedly malfunction while large files are being written to them at once.\u201d<\/p>\n The initial report came courtesy of @Necoru_cat who posted on X<\/a> that \u201cdrives disappear from the OS (SMART data also becomes unreadable); in some cases, access to the buffered tree is possible, but files cannot be read.\u201d This seems to be a \u201csuspected issue with the operation of the drive cache\u201d with a \u201chigh likelihood of file corruption.\u201d<\/p>\n ForbesMicrosoft\u2019s Emergency Update For Windows Users\u2014\u2018Critical Issues\u2019By Zak Doffman<\/a><\/p>\n Unsurprisingly, it\u2019s not yet clear how widespread an issue this is, and while the list of drives suspected to be vulnerable is currently limited, it\u2019s unlikely that many users are rushing to test their own SSDs with a large file write to see if they fail.<\/p>\n @Necoru_cat\u2019s testing suggests \u201cSSDs with over 60% usage after approximately 50GB of continuous writing\u201d are affected, with \u201csimilar symptoms on HDDs as well. Our tests suggest that Phison NAND controllers are relatively prone to issues, with DRAM-less models from the same company tending to exhibit issues at lower write volumes.\u201d<\/p>\n Microsoft has not commented as yet \u2014 although I heave reached out to see if there\u2019s any confirmation on the reports and guidance for users. Past history suggests we\u2019ll see an annotation in the update report once this has been fleshed out.<\/p>\n It\u2019s not dissimilar to the latest emergency update, which fixed what Windows Latest<\/a> described as a \u201cheadache\u201d for users, lamenting that it was some time after the website \u201cflagged critical issues\u201d before \u201cMicrosoft finally acknowledged our report.\u201d<\/p>\n WccfTech says SSDs thought to be affected by the update failure are as follows:<\/p>\n Corsair Force MP600 The site says \u201cthe problem is likely from a storage driver or kernel-level regression that came with the update, which mishandles long sequential writes, ultimately leading to controller lock-up, which makes the drive disappear and is not recognizable by the OS.\u201d<\/p>\n Until there is any official word from Microsoft through official channels on the issue and the fix, users are advised \u201dto avoid long sequential write instances, especially if their drive is on the above-mentioned list\u201d or has \u201ca Phison controller onboard.\u201d<\/p>\n
\n Phison PS5012-E12 controller-equipped SSD
\n KIOXIA EXCERIA PLUS G4
\n Fikwot FN955
\n SanDisk Extreme PRO M.2 NVMe 3D SSD
\nForbesMicrosoft Confirms \u2018Last Update\u2019 For 700 Million Windows UsersBy Zak Doffman<\/a><\/p>\n