Windows updates can add new features or fix previous operating system bugs, but they can also end up with new bugs that weren’t there before.
Users report that SSD read speeds have dropped drastically after the latest Windows 11 update (Windows 11 version 22H2 – KB5023706). While the few reported events were thought to be localized to the ADATA XPG SX8200 Pro 1TB SSD, the issue was found to affect other manufacturers and can be fixed after uninstalling the update or with a somewhat botched fix.
Windows slows down SSD
As reported by some media, this problem has started to occur after the Windows 11 update KB5023706. This affects the reading speed of SSDs, reducing it by half. If speed is precisely the most important characteristic of solid-state drives, by reducing this parameter, system performance drops significantly.
Windows 11 Moment 2 update has been released by Microsoft. This major update focuses on the integration of Bing Chat, based on GPT-4, in the user taskbar search. However, if we take a look at the list of known issues, performance loss on SSDs is included.
“Copying large multi-gigabyte (GB) files may take longer than expected to finish on Windows 11, version 22H2. You’re most likely to experience this issue when copying files to Windows 11, version 22H2 from a network share via Server Message Block (SMB), but local file copy might also be affected. be affected by this problem.
Only affects some models
According to early reports, the issue was related to the ADATA SSD, not other SSD models, although it has also now been reported on Team Group A440 Pro 2TB drives as well. Addressing Windows 11 issues with some SSDs, Microsoft states that “to mitigate this issue, you can use file copy tools that don’t use the cache (I/O buffer) manager.”
Also, they launch two command lines to fix the problem temporarily, while they create a final solution.
The commands that “fix” the problem are:
- robocopy someserversomeshare c:somefolder somefile.img /J
- xcopy someserversomeshare c:somefolder /J
The final solution should be a fix to the update file or wait until the next major update to see if it is no longer listed as a problem. Be that as it may, those affected are seeing very limited performance and we hope that it will be resolved as soon as possible.
