Context menu is missing a lot of apps (in comparison to Win File Explorer).
46 views
Skip to first unread message
bill boro
Sep 25, 2026, 10:17:41 PMSep 25
to OneCommander
Why?
OneCommander Support
Sep 25, 2026, 10:17:59 PMSep 25
to OneCommander
OneCommander Support
Sep 26, 2026, 6:20:39 PMSep 26
to OneCommander
Fresh install of both of these in blank sandbox and they do show up.
bill boro
Sep 26, 2026, 10:10:24 PMSep 26
to OneCommander
I do install apps in sandbox ONLY if testing. Those 2 and many more apps are working just fine and even by re-installing them (in normal way) still don't show up in your context menu. Not like in MS File explorer. I believe it is your apps fault and not the process of installation.
Can you point to the cause why your app not like the other file explorers?
I have degree in EE and decades of working experience in CSci both R&D and troubleshooting. Thx
OneCommander Support
Sep 27, 2026, 11:16:55 AMSep 27
to OneCommander
Have you tried installing both OneCommander and WinRAR in a clean Windows Sandbox and checking the context menu there?
If they work together in Sandbox (same version as you currently have), as they do in my testing, that is important because it shows that OneCommander and WinRAR are compatible with each other and that something specific to your Windows installation or shell-extension configuration is causing the difference.
OneCommander doesn't discover WinRAR or other context-menu applications itself. At the relevant point it essentially just asks Windows for the context menu for the selected file:
var hr = menu.QueryContextMenu(hMenu,0,1,0x7FFF,Shell32.CMF.CMF_NORMAL);
Windows and the registered shell extensions then determine which menu items are returned and OC just shows them in its own menu style.
There are several reasons the result can differ on a particular system. A security product or shell-extension manager can selectively prevent an extension from loading in OneCommander while allowing it in Explorer. Running OC elevated can also affect some extensions. There can also be different 32/64-bit COM registrations.
However, since you say that **many** context-menu extensions are missing, I'd first test for a conflicting/broken shell extension. One badly behaving context-menu extension can interfere with enumeration of extensions that follow it.
Could you please try the following?
Download **ShellExView**:
https://www.nirsoft.net/utils/shexview.html
Use **"Download ShellExView for x64"** near the bottom of the page.
Then:
1. Run ShellExView.
2. Select **Options → Hide All Microsoft Extensions**.
3. Click the **Type** column to sort by type.
4. Find the entries whose Type is **Context Menu**.
5. Disable a few non-Microsoft Context Menu extensions at a time, then right-click the **same file** in OneCommander again (no need to close OC between tests).
6. If the missing context-menu items now appear, re-enable the extensions in groups until they disappear again. This will identify the extension interfering with enumeration.
You don't need to test 20 extensions individually. Disable approximately half, test OC, then enable/disable half of that group depending on the result. Repeating this should narrow it down to the problematic extension in only a few tests.
Some shell extensions that have caused OneCommander context-menu problems in the past include Fast Explorer, File Renamer Turbo, Tim by QQ, ACDSee PicaView, HoneyView, GeoSetter, and Cairo, although another extension could certainly be responsible on your system.
Please let me know whether OC + WinRAR work together in Windows Sandbox, and, if disabling any particular non-Microsoft Context Menu extensions fixes it
If they work together in Sandbox (same version as you currently have), as they do in my testing, that is important because it shows that OneCommander and WinRAR are compatible with each other and that something specific to your Windows installation or shell-extension configuration is causing the difference.
OneCommander doesn't discover WinRAR or other context-menu applications itself. At the relevant point it essentially just asks Windows for the context menu for the selected file:
var hr = menu.QueryContextMenu(hMenu,0,1,0x7FFF,Shell32.CMF.CMF_NORMAL);
Windows and the registered shell extensions then determine which menu items are returned and OC just shows them in its own menu style.
There are several reasons the result can differ on a particular system. A security product or shell-extension manager can selectively prevent an extension from loading in OneCommander while allowing it in Explorer. Running OC elevated can also affect some extensions. There can also be different 32/64-bit COM registrations.
However, since you say that **many** context-menu extensions are missing, I'd first test for a conflicting/broken shell extension. One badly behaving context-menu extension can interfere with enumeration of extensions that follow it.
Could you please try the following?
Download **ShellExView**:
https://www.nirsoft.net/utils/shexview.html
Use **"Download ShellExView for x64"** near the bottom of the page.
Then:
1. Run ShellExView.
2. Select **Options → Hide All Microsoft Extensions**.
3. Click the **Type** column to sort by type.
4. Find the entries whose Type is **Context Menu**.
5. Disable a few non-Microsoft Context Menu extensions at a time, then right-click the **same file** in OneCommander again (no need to close OC between tests).
6. If the missing context-menu items now appear, re-enable the extensions in groups until they disappear again. This will identify the extension interfering with enumeration.
You don't need to test 20 extensions individually. Disable approximately half, test OC, then enable/disable half of that group depending on the result. Repeating this should narrow it down to the problematic extension in only a few tests.
Some shell extensions that have caused OneCommander context-menu problems in the past include Fast Explorer, File Renamer Turbo, Tim by QQ, ACDSee PicaView, HoneyView, GeoSetter, and Cairo, although another extension could certainly be responsible on your system.
Please let me know whether OC + WinRAR work together in Windows Sandbox, and, if disabling any particular non-Microsoft Context Menu extensions fixes it
Reply all
Reply to author
Forward
0 new messages