Cutting files with CTRL+X sometimes doesn't make files grayed-out (transparent)

A longer while ago I noticed that cutting files using the CTRL+X hotkey doesn't always make files grayed-out or transparent to signal that they're being cut.

It usually happens when I'm pressing CTRL+X too fast, or when the CTRL key is released a few milliseconds before X is pressed. Another possibility is that it doesn't work when the file was just selected with the left mouse click, but I still didn't recognize exact problem cause.

It's possibly my wrong habit in pressing keys (releasing CTRL too fast), but e.g. Windows Explorer handles these things better, and still cuts files when X is pressed shortly after CTRL.

I'm still not 100% sure if that's the case, because sometimes it just doesn't gray-out files even when CTRL+X is pressed for a longer while. It seems very random to me.

I am wondering if someone noticed the same thing, or it's just my keyboard?

I suppose a different combination of preferences, but I've NEVER seen a file become become grayed-out due to pressing CTRL+X.

I'm not the least bit familiar with Explorer but I just tried and couldn't make it happen there either.

Is the problem only that the files aren't greyed out, or is it that they aren't cut at all?

E.g. If you sometimes release Ctrl before you push X, it won't cut the files.

If it's not because of that, the most likely culprit is something which monitors the clipboard or changes how it works and which isn't always forwarding events properly, so the cut event happens but isn't seen by the Opus window.

Unfortunately, I think this also works randomly. Sometimes CTRL+V in another folder pastes the "cut" file, sometimes it doesn't when it wasn't grayed out.

I noticed the following method to reproduce it faster:

  • Details files view.
  • Some .zip and other files in the folder.
  • Select file with the Left mouse button, then quickly press CTRL+X.
  • Select one file above (or one file below the previously selected one), and CTRL+X again.
  • Switch back to the previously selected file, CTRL+X, again switch to the same file as before, CTRL+X, and so on 20+ times.

Sometimes a new file doesn't become grayed-out on CTRL+X press, even though the previously cut file becomes non-grayed-out again. So it makes all files non-grayed, but doesn't mark a new cut file.

I know it's confusing when being described by text. I noticed the same behavior using a different device (laptop with touchpad instead of the mouse). A bit strange but it feels like some events are being missed in the window.

I find that some functions just don't work in certain folders. I have a folder where ctrl+x, ctrl+c, del, or alt+enter don't work. The buttons corresponding to these functions are also grayed-out in the toolbar. But if I copy the content in the folder to another location, these functions work well again.

Which folders have the problem?

Are they similar in File Explorer?

File Explorer doesn't have this issue. One of such folders is one created by running New-Item -Path . -Name "foldername" -ItemType "directory" -Force as my current user. Another is created when decompressing an .rar file using winrar.

edit: Resetting Dopus configs solves this, but the issue reappears after restoring backups.

If the problem seems tied to configuration, it must be a setting that’s changed from the defaults, or a script that’s installed maybe, but I can’t think of any that would do that,

Another thing to check is that Opus isn’t being launched elevated via UAC, as that can block notifications from reaching it.

Other tools which monitor the clipboard can also prevent clipboard notifications reaching apps that were started before them, if they don’t forward the notifications correctly.