Recycle bin open from F8 context menu not work

[Hurdet]

When I try to use Context menu of the [F8 Delete] button Selecting "Open" it not show recycle Bin in Explorer but error: An outgoing call cannot be made since the application is dispatching an input-synchronous call.

[gdpr deleted 6]

Hmm, on my Win7 x64 box, it works both with the 32-bit and 64-bit versions of TC 9.51, and it works both for TC running with the normal restricted user account or running elevated.
It also works here in a Win10 x64 Pro VM, although it's just the rather old version 1809 (clean VM, no other 3rd-party apps or drivers aside from the VMWare tools and TC 9.51, of course).

I don't know, but might this perhaps be an issue with new(er) Win 10 versions?


A quick googling around suggests that the error message is related to calling into some COM object, but that little fun fact alone might not be tremendously helpful...

[petermad]

It works here with both 32bit and 64bit TC 9.51 under Windows XP, Windows 8.1, Windows 7 and Windows 10, 2004.

[Hurdet]

Not problem with Double Commander.

[Horst.Epp]

No problem here with TC x86 and x64

[ghisler(Author)]

Try opening the recycle bin within Total Commander instead:
cm_OpenRecycled

[Hurdet]

This opens it up inside TC. But why doesn't it work from F8?

[petermad]

2Hurdet

But why doesn't it work from F8?

Well it works for Horst.Epp and myself (I even testet on 4 different computers with 4 different OS's), so it is rather somthing on your system or your TC configuration. Have you tried with a clean wincmd.ini file?

[Hurdet]

Also with a clean wincmd.ini file in 2 different computers.

[gdpr deleted 6]

Try to find commonalities between your 2 computers with respect to:

- any 3rd-party software that is used on both computer (including software that has already been uninstalled prior to observing the issue, and which might have left some things in the OS messed up)
- any system tweaks/hacks that are applied in the same manner on both computers

While a sample size of 4 or 5 is not really statistically significant, it hints at something with your computers being different compared to any of the computers/VMs we used to try reproducing the issue. The big question is: What could it be? (I would almost suggest to do a new, clean installation of the OS, but restoring your work environment with your programs and settings could be a major PITA. So i leave it to you whether you want to apply this sledgehammer method just for the sake of trouble-shooting the F8 context menu...)

[Hurdet]

I found that depend on a software that use:
SetWindowsHookEx(WH_MOUSE_LL, yyy, xxx, NULL);
When I disable hook not have problem.

[Hurdet]

precisely:
problem is when I
SendMessage WM_RBUTTONDOWN and WM_RBUTTONUP
instead of SendInput.
Problem only on "open", not in other items (empty, add, ...).