bug with file operations after latest windows 11 update

Question

bug with file operations after latest windows 11 update

nikos 10

I am the developer of xplorer2 <Removed>, a file manager like windows file explorer, and I want to report a windows BUG that affects my program.

since the latest windows 11 update (10.0-26100.4061) my program will not show the file copy progress window, a feature that works in all versions from windows 95 and up. The situation is quite technical to explain, so I will try to be succinct

no matter how I initiate the file copy (clipboard copy/paste, drag-drop, even using IFileOperation shell interface), the file is copied but without any visual feedback (the above progress window is missing). I will include some C++ code how am I handling a file paste operation:

IDataObject* source = OleGetClipboard(); 
IDropTarget* target = IShellFolder::GetUIObjectOf(IID_IDropTarget); 
target->DragEnter(source, MK_LBUTTON | MK_CONTROL, POINT(0,0), DROPEFFECT_COPY); 
target->Drop(source, MK_CONTROL, (0,0), &effect); 
// copy works but no progress dialog is shown

I don't think the particular parameters used in this code block are relevant, as other parts of the program that SHOULD show a file progress indicator, do not show it either

please forward this to someone of the windows shell (file explorer) team for consideration

thank you in advance

Nikos Bozinis

PS. some people see the copy progress window only the first time they copy a file with xplorer2, then it goes silent from the 2nd file operation and for the duration of the program run

Reply

nikos 10 Reputation points

2025-05-26T06:33:36.8866667+00:00

it also happens when plain SHFileOperation API is used to copy files, first time it shows progress, then nothing!
Viorel 122.1K Reputation points

2025-05-26T13:53:54.0666667+00:00

In order to lessen unscientific empiricism, perhaps you should provide a sample Visual Studio project that reproduces the problem (which only needs manual adjustments of paths), and details such as the size of copied files, whether SHFileOperation is used to copy a single file or a group of files, whether the progress window appears in other instances of the program or File Explorer, etc.

nikos 10

It is quite easy to reproduce, create a dialog based MFC application, make the dialog a drop target ("accept files" = TRUE), then use this as a WM_DROPFILES handler below

the first time you drag-drop a file, you will see a progress copying it into TEMP folder. The second time you see nothing.

void CshfileopDlg::OnDropFiles(HDROP hDropInfo)
{
	WCHAR buf[MAX_PATH] = {0}
	DragQueryFile(hDropInfo, 0, buf, MAX_PATH); // just get the first one
	DragFinish(hDropInfo);
	//MessageBox(buf);

	SHFILEOPSTRUCT fop = {0};
	fop.hwnd = m_hWnd;
   fop.wFunc = FO_COPY;
   fop.pFrom = buf;
	buf[lstrlen(buf)+1] = 0;
	WCHAR temp[MAX_PATH];
	ExpandEnvironmentStrings(L"%TEMP%", temp, MAX_PATH);
   fop.pTo = temp;
   fop.fFlags = FOF_ALLOWUNDO;
	int res = SHFileOperation(&fop);

	CDialogEx::OnDropFiles(hDropInfo);
}

Viorel 122.1K Reputation points

2025-05-28T12:33:07.29+00:00
To work around the problem, try to use the IFileOperation temporarily with FOFX_ADDUNDORECORD | FOFX_NOMINIMIZEBOX flags.

It seems that the issue needs a direct support, or at least a report via Feedback Hub.

Regarding the UI differences:

https://developercommunity.visualstudio.com/t/After-applying-KB5055627-the-display-co/10896323
Leanterface 10 Reputation points

2025-05-30T03:39:56.74+00:00

Developer of OneCommander file manager here - many users report the same issue in the past several days. Can't find any recent update in common with users that report the same issue. Microsoft should fix it ASAP!
Marek 0 Reputation points

2025-06-01T12:27:06.86+00:00

I am developer of the FreeCommander file manager - the same problem reported by multiple users. I updated my Windows 11 PC to version 24H2 Build 26100.4061 a few days ago. Until yesterday, I couldn't reproduce the problem. The progress dialog was always there during the copy process. Suddenly, today, the behavior is as described by many users. After starting the program, the progress dialog is visible during the first copy, but it disappears afterward, but the operation is performed.

A fix from Microsoft would be appreciated by many users.
Marek 0 Reputation points

2025-06-01T15:52:12.8133333+00:00

Using the operation flag FOFX_NOMINIMIZEBOX with IFileOperation brings back progress dialog, however with old UI:
Leanterface 10 Reputation points

2025-06-07T15:22:05.83+00:00

I have created .NET 8 version that reproduces the issue:
https://github.com/m1l/WindowsOperationsBroken

I can't reproduce it myself but a few users who can have confirmed that the behavior is the same - showing dialogs the first time only
John Kennedy 0 Reputation points

