Page 1 of 1
Entry missing from context menu
Posted: 09 Nov 2022 09:24
by kiwichick
I've just installed IObit Unlocker. Why doesn't it show up in either of the context menus (standard and 64-bit)? It's there in Windows Explorer. Is it usual behaviour for some entries to not appear in XY's context menus?
Re: Entry missing from context menu
Posted: 09 Nov 2022 09:52
by highend
Re: Entry missing from context menu
Posted: 09 Nov 2022 10:14
by kiwichick
Thanks for that. I don't think I'll use the custom context entry because I want to have the interface. However, I have a CTB to open the current folder in Windows Explorer, so I'll just use that and work on the file/folder from there. But do you happen to know why it's missing?
Re: Entry missing from context menu
Posted: 29 Aug 2023 15:34
by xyMario
Thank you for this! Unfortunately after using it now every folder I click using regular File Explorer seems to activate IOBit unlocker instead of opening it, so I had to remove this. If I could get it to work just with xyplorer it may be usable.
I would also like to know why this and other apps do not show in the context menu of XYplorer but do with other similar programs. I am evaluating this and this lack of integration is a big drawback for me. Maybe a deal-breaker. I do like the program otherwise. It would be great to be able to bring up the menu.
What is a CTB? If I could use a work around it may help.
Any help would be greatly appreciated!

Re: Entry missing from context menu
Posted: 29 Aug 2023 15:38
by highend
To remove the registry changes from the other thread, just remove the two keys?
Code: Select all
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\shell\IObit Unlocker (Own)]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\IObit Unlocker (Own)]
If it still fails you've done something else, these two entries shouldn't conflict with the original ones.
Uninstall and reinstall the software...
Custom
Toolbar
Button
Re: Entry missing from context menu
Posted: 29 Aug 2023 16:19
by admin
Over here the IObit Unlocker entry is featured in the extended 64-bit shell context menu. Hold SHIFT while opening the menu to show the extended menu.
Re: Entry missing from context menu
Posted: 29 Aug 2023 18:07
by xyMario
Thank you both. These solutions worked! Your help is much appreciated!

Re: Entry missing from context menu
Posted: 03 Sep 2023 01:53
by kiwichick
admin wrote: ↑29 Aug 2023 16:19
Over here the IObit Unlocker entry is featured in the
extended 64-bit shell context menu. Hold SHIFT while opening the menu to show the extended menu.
On my PC I don't see IObit Unlocker in the 64-bit menu. I also don't get the 64-bit menu when holding Shift.
Re: Entry missing from context menu
Posted: 03 Sep 2023 09:32
by admin
How do you open 64-bit menu?
Re: Entry missing from context menu
Posted: 05 Sep 2023 06:56
by kiwichick
admin wrote: ↑03 Sep 2023 09:32
How do you open 64-bit menu?
Hold Shift while right-clicking a file. I also use the standard context menu entry which says to show to 64-bit menu. Neither way has an entry for IObit Unlocker. Have I misunderstood something and that's not the "extended 64-bit shell context menu"?
Re: Entry missing from context menu
Posted: 05 Sep 2023 10:08
by admin
Two ways to show the extended 64-bit shell context menu:
1) Check Configuration | Other | Shell Integration | 64-bit Windows | Show the 64-bit context menu, then hold SHIFT while right-clicking a file.
2) Uncheck Configuration | Other | Shell Integration | 64-bit Windows | Show the 64-bit context menu, then right-click a file, then hold SHIFT while clicking "Show 64-bit context menu".
Re: Entry missing from context menu
Posted: 06 Sep 2023 02:33
by kiwichick
admin wrote: ↑05 Sep 2023 10:08
2) Uncheck
Configuration | Other | Shell Integration | 64-bit Windows | Show the 64-bit context menu, then right-click a file, then hold SHIFT while clicking "Show 64-bit context menu".
Thanks Don, totally my fault. I was having a brain fart and holding Shift while right-clicking a file to bring up the menu then letting Shift go while clicking "Show 64-bit context menu". Got it sorted now.