FreeCommander Forum

Yes, and that is just the situation, when I click on it, I get error message "Application not found". But if the same context menu is called (by short right click) from the main window (left or right) showing list of drives, not from the drive bar, it works OK. Why?

If performed from WINDOW in FC with list of drives (This Computer), it works! But if performed from drives listed ABOVE THE WINDOW in FC, it does not work. What is difference in acces to context menu with these two cases? How can it be solved? Should I report it as a BUG?

I tried to run "FcContextMenu64.exe" manually, after it I can found this running in systray, but no change. Still unable to unlock a BitLocker-encrypted drive from FC. Any other ideas or solutions? Or experiences in other versions of Windows?

Thank you, but non of both ways works. In both cases the menu appears the same as in 32 bit versinon and the problem persist also. (Sorry if I made some mistakes in english.)

Attempt to unlock a BitLocker-encrypted drive from the context menu displays "Application not found".

The problem occurs only if the context menu is invoked from a FreeCommanderXE (portable version) - when called directly from Windows Explorer, everything is OK. I use Windows 10.