2025-06-10T15:53:23.76+00:00

Just a lay user. Same problem with Q-Dir explorer. Shows the progress bar once if I'm lucky and then nothing. Just updated Windows 11 to the latest and greatest as of 6/10/25 and no chenge. Frustrating and obvious that it is not the problem of the software developers.

John
Reinhard 0 Reputation points

2025-06-11T13:19:10.6666667+00:00

Developer of FileBot here. My users have reported the same issue. The IFileOperation dialog either doesn't show up at all, or only once and then never again, even though operations are performed as if FOF_SILENT was set. I can notably reproduce the issue on my Win 11 machine. My users report that everything worked fine until some recent Win 11 update, and the same release works normally on Win 10 machines.
John Kennedy 0 Reputation points

2025-06-11T19:01:43.18+00:00

Friends,

Have to apologize for being vague in my report. My experience with coding is limited to a few lines of Morse Code I learned as a Boy Scout, so not much help here other than sharing surface level symptoms. I did find one anomaly worth mentioning.

Two computers with Win 11 Home. Both updated with the latest cumulative packages as of 6/11/25

First computer is a Dell Victus gaming PC with win 11 home version 24H2, 10.0.26100, build 26100. Latest cumulative update is KB5063060.

Q-Dir explorer still doing the same thing. Inconsistent presentation of the progress bar on fresh launch. Sometimes shows the progress bar and sometimes not. Consistent that the second and subsequent attempts within a session to transfer does not show the bar. The transfer itself goes on properly, only no visual indication of when it is completed.

Second computer, Dell Inspiron laptop with Win 11 Home ver 23H2, 10.0.22631 build 22631. KB506099 cumulative update.

Q-Dir works in this computer. Progress bars consistent across multiple transfers. Shorter files around 200k don’t show the process bar, but larger GB size folders do show the transfer progress. The computer is fast, so lack of progress bars for smaller files that appear almost instantly may be normal behavior.

So it looks like win 11 version 24H2 is broken whereas ver 23H2 is not.

Hope somebody at MS can fix this soon.

John
Niraj Yadav 0 Reputation points

2025-06-13T17:57:08.62+00:00

So, as a user of Nikos' Xplorer² FM as well as OneCommander FM, which is also experiencing this issue, the OC dev has pinpointed it down to a couple of Windows Updates that might be the culprit:

I think I found the culprit for missing copy/move progress dialogs

KB5060842

Upgraded one Windows 10 PC to Windows 11; OC dialogs work, Windows says there is an update KB5060842 available; I install it and after restart dialogs are broken. Went into

Settings > Windows Update > Update history > Uninstall updates

and uninstalled that update and the dialogs show up again.

Anyone else had that update installed recently?

and

Also caused by KB5063060. Uninstalling that one fixes the issue

With a linked YT video showing the fix.

https://www.youtube.com/watch?v=r4fq6T4JrM4

Both of those show as Cumulative updates, so it may take some doing to get them uninstalled.
Viorel 122.1K Reputation points

2025-06-13T18:59:37.6733333+00:00

Perhaps the manufacturer is not yet aware about the defect or undocumented changes in usage, and should be informed by the involved developers using dedicated channels.

1 answer

Your answer

nikos 10 Reputation points

2025-05-26T06:33:36.8866667+00:00

it also happens when plain SHFileOperation API is used to copy files, first time it shows progress, then nothing!
Viorel 122.1K Reputation points

2025-05-26T13:53:54.0666667+00:00

In order to lessen unscientific empiricism, perhaps you should provide a sample Visual Studio project that reproduces the problem (which only needs manual adjustments of paths), and details such as the size of copied files, whether SHFileOperation is used to copy a single file or a group of files, whether the progress window appears in other instances of the program or File Explorer, etc.
nikos 10 Reputation points

2025-05-27T11:51:15.8166667+00:00

It is quite easy to reproduce, create a dialog based MFC application, make the dialog a drop target ("accept files" = TRUE), then use this as a WM_DROPFILES handler below

the first time you drag-drop a file, you will see a progress copying it into TEMP folder. The second time you see nothing.

void CshfileopDlg::OnDropFiles(HDROP hDropInfo) { WCHAR buf[MAX_PATH] = {0} DragQueryFile(hDropInfo, 0, buf, MAX_PATH); // just get the first one DragFinish(hDropInfo); //MessageBox(buf); SHFILEOPSTRUCT fop = {0}; fop.hwnd = m_hWnd; fop.wFunc = FO_COPY; fop.pFrom = buf; buf[lstrlen(buf)+1] = 0; WCHAR temp[MAX_PATH]; ExpandEnvironmentStrings(L"%TEMP%", temp, MAX_PATH); fop.pTo = temp; fop.fFlags = FOF_ALLOWUNDO; int res = SHFileOperation(&fop); CDialogEx::OnDropFiles(hDropInfo); }
Viorel 122.1K Reputation points

2025-05-28T12:33:07.29+00:00

To work around the problem, try to use the IFileOperation temporarily with FOFX_ADDUNDORECORD | FOFX_NOMINIMIZEBOX flags.

It seems that the issue needs a direct support, or at least a report via Feedback Hub.

Regarding the UI differences:

https://developercommunity.visualstudio.com/t/After-applying-KB5055627-the-display-co/10896323
Leanterface 10 Reputation points

2025-05-30T03:39:56.74+00:00

Developer of OneCommander file manager here - many users report the same issue in the past several days. Can't find any recent update in common with users that report the same issue. Microsoft should fix it ASAP!
Marek 0 Reputation points

2025-06-01T12:27:06.86+00:00

I am developer of the FreeCommander file manager - the same problem reported by multiple users. I updated my Windows 11 PC to version 24H2 Build 26100.4061 a few days ago. Until yesterday, I couldn't reproduce the problem. The progress dialog was always there during the copy process. Suddenly, today, the behavior is as described by many users. After starting the program, the progress dialog is visible during the first copy, but it disappears afterward, but the operation is performed.

A fix from Microsoft would be appreciated by many users.
Marek 0 Reputation points

2025-06-01T15:52:12.8133333+00:00

Using the operation flag FOFX_NOMINIMIZEBOX with IFileOperation brings back progress dialog, however with old UI:
Leanterface 10 Reputation points

2025-06-07T15:22:05.83+00:00

I have created .NET 8 version that reproduces the issue:
https://github.com/m1l/WindowsOperationsBroken

I can't reproduce it myself but a few users who can have confirmed that the behavior is the same - showing dialogs the first time only
John Kennedy 0 Reputation points

2025-06-10T15:53:23.76+00:00

Just a lay user. Same problem with Q-Dir explorer. Shows the progress bar once if I'm lucky and then nothing. Just updated Windows 11 to the latest and greatest as of 6/10/25 and no chenge. Frustrating and obvious that it is not the problem of the software developers.

John
Reinhard 0 Reputation points

2025-06-11T13:19:10.6666667+00:00

Developer of FileBot here. My users have reported the same issue. The IFileOperation dialog either doesn't show up at all, or only once and then never again, even though operations are performed as if FOF_SILENT was set. I can notably reproduce the issue on my Win 11 machine. My users report that everything worked fine until some recent Win 11 update, and the same release works normally on Win 10 machines.
John Kennedy 0 Reputation points

2025-06-11T19:01:43.18+00:00

Friends,

Have to apologize for being vague in my report. My experience with coding is limited to a few lines of Morse Code I learned as a Boy Scout, so not much help here other than sharing surface level symptoms. I did find one anomaly worth mentioning.

Two computers with Win 11 Home. Both updated with the latest cumulative packages as of 6/11/25

First computer is a Dell Victus gaming PC with win 11 home version 24H2, 10.0.26100, build 26100. Latest cumulative update is KB5063060.

Q-Dir explorer still doing the same thing. Inconsistent presentation of the progress bar on fresh launch. Sometimes shows the progress bar and sometimes not. Consistent that the second and subsequent attempts within a session to transfer does not show the bar. The transfer itself goes on properly, only no visual indication of when it is completed.

Second computer, Dell Inspiron laptop with Win 11 Home ver 23H2, 10.0.22631 build 22631. KB506099 cumulative update.

Q-Dir works in this computer. Progress bars consistent across multiple transfers. Shorter files around 200k don’t show the process bar, but larger GB size folders do show the transfer progress. The computer is fast, so lack of progress bars for smaller files that appear almost instantly may be normal behavior.

So it looks like win 11 version 24H2 is broken whereas ver 23H2 is not.

Hope somebody at MS can fix this soon.

John
Niraj Yadav 0 Reputation points

2025-06-13T17:57:08.62+00:00

So, as a user of Nikos' Xplorer² FM as well as OneCommander FM, which is also experiencing this issue, the OC dev has pinpointed it down to a couple of Windows Updates that might be the culprit:

I think I found the culprit for missing copy/move progress dialogs

KB5060842

Upgraded one Windows 10 PC to Windows 11; OC dialogs work, Windows says there is an update KB5060842 available; I install it and after restart dialogs are broken. Went into

Settings > Windows Update > Update history > Uninstall updates

and uninstalled that update and the dialogs show up again.

Anyone else had that update installed recently?

and

Also caused by KB5063060. Uninstalling that one fixes the issue

With a linked YT video showing the fix.

https://www.youtube.com/watch?v=r4fq6T4JrM4

Both of those show as Cumulative updates, so it may take some doing to get them uninstalled.
Viorel 122.1K Reputation points

2025-06-13T18:59:37.6733333+00:00

Perhaps the manufacturer is not yet aware about the defect or undocumented changes in usage, and should be informed by the involved developers using dedicated channels.

Answer 1

Here's a breakdown of the situation and what you can do, based on your report and similar discussions:

Understanding the Problem:

Regression: The core issue is that the file copy progress window, which previously worked reliably across Windows versions using standard shell interfaces (like IDataObject, IDropTarget, IFileOperation, and even SHFileOperation), is now either not appearing at all or only appearing for the first operation in Windows 11 build 10.0-26100.4061.
Affects multiple interfaces: The fact that it impacts various methods of initiating file operations (clipboard, drag-drop, IFileOperation, SHFileOperation) suggests a deeper issue within the Windows shell's handling of these operations, rather than a specific bug in how xplorer2 calls one particular API.
"Silent" behavior: The observation that it acts "as if FOF_SILENT was used" after the first operation is a strong clue, suggesting that something in the shell's internal state might be incorrectly suppressing the UI.
Not unique to xplorer2: Other users of custom file managers (like One Commander, based on search results) have reported similar issues with missing file transfer progress windows after Windows updates, further supporting the idea that this is a Windows bug.

Why this is difficult to "resolve" directly as a user/developer (without Microsoft):

This isn't typically something an end-user or even a third-party developer can "fix" with a simple workaround. The progress window is handled by the Windows Shell itself, and if the shell isn't triggering it correctly, there's no readily available API for a third-party application to force it.

What you should do (and have already done effectively):

Report to Microsoft (You've done this, excellent!): Your post on the Microsoft Learn platform (formerly Microsoft Answers) is the correct channel. It's crucial to report these regressions directly to Microsoft, as they are the only ones who can patch the underlying operating system.
- Provide a minimal reproducible example: As suggested by others in the Microsoft thread, providing a simple Visual Studio project that demonstrates the issue (e.g., the MFC dialog example you mentioned) is invaluable for Microsoft's engineers to debug. The more easily they can reproduce it, the faster they can investigate and fix it.
- Keep the thread updated: If you find any further clues or other users report similar issues, update your Microsoft thread.
Encourage other affected users to report: The more users who report the same problem through official Microsoft channels (Feedback Hub, Microsoft Learn), the higher the priority it will receive.

Possible (temporary/diagnostic) workarounds or checks for users:

While you wait for Microsoft to address the bug, here are some things users experiencing this might try, though these are more general troubleshooting steps and less likely to directly "fix" a confirmed OS bug:

Restart Explorer: Sometimes restarting the Windows Explorer process (via Task Manager) can temporarily resolve display glitches. However, based on your report, this might only work for the first copy operation after the restart.
Check for further Windows Updates: Microsoft rolls out cumulative updates frequently. It's possible a future update might include a fix for this. Ensure Windows Update is set to automatically download and install updates.
System File Checker (SFC) and DISM: These tools can sometimes fix corrupted system files. While unlikely to directly fix an API regression, it's a standard troubleshooting step.
- Open Command Prompt as Administrator.
- Run sfc /scannow
- Run DISM.exe /Online /Cleanup-image /Scanhealth
- Run DISM.exe /Online /Cleanup-image /Restorehealth
Temporarily switch back to Windows File Explorer: If the lack of progress feedback is critical, users might need to temporarily switch back to the built-in File Explorer for large file operations until the bug is resolved in Windows.
Rebuild Search Index (less likely, but reported to help with some Explorer issues): Some users have reported that rebuilding the Windows Search Index can resolve seemingly unrelated Explorer issues.
- Go to Control Panel > Indexing Options.
- Click "Advanced" > "Rebuild".

Key takeaway for you as a developer:

You've identified a genuine operating system bug. Continue to provide as much detail as possible to Microsoft and encourage other users to report it. There's no specific code change you can make in xplorer2 to force the shell to display the progress dialog if the underlying shell API itself is misbehaving due to a Windows update.

It's a frustrating situation, but your proactive reporting is the best way to get it resolved by Microsoft.

Leanterface 10 Reputation points

2025-06-14T03:08:56.93+00:00

Culprit is KB5063060 - Tested on 5 PCs in college where I work (test before updating, after updating, and after uninstalling the update)

https://youtu.be/r4fq6T4JrM4

On 2 machines that didn't get that update but were still broken, I the culprit was KB5060842 and after uninstalling it the dialogs were back

Share via

bug with file operations after latest windows 11 update

1 answer

Your answer