Take it with a salt rash, as Microsoft has not officially confirmed the issue at this point. According to reports, which originated from the Japanese website Top PC GamerThe latest security update for Windows 11 is causing issues for some users.
here are the details:
- The issue occurs after the establishment of KB5063878 or KB5062660.
- The KB5063878 Windows 11 is the final security update for version 24h2 which was released by Microsoft on this month’s patch day.
- The KB50626660 update is a preview update, which was released at the end of Microsoft July 2025
- The problem can affect the system with solid state drives (SSD) if A) A large number of files or B) a large single file is written on the drive.
- In the worst condition the drive becomes inaccessible.
One of the first users to report this issue was X-Ruser Necoru_CatThe user noticed that this problem occurred when updating the game Cyberpank 2077 after the latest security update to Windows 11 version 24h2 on the system.
The drive on which the cyberpank was installed on 2077 became inaccessible as a result. The user said that writing 50 consecutive gigabyte files to SDD with a use rate of at least 60 percent caused the issue. However, the solid state drive will reopened after a restart and will be re -recognized. Writing a large amount of data on the drive will cause problems again according to the user. In addition, niche PC gamer notes, some SSD may not be re -available even after reboots.
The top PC gamer conducted tests to learn more about the issue. According to the report, the following SSDs are influenced by this issue:
- CORSAIR Force MP600
- PHSON PS5012-E12 SSD with controller
- Kioxia Exceria Plus G4
- Fnmt fn955
- With SSD Innogrit controller
- Maxio SSD
- Kioxia M.2 SSD
- Sandisk Extreme Pro M.2 Nvme 3 D SSD
According to the following drive tests appear unaffected by this issue:
- Solidigm P44 Pro
- Samsung 980
- Sandisk SSD Plus 240GB SDSSDA-240G
The X-user also conducted the tests and made a list of affected and unaffected SSDs.
Here are SSDs that were found to be affected by this issue:
- WD Blue SN5000 2TB Nvme
- WD Red SA500 2TB SATA
- WD BLUE SA570 1TB Sata M.2 (restarted to recover)
- WD Blue SA510 2TB SATA (inaccessible, not restored even after reboot)
- CORSAIR Mp510 960GB Nvme
- CORSAIR Mp600 2TB NVMMME (Return to recover)
- SK HYNix Platinum P41 Nvme
- Important P3 Plus NVMME (restarted to recover)
- Adata Legend 800 2TB NVMMME (Restarted to recover)
- HP FX7000 2TB NVMMME (Return to recover)
- XPG SX8200 Pro 2TB NVMMME (Restarted to recover)
- Hanye He70 2TB NVMMME (Return to recover)
And here are SSDs that were not affected:
- Samsung 990 for 2TB Nvme
- Samsung 980 for 2TB Nvme
- Samsung 870 Evo 1 TB Sata
- WD Black SN7100 2TB Nvme
- WD Blue SA510 1TB Sata M.2
- Seagate FC530 2TB Nvme
- Seagate FC530 1TB Nvme
- Solidigm P44 Pro NVME
- Important T700 2TB Nvme
Microsoft has not officially responded to claims at this point. If you run a system with one of the SSDs that appear to be affected by the problem, you want to be very careful after the installation of the update, or even postpon the installation until more information is available.
Thanks for reading..
