Version 15.4 Build 3089 on Windows 24H2 Build 26100.3915

[TanMan]

I recently updated to Version 15.4 Build 3089 and everything was fine. Then a few days ago, I updated Windows to 24H2 Build 26100.3915. Before this, using Ctrl-C and Ctrl-V did a File Explorer file copy, showing the file copy progress window. Since this Windows update, the copy still happens, but no copy progress window is shown. Doing a copy using File Explorer does show the progress window, but no window appears using Multi Commander.

FYI, I use Ctrl-C and Ctrl-V since it's significantly faster than using Multi-Commander Copy.

[Mathias (Author)]

I don't know why Ctrl+V stop showing that. Might be a windows bug. MC has no control over that at all. When you do "paste" MC just tell windows to "paste" the clipbard content into path X. Then Windows does the rest.
So if Ctrl+V does not show a progress dlg for large files, Try reboot. Else there is some issue with Windows, anyway MC has no control over the WIndows Shell progress dialog at all.

* Normally mc is faster. but a lot of things affect speed, also Windows does not show real time. It say it done when it has written to the cache, Not everything might be actually written to drive yet. When MC say it is done when data is actually completed the write to the disk and cache are flushed.
But there should be not much different. They all read and write the files in the same way. Not many ways to do that. But a lot of things affect copy speed. specially some security software do extra hard check for write from 3rd party program. and more relaxed when it is done from Windows own process. Many many things affect speed and it is also very hard to actually get the correct way to actually time it correctly since some say they are done when the last write to the file have completed. When actually the data is not written to disk yet. but still is in the cache waiting to be written to disk

[TanMan]

Ok. Thanks. It's definitely something with File Explorer, but I haven't been able to figure it out yet. Probably something with Visual Studio Community which I have installed, but I haven't identified it yet.