Windows 11 22H2: Microsoft confirms performance issues when copying files

Windows[German]Copying large files under Windows 11 22H2 can lead to a serious drop in speed. What was already known from user circles and described by individual Microsoft employees has now been officially confirmed by Microsoft. So far, there are only workarounds that Microsoft suggests to work around the problem. Below is an overview of where the problem occurs and what the user can do about it.


Currently, Windows 11 22H2, which was already released in September 2022 and has been distributed more widely in the meantime, cannot get out of the negative headlines. One problem concerns copying large files between cloud instances and local disks. The colleagues at Neowin already pointed out the tech community article Slower SMB read performance for large files in 22H2 by Ned Payle at the beginning of October 2022.

In that October 3, 2022 post, the Microsoft employee confirms that there can be a performance hit when copying large files from a remote computer to a Windows 11 computer or when copying files to a local drive. According to the article, file operations transferred via the SMB network protocol are affected.

The status of this issue is said to be available in the Microsoft 365 Admin Center under ID WI442499, if Windows Release Health is available there.

According to comments by Ned Pyle, the bug is located in the Windows 11 kernel version 22H2. The reason for the bug is the preview update KB5017389 from September 30, 2022, which is supposed to fix numerous bugs (see Windows 11: Preview-Update KB5017389 (Sept. 30, 2022)). In the meantime, Microsoft has confirmed the issue in the Know Issues section of the English-language version of the support article KB5017389:

Copying large multiple gigabyte (GB) files might take longer than expected to finish on Windows 11, version 22H2. You are more likely to experience this issue copying files to Windows 11, version 22H2 from a network share via Server Message Block (SMB) but local file copy might also be affected.Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.

Microsoft assumes that consumers in the home and users in small companies are probably not affected by this problem (such large files are not transferred there).

Workaround from Microsoft

According to Microsoft, the problem can be avoided by using robocopy and xcopy at the command prompt level. The reason is that these commands do not use a cache manager (buffered I/O). The copy operations could be performed using the following commands


robocopy \\someserver\someshare c:\somefolder somefile.img /J


xcopy \\someserver\someshare c:\somefolder /J

where the source and destination paths should be inserted. Microsoft is working on fixing this bug and plans to fix it with one of the upcoming updates for Windows 11 22H2.

Similar articles
Windows 11 2022 Update (22H2) released
Windows 11 22H2: Issues and upgrade stoppers
Windows 11: Printer driver confirmed as upgrade stopper (Sep 29, 2022)
Windows 11 22H2: Out-of-band update KB5019311 (Sept. 27, 2022)
Windows 11: Compatibility issues with Intel Smart Sound Technology
Windows 11: Preview-Update KB5017389 (Sept. 30, 2022)
Windows 11 strengthens SMB traffic protection
Windows 11 22H2 rollout in new phase
Windows 11 22H2: Provisioning packages may not work as expected
Windows 11 22H2: Microsoft investigates RDP issues
Windows 11: Microsoft helps to re-gain gaming performance

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Update, Windows and tagged , , . Bookmark the permalink.

3 Responses to Windows 11 22H2: Microsoft confirms performance issues when copying files

  1. EP says:

    copy files performance problem continues with the Nov. 8 KB5019980 update.
    so it's still not fixed even with KB5019980.

    though I recently saw this:

    that one seems to have a "CopyFile" bug fix but it might be a fix for a different copy files problem

Leave a Reply

Your email address will not be published. Required fields are marked *