[German]It is an issue that has been bothering users for months. There is a bug in Windows 11 22H2 that causes a serious speed drop when copying large files. Since December 2022 I have been hoping that this would be fixed with a patch. But now this bug is fixed with the lastest preview update, as I just found out.
The copy file performance bug
When copying large files under Windows 11 22H2, users have reported a serious speed drop – and individual Microsoft employees as well as Microsoft itself have also confirmed this (see also the blog post Windows 11 22H2: Microsoft confirms performance issues when copying file).
The long journey to the fix
There were indeed fixes in the File Copy area in the Insider Preview of November 28, 2022, which were also rolled out with the security updates (Patchday: Windows 11/Server 2022-Updates (December 13, 2022)) on December 13, 2022. But in the links to blog posts listed at the end of the article, it can be seen that the fix for the copy bug in the kernel has not been fixed yet.
The fix has now been addressed by Microsoft though, and has probably been built into Insider Preview build 22621.1343 for Windows 22H2. In the Windows Blog, the description Releasing Windows 11 Build 22621.1343 to the Release Preview Channel states:
We fixed an issue that affected copying from a network to a local drive. Copying was slower than expected for some users.
This Insider Preview already ranks as update KB5022913, which was then released on February 28, 2023 as a preview update for Windows 11 version 22H2 (see Windows 11 22H2: Preview Update KB5022913 (Feb. 28, 2023)). The reference to the fix for the file copy bug can be found there as well.
Microsoft confirms the fix
In the English-language blog, EP pointed out in this comment (thanks for that) that update KB5022913 includes the fix for slow copy performance. In the October 2022 Techcommunity post Slower SMB read performance for large files in 22H2, Neil Pyle pointed out in a March 6, 2023 update that the February 28, 2023—KB5022913 (OS Build 22621.1344) Preview – Microsoft Support update includes the kernel update to fix the problem. As of March 14, 2023, the fix will then be rolled out with the security updates in general.
Similar articles:
Windows 11: Preview-Update KB5017389 (Sept. 30, 2022)
Windows 11 22H2: Microsoft confirms performance issues when copying file
Windows 11 22H2: Fix for performance issues during copying files still not rolled out
Windows 11 22H2: Microsoft fix for file copy performance issues is coming
Windows 11 22H2: Moments 2 update KB5022913 brings many new features
Windows 11 22H2: Preview Update KB5022913 (Feb. 28, 2023)
Windows 11 22H2: Moments 2 update KB5022913 causes startup problems with third-party GUI tools
Windows 11: "Defender trouble" due to updates KB5022845 and KB5022913 (app startup hangs)
although the weird part about the KB5022913 update is that Microsoft still lists the "Copying large multiple gigabyte (GB) files might take longer than expected" problem in the "known issues" section of MS support article 5022913, even though MS seems to have "fixed" the copying problem.
seems as if Microsoft is contradicting themselves that way. maybe W11 22H2 users are better off waiting for and installing the next update come next Tuesday March 14
nope. I take this all back
it seems Microsoft did not completely or partially fixed the copy performance problem as some 22H2 users are still experiencing the problem, even with the KB5022913 & newer update installed.
heck, the newly released March 14 KB5023706 update still lists the copy problem in the "known issues" section (click on the known issues link to expand it) of MS article 5023706:
https://support.microsoft.com/help/5023706
follow up – it seems Microsoft has cleaned up the MS support articles from KB5022913, KB5023706 & newer updates either in late April 2023 or early May 2023 that no longer mentions the copy kernel problem in the known issues section.
the darn MS tech support folks who wrote those articles were just a few months late in recognizing the copy problem was really fixed starting with the KB5022913 update