Windows 11 24H2 Update Causing SSD Failures: Full Guide

One of the main problems following the update in Windows 11 24H2 is that these users face strange behavior while they are copying or installing a large amount of data. The rare case is the issue that appears while moving files larger than 50 GB or updating big games that download tens of gigabytes at once.

This is what usually occurs:

• File Explorer either slows down or gets stuck in the middle of the transfer.
• A notice pops up mentioning the drive in the error message.
• Without any warning, the SSD disappears from Windows and at times it is not even recognizable in the BIOS.
• Rebooting the system may give the drive back but the files that were being copied are most probably gone.
• In the worst scenarios, the drive never returns and it stops working permanently.

• Large video files, heavy games, or backups are especially at risk of being damaged due to this update.
• Just a single transfer might often be enough to cause the error.

In this sense, the update becomes particularly harmful for users who work with such files. One export only could be sufficient for the issue to appear.

Which Drives Are at Risk?

It is not so that each and every solid-state drive is susceptible to the problem, but a considerable number of researches have highlighted those Phison-controlled drives to be the most affected. They are the controlling units in the SSDs that decide how the data is to be saved and, conversely, how it is to be read. They are very typical of reasonably priced consumer SSDs.

We are aware of reports that the August Windows 11 update may be causing issues with certain storage devices. Our teams are actively investigating the matter in collaboration with hardware partners to identify the root cause and deliver a fix as soon as possible.

         Microsoft spokesperson

Difficulties have been encountered with these drives:

• Western Digital Blue SN5000 and Blue SA510 (the SA510 very often doesn’t recover at all)
• Corsair Force MP510 / MP600
• SK hynix Platinum P41 (generally returns after reboot)
• ADATA Legend 800
• HP FX7000
• XPG SX8200 Pro
• Kioxia Exceria Plus G4
• SanDisk Extreme Pro M.2 3D

In an independent test of 21 different SSD models, 12 of them failed to pass the stress test combined with this Windows update. The majority of the affected drives came back after rebooting the PC, however, one (the WD SA510) was exception – it remained broken forever.

Additionally, a few reports have come in regarding hard drives (HDDs) which have indicated similar failure symptoms, but the main risk is still to be found in SSDs.

Surprisingly, the issue with drives based on Phison technology does not seem to affect those from Samsung or Seagate that are using different controller units because of which they are not in the scope of the bug.

Why Is This Happening?

Learning how Windows 11 manages write caching post-August update has lead the most to connect this problem to the new method.

By default when copying files, Windows breaks the data into smaller portions and sends each part one after the other to the SSD. The SSD is equipped with a small, fast buffer (mostly known as an SLC cache) aimed at making the writes a smooth procedure. Should the storage become full, Windows is expected to ease his pace and wait for the SSD to be ready for the next portion.

Unfortunately, it seems that the recent update has caused a situation where Windows is sending excessive data while the rate is not slowed down. If the buffer on the drive is weak or too small, the controller of the SSD is being overwhelmed by the data. The drive is thus malfunctioning in one of the following ways:

• It loses power for a short time and is invisible to the system until the device is rebooted.
• Or, in more severe situations, it totally freezes and ruins the stored data, hence, the drive cannot be used anymore.

Now, this is the reason for the failures most of the time occurring during the very large transfers and why certain SSDs with smaller or older controllers are more susceptible to this issue.

Microsoft’s Response

Currently, there is no official fix from Microsoft yet. Nevertheless, they said to the media that they have read all the reports and are already working with the hardware vendors to locate the problem.

Among others, the bug has been connected to:

• Windows 11 24H2 (Build 26100.4946) with KB5063878 (launched August 12, 2025).
• The prior preview update KB5062660 (July 2025) may have a little impact too.

Removing KB5063878 may prevent the bug from occurring, but it definitely will not recover lost data nor hardware that has already been damaged.

What SSD Makers Are Saying

Phison, the one responsible for the controllers in many of the SSDs that are affected, is acknowledging the issue. They have given a declaration that they are cooperating with Microsoft and other manufacturers to do more testing and support with the firmware if necessary.

The problem is that Phison does not provide the new version of the firmware directly to the customers. Rather, it is the manufacturer of the SSD (e.g. WD, Corsair, ADATA, etc.) that issues the update, and it is then the customers who get it. The time it will take to update the software varies from brand to brand, and not all drives may be getting a fixed version of the software.

Besides that, other companies producing SSD haven’t made public announcements yet, however, as soon as the data is available, more of them are likely to say so.

What You Should Do Now

If you updated your PC manually, or the update was installed on your PC automatically without your intervention, here are some steps that you can follow to avoid major problems and protect your files:

Pause Windows Updates

• First, try to stop the updates if possible and wait until Microsoft confirms a solution. It will halter the installation of KB5063878 if the update has not been done yet.

Avoid Large Transfers

• Do not transfer (move or copy) files that are larger than 50 GB at one time.
• Moreover, if you are forced to do so, cut up the transfer into smaller parts and rest for a while each time before resuming.

Backup Your Data

• Extract the files which matter the most to you from the PC and store them on other mediums such as SSD, HDD or a cloud service.
• Implement the 3-2-1 rule: Have 3 copies of data, store them on 2 different types of media, and keep 1 in a location that is physically different or has a different access route (e.g., cloud).

Restart if Issues Happen

• In case your SSD disappears, do not hesitate to restart your PC immediately. Most drives, in general, will reappear although the files that were being worked on might get lost.

Watch for Updates from Your SSD Brand

• Pay attention to the official support websites of brands like WD, Corsair, ADATA, etc. They may bring out firmware fixes in the coming weeks.

Final Thoughts

The Windows 11 24H2 storage bug is maybe the most impactful update issue that you have heard about in years since it messes up the whole storage part of the system that is totally user-dependent.

Though there are a lot of uninfected SSDs, the possibility of data corruption and eventual drive failure is, therefore, an issue that raises concern over the safety of users’ data. The most securing actions to take before permanent solutions will be released by Microsoft and SSD manufacturers are as follows:

• Pause updates if possible.
• Do not directly duplicate huge files.Make dependable backups of the essential data.It is a fact that a data loss can be very stressful. So, it is the best way to protect yourself by taking the necessary precautions beforehand.
• Do not directly duplicate huge files.
• Make dependable backups of the essential data.