Separate files from folders
Right-click a folder, then a file, then empty space. The pattern tells you whether the handler is a file action, a folder action or a shell-wide overlay.
A context menu that pauses for one or two seconds on every click is loading a handler that waits. The fix is narrowing which one.
Check the **shell extensions** first, then the **cloud sync overlays**, then a **network path** in the folder. A menu that only lags on files is a handler; one that lags everywhere is the shell itself.
Right-click a folder, then a file, then empty space. The pattern tells you whether the handler is a file action, a folder action or a shell-wide overlay.
A long menu is slower to build. The Windows 11 menu shortens the visible list and hides the rest behind Show more options, which is why the second click is faster.
Sort ShellExView by company, disable the non-Microsoft context menu entries in halves and test after each restart of the shell.
A mapped drive that is offline makes the menu wait for a timeout. Disconnect stale mappings and the delay disappears with them.
net use
OneDrive and similar clients add status entries that resolve in the background. Pausing the client for ten minutes is a faster test than disabling five handlers.
Time ten right-clicks before and after. A change you cannot measure is either not the cause or not the fix.
A desktop-specific handler, often a wallpaper or icon tool.
A network path or a huge file count. Test a local folder with few files.
A timeout, usually a dead network location in the shell namespace.
A shell replacement or a damaged profile. Test with a new user account.
No. The handlers can be disabled properly in ShellExView.
The handler is warm. The first click pays for loading it.
Re-enable the extensions in ShellExView and restart **explorer.exe**. Every previously active handler returns.
Free · no account needed · tracks your progress