When I right click on certain files only (for example a .msi file) the context menu is slow.
Windows 11 Explorer is also slow when right click - show more options
I have installed the shexview utility and disabled all extensions, except the Microsoft ones and the Directory Opus ones but this has not improved the situation.
Is there any way to trace the Context Menu so I can see the timings for each extension? Or is there any known issue about this?
I am using Windows 11 Pro with the latest updates. Directory Opus and Start11.
1 Like
It’s probably antivirus scanning the file if it only happens for MSIs.
I have followed the steps outlined here
and I generated a debug here is the output
| 00000027 | 0.00181740 | [17724] [17816] dopus: Packaged COM: MicrosoftWindows.CrossDevice_1.24051.36.0_x64__cw5n1h2txyewy | |
|---|---|---|---|
| 00000028 | 0.00197580 | [17724] [17816] dopus: CLSID: {792252D0-144F-11E1-BE50-0800200C9A66} (Shell010Ext Class) (C:\Program Files\010 Editor\shlext010x64.dll) | |
| 00000029 | 0.03240580 | [17724] [17816] dopus: CreateShellExtInit: IP | |
| 00000030 | 0.03256370 | [17724] [17816] dopus: Add CME button &010 Editor with ID 1003 = 0x3eb | |
| 00000031 | 0.03275600 | [17724] [17816] dopus: CLSID: {A6595CD1-BF77-430A-A452-18696685F7C7} (Acrobat Elements Context Menu) (C:\Program Files (x86)\Adobe\Acrobat 2020\Acrobat Elements\ContextMenuShim64.dll) | |
| 00000032 | 0.04761220 | [17724] [17816] dopus: CreateShellExtInit: IP | |
| 00000033 | 20.49374580 | [17724] [17816] dopus: CLSID: {EE15C2BD-CECB-49F8-A113-CA1BFC528F5B} (DriveFS ContextMenu Handler) (C:\Program Files\Google\Drive File Stream\90.0.3.0\drivefsext.dll) | |
| 00000034 | 20.51240349 | [17724] [17816] dopus: CreateShellExtInit: IP | |
| 00000035 | 20.51664734 | [17724] [17816] dopus: CLSID: {09A47860-11B0-4DA5-AFA5-26D86198A780} (C:\Program Files\Windows Defender\shellext.dll) | |
| 00000036 | 20.51771164 | [17724] [17816] dopus: CreateShellExtInit: IP | |
| 00000037 | 20.52793694 | [17724] [17816] dopus: Open-With Menu: Building... | |
| 00000038 | 20.53027534 | [17724] [17816] dopus: Open-With Menu: Done. |
it looks like there is long delay between these entries
| 00000032 | 0.04761220 | [17724] [17816] dopus: CreateShellExtInit: IP | |
|---|---|---|---|
| 00000033 | 20.49374580 | [17724] [17816] dopus: CLSID: {EE15C2BD-CECB-49F8-A113-CA1BFC528F5B} (DriveFS ContextMenu Handler) (C:\Program Files\Google\Drive File Stream\90.0.3.0\drivefsext.dll) |
Ok I figured it out
I blocked
CLSID: {A6595CD1-BF77-430A-A452-18696685F7C7} (Acrobat Elements Context Menu) (C:\Program Files (x86)\Adobe\Acrobat 2020\Acrobat Elements\ContextMenuShim64.dll)
and now it's fast again
I had a slow-right-click issue come up as well (DOpus 13). I followed the debugging steps and found the issue was being caused by an extension mentioned above, apparently related to Google Drive:
CLSID: {EE15C2BD-CECB-49F8-A113-CA1BFC528F5B} (DriveFS ContextMenu Handler) (C:\Program Files\Google\Drive File Stream\90.0.3.0\drivefsext.dll)
I blocked that extension in DOpus Preferences and that solved my delay. Wanted to report it here, as suggested.
3 Likes
I disabled "MicrosoftWindows.CrossDevice" as files and folders inside OneDrive synced folders take forever to open the context menu.
3 Likes
Thank you for this Nicola, this fixed my delay problem. Kind of a bummer though because now I can't use the "Share..." function with Onedrive locations.
In MS-File Explorer "Share..." works and has no delay, I'm not sure what MS updated to break things in DOpus. This happened after an in-place update from Windows 10 -> Windows 11, so I'm thinking that is related.
I also had to turn off MicrosoftWindows.CrossDevice recently. I don't know how long I've had the problem because I always use Dopus's own, but there's some change in windows that makes it not work as it should in Dopus. For me it doesn't matter that it doesn't work because I don't use that function at all.
It took a while before I figured out that it was MicrosoftWindows.CrossDevice, just delay in the Onedrive folders for me too.
The guide that Dopus has posted on the forum helped me find the error:
Glad to help.
I suggest to Dopus devs to investigate the CrossDevice issue as many users have the same problem.
2 Likes
Perhaps @Leo might have some updates/suggestions?
We'll block CrossDevice by default in 13.14. We recommend blocking it manually if you're seeing problems with it and don't want to wait.
1 Like