Latest Windows 11 security patch might be breaking SSDs under heavy workloads — users report disappearing drives following file transfers, including some that cannot be recovered after a reboot
Some say continuous transfers exceeding 50GB can cause drives to vanish from the OS

Microsoft’s latest security update for Windows 11 is allegedly causing SSD failures during heavy file transfers. The issue was reported by X user Nekorusukii @Necoru_cat, who was updating Cyberpunk 2077 on a system running Windows 11 24H2 with the KB5063878 update installed, when the SSD on which the game was installed disappeared from the operating system.
An investigation by the user reveals a potential bug that appears during continuous file transfers on certain storage devices, particularly when the transfer exceeds 50GB and the drive is over 60% full. In these cases, the SSD can sometimes disappear from within the operating system. While restarting the PC makes the SSD visible again, the issue seems to occur again as soon as a large data transfer is performed again.
It was earlier reported that the issue lies within how SSDs handle cache, especially DRAM-less models equipped with Phison NAND controllers, but it turns out the problem isn't confined to those types of drives. A series of tests was carried out to establish the scope of the problem, which included copying Cyberpunk 2077's Steam library folder to the drive, preparing a compressed archive, and then copying the expanded archive into the target storage.
Out of the 21 drives tested, it was found that 12 of them became inaccessible, but only the Western Digital SA510 2TB could not be recovered even after a reboot. This indicates that the issue seems to impact SSDs with multiple types of SSD controllers.
Nekorusukii has listed the complete findings and explains that the SSDs were tested only on his own system, so the results may not offer enough proof on the real-time performance of these drives. Additionally, they do not assert that the Windows 11 24H2 KB5063878 or the previously released KB5062660 updates are directly responsible for the issues. However, a separate report by Japanese outlet NichePCGamer has further identified at least eight users on X who are facing similar issues on their respective drives.
According to a user with a SanDisk Extreme Pro M.2 NVMe 3D SSD, the drive became inaccessible after installing a 50GB update for Honkai: Star Rail. Although restarting the system resolved the issue, the user encountered it again on multiple occasions in August. Suspecting the KB5062660 update as the cause, the user deleted the update file, after which the problem no longer occurred.
By the looks of it, the issue doesn’t seem to be widespread. While we wait for Microsoft and SSD manufacturers to acknowledge the bug, it is best to stay cautious, especially if you are dealing with large continuous file transfers on systems running the latest Windows 11 KB5063878 update. We've reached out to Phison specifically regarding the issue, but the company wasn't immediately available for comment.
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
Follow Tom's Hardware on Google News to get our up-to-date news, analysis, and reviews in your feeds. Make sure to click the Follow button.

Kunal Khullar is a contributing writer at Tom’s Hardware. He is a long time technology journalist and reviewer specializing in PC components and peripherals, and welcomes any and every question around building a PC.
-
Alvar "Miles" Udell 50gb+ to a drive with a certain controller that has over 60% usage does sound niche as far as the number of Windows Insiders who would have it goes, but given the size of the Windows Insider program it's difficult to imagine this wasn't triggered before wide release, especially given the SK Hynix P41 Platinum is one of the best drives you can/could get for your money.Reply -
das_stig 50gb+ in corporate world is nothing if you're reimaging or those working with videos. and even if they aren't corporate drives are normally as cheap as the OEMs can make them so may be more volatile.Reply -
CrazyCarrot911 Just waiting for the thread where it says it entered server space, 50GB is peanuts when it comes to volume.Reply
Redmond, what have ya done again ??? -
HypnoLya I can say, the drive being filled up to 60% isn't a hard requirement. Just a few days ago, I was doing a swap from a 1TB 990 Pro (boot drive) to a 2TB 990 Pro, using EaseUS's clone software. First two times, it locked up the destination drive. It couldn't see the drive until I restarted.Reply
I thought it might have been thermal locking because the drive was getting insanely hot, even with a copper plate on it (at the time, it was in an external enclosure). Thinking it was a thermal problem, I got a new external enclosure, specifically getting a lower end one, with the idea that it would hopefully bottleneck the process and lower the temp of the SSD.
It ended up working, but now I'm wondering if it wasn't just because of this; and I got lucky on the third try. -
MoxNix
Backing up a drive might cause the problem.stuff and nonesense said:Only 3 things to say to this…
backup
BackUp
BACKUP
Now I have to wonder if that's what happened to a 512GB 2.5 inch Crucial MX500 SATA SSD that got bricked after I tried cloning a Windows install from another drive to it. Non recoverable, I can't even see the drive when booting into repair mode from a Windows install disk now. -
TechieTwo IMNHO these types of blatant O/S product defects should be actionable for all losses incurred.Reply -
hotaru251 yet another reason forced updates shouldnt be a thing. Should always have option to keep something how it is.Reply -
abufrejoval
Thankfully SSDs don't seem to die on me, so I never got to try this method myself, essentially a certain power cycle sequence: seems pretty safe to try on a drive you've given up as dead.MoxNix said:Backing up a drive might cause the problem.
Now I have to wonder if that's what happened to a 512GB 2.5 inch Crucial MX500 SATA SSD that got bricked after I tried cloning a Windows install from another drive to it. Non recoverable, I can't even see the drive when booting into repair mode from a Windows install disk now. -
Sluggotg I believe the most likely cause is overheating. Some people have cases with limited air flow around the SSDs. These high end M.2 drives need a heatsink and air flow across it. When it gets too hot during the file transfers it overheats and is no longer visible to Windows. They reboot, the drive cools off and can be accessed again. If it gets too hot, the drive is ruined and no longer usable even after reboot.Reply
Just a theory.