Good morning all,
Using the latest beta on Windows 10 x64 (1809). I have a VHDX that is Bitlockered. In XY, I can right-click the VHDX and mount it successfully; however, when I try to unlock it using the non-x64 context menu :
I get this message :
Please note, that if I choose "Show 64-bit Context Menu" and choose Unlock from there, it works. Is this because the x86 context menu cannot find/use manage-bde.exe ? or something else ?
If I use the same context menu in Explorer :
I get the unlock/password prompt and can continue :
Issue Unlocking Bitlocker Drive
-
- Site Admin
- Posts: 60357
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Issue Unlocking Bitlocker Drive
The context menu is fed by the registry. If the "Unlock drive..." command appears in the 32-bit menu but does not do anything then the application has been incorrectly registered regarding this entry. In theory you can fix it (= remove that useless command) by editing the registry... but you have to know what you do.
FAQ | XY News RSS | XY Twitter
Re: Issue Unlocking Bitlocker Drive
Hello again,
Using ShellMenuView from Nirsoft (and manually searching the Registry), there is only 1 option for "Unlock Drive". If I disable this menu option, it disappears from both the 32 and 64bit context menus. The filename and command for this entry is C:\Windows\System32\bdeunlock.exe - which is present on the machine.
It would seem that this single menu entry is used on both context menus; however, fails on the 32bit only. Any updated ideas as to why I would get the "Application not found" when the file does in fact exist ?
Using ShellMenuView from Nirsoft (and manually searching the Registry), there is only 1 option for "Unlock Drive". If I disable this menu option, it disappears from both the 32 and 64bit context menus. The filename and command for this entry is C:\Windows\System32\bdeunlock.exe - which is present on the machine.
It would seem that this single menu entry is used on both context menus; however, fails on the 32bit only. Any updated ideas as to why I would get the "Application not found" when the file does in fact exist ?
-
- Site Admin
- Posts: 60357
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Issue Unlocking Bitlocker Drive
The path "C:\Windows\System32" is ambiguous. It points to C:\Windows\SysWOW64 in 32-bit processes. A design decision that has and will haunt the world for a long time.
FAQ | XY News RSS | XY Twitter