What happens? You get op up window saying "The source and destination file names are the same.". So what is the problem?

Apparently nothing wrong if I click OK of the X icon of the pop up. But if I ignore it and click somewhere else in FC, then that popup window is send back behind FC in terms of focus. And so if I now select some other file and press CTRL + C, that other file will not be copied to the Windows' clipboard. I can select that file and use the OS shell menu to copy it and paste it in some other software or on a desktop- but I will not be able to paste it with CTRL + V in FC. Also I will not be able to successively execute other shortcuts like CTRl + M, because instead of getting to the Multi Rename, my selected files will be sent to my docked at the top Winamp [be it 5.666 or 5.8]. And it is not the fault of Winamp, because that blockade happens also when it is not running [and so CTRL + M will do nothing]. And this has been happening since I can remember

To fix this I need to minimize and / or move FC enough so that I can see that pop up window- and close it. Or just close and reopen FC, which is quicker and more convenient for me

So I propose that such pop up window should:

A] close itself automatically if not OK-ed or X-ed

B] appear also as an icon on a taskbar, so that the user will know that something is affecting FC

C] re-appear every time a shortcut will be pressed, so that the user will know why it cannot be executed successfully

I am using FreeCommander XE 2018 Build 770 32-bit public and this was happening on Windows 7 x64 and now is happening on Windows 10 in the exact matter- with the exception of solluton B being apparently already implemented

It looks just some (or all?) hotkeys are blocked, while that dialog is opened, in background, e.g. Tab, F2, F12, Ctrl+C, Ctrl+V, when using the context menu or toolbar buttons, it works good.

EDIT: I just found, that dialog block also the feature drag&drop link in web browser, so perhaps it's a Windows issue/limitation, at least partly, so I'm not sure if it's possible to fix it in FC. Anyway, it's a really strange issue.

@ Forez - your suggestion "B] appear also as an icon on a taskbar, so that the user will know that something is affecting FC"
This is already imlpemented. The FC icon changes as soon as more than one FC window is open.

as for creating an icon on the taskbar for every FC window opened, I would prefer not, then the taskbar would be cluttered, messy.

Secondly, while the window with warning message was in the background, I was able to continue using FC, i.e. used shortcut strg+m and renamed several files.

@ Forez - your suggestion "B] appear also as an icon on a taskbar, so that the user will know that something is affecting FC"
This is already imlpemented. The FC icon changes as soon as more than one FC window is open.
[...]

Yes I noticed that in Windows 10 at a last moment and adjusted the end of my initial post. However on Windows 7 I did not see any kind of indication- but that was maybe because of the tweaks I made to my system [and I also no longer have an access to that system configuration to check it out]

as for creating an icon on the taskbar for every FC window opened, I would prefer not, then the taskbar would be cluttered, messy.
[...]

Well currently I do get a separate FC icon for it on the Taskbar, as I tweaked the rules concerning grouping on it. I am OK with that, because It is unlikely that I will miss an additional FC icon on- and every such icon tells me that something should probably be taken care off

made possible for me to execute CTRL + M in a proper way in such situation

So what is behind the idea of having the ability to select that- thus block such shortcuts? A fail safe in form of an indication that something is wrong? If yes then it is a poor one, as it took me a lot of time to figure it out [especially taking into consideration that until recently I did not get extra FC icons on my Taskbar]

If this setting is checked, the file transfer (copy or move) is made synchronously, with the result that the FreeCommander window is blocked while the operation is in progress. If this setting is not checked, the transfer operation is done in the background (asynchronously) and working in the FreeCommander window can be continued.

Some programs or devices support only synchronous operations. In that case this setting should be checked.

If the CTRL key is pressed when starting the drag operation, the opposite option will apply.

If this setting is checked (synchronously operations) and a very large file should be copied with drag&drop, by pressing the CTRL key the copying can be done asynchronously.