unable to unlock a BitLocker-encrypted drive

[kolo]

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.

[joby_toss]

Maybe the problem is that you're using XE 32 bit on win 10 64 bit.
Try holding the Win logo key while right clicking, to invoke the 64 bit context menu or use the ShowContextMenu64Bit=1 string if you prefer to see for right click always 64-bit context menu (details here).

[kolo]

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.)

[kolo]

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?

[kolo]

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?

[joby_toss]

I don't have windows 10 to test, but in XE you can long right click the drive buttons in the drive bar to access the context menu.

Here it is in my win 7:

[kolo]

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?

[joby_toss]

Hmm, you're right:



It is a bug (context menu invoked from the drive bar is always 32 bit) and I hope Marek can find a solution for this.
For others reading this: using XE 64 bit works fine.