Right-click not working in Windows 11 — context menu not appearing, appearing then immediately disappearing, or only showing a few options — has two common causes: Windows Explorer needs restarting (resolves about half of cases in 5 seconds), or a shell extension installed by some app is conflicting with the context menu (more involved fix). If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
The 5-second test: Ctrl+Shift+Esc → find “Windows Explorer” → right-click → Restart. The screen briefly flashes; the taskbar reloads. Try right-clicking again. If it works now, Explorer was the cause and you’re done. If the problem returns later, an Explorer addin or shell extension is causing repeated failures and the deeper fix below is needed.
If Explorer restart doesn’t help, the next quickest fix is the ShellExView audit. Microsoft’s NirSoft ShellExView (free) shows every shell extension on your system. Disable third-party extensions one at a time until right-click returns — that identifies the culprit. The full diagnostic below covers each path including the registry fix when ShellExView doesn’t find the offender.
Fastest fix: restart Windows Explorer
The right-click context menu is part of Windows’ shell, managed by Explorer. When Explorer gets into a bad state: context menus stop appearing or appear blank. Ctrl+Shift+Esc → Task Manager → right-click “Windows Explorer” → Restart. The desktop flickers briefly, then returns to normal. Test right-click immediately after.
If this resolved it: the issue was a transient shell state. If it happens regularly: the root cause needs addressing (see below).
Context menu appears then immediately disappears
This is the most frustrating variant — you can see the menu flash for a fraction of a second before it vanishes. The cause: a shell extension registered for the context menu is crashing immediately, taking the menu down with it. A faulty third-party shell extension (added by software installation) initiates then crashes the entire context menu display.
Fix: ShellExView (free from nirsoft.net) lists every shell extension installed on the system, including third-party ones. Sort by “Modified time” — recently installed or recently updated extensions appear at the top. Disable suspicious or recently-added extensions (right-click → Disable Selected Items) → test right-click after each group. The extension that causes the menu to work when disabled is the culprit. Uninstalling the associated software is the clean solution.
Desktop right-click not working
If right-click on the desktop specifically doesn’t work while File Explorer and taskbar work fine: tablet mode may be active or the desktop shell component has a specific issue. Settings → System → Display → check if tablet mode is somehow enabled. Win+I → search “Tablet mode” — disable it if active.
Also: some Windows 11 builds moved the context menu to a two-step process (click “Show more options” for the full legacy menu). If what appears is a simplified context menu rather than no menu: this is the new Windows 11 context menu design, not a failure. The full menu appears with Shift+right-click or by clicking “Show more options” at the bottom of the new menu.
Registry fix for context menu issues
Corrupted registry entries for shell extensions cause persistent context menu failures that Explorer restarts don’t fix. Run System File Checker to repair corrupted shell infrastructure:
sfc /scannowAdministrator Command Prompt. After SFC completes and you restart: test right-click. If SFC reported repaired files: shell infrastructure corruption was the cause.
For more targeted registry repair: Win+R → regedit → navigate to HKEY_CLASSES_ROOTDirectoryBackgroundShell and HKEY_CLASSES_ROOTDirectoryBackgroundShellexContextMenuHandlers. If any subkeys have obvious errors or don’t belong to installed software: they can be deleted to clean up the context menu extension list. Be cautious — deleting legitimate entries removes useful context menu options.
Restore the Windows 10 classic context menu
Windows 11’s new two-step context menu is a common complaint. To restore the full classic context menu permanently: Administrator Command Prompt:
reg add "HKCUSoftwareClassesCLSID{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}InprocServer32" /f /ve
Then restart Explorer. This restores the Windows 10-style full context menu as the default for right-click on the desktop and File Explorer. To revert: delete that registry key and restart Explorer.
File Explorer right-click specifically
Right-click in File Explorer that produces no menu or a very slow menu: too many shell extensions are loading for each right-click. Every installed application can add entries to the context menu, and with many applications installed: the menu takes several seconds to load as each extension is queried. ShellExView again: identify and disable extensions from applications you don’t need in the context menu.
Our guide on taskbar and shell issues covers the Explorer restart approach for other shell failures that occur alongside right-click problems. For context menu customisation beyond fixing failures, our Windows shell customisation guide covers ShellExView and similar tools in more detail. Microsoft’s context menu documentation covers the new Windows 11 context menu design, the keyboard shortcut to access it (Shift+F10 for the full classic menu), and Group Policy settings that can restore the classic menu in enterprise deployments.
Right-click not working in specific applications
If right-click works everywhere in Windows except inside one specific application: the application is capturing mouse events and preventing Windows from seeing the right-click. This is common in games, drawing applications, and remote desktop sessions. For the application: check its own right-click or context menu settings. Some applications use Ctrl+click or a custom button for context menu functionality instead of right-click.
Touch screen right-click (press and hold)
On touchscreen Windows 11 devices: right-click is simulated by pressing and holding (long press). If this doesn’t produce a context menu: Settings → Bluetooth and devices → Touchscreen → confirm “Press and hold to right-click” is enabled. If the hold produces an animation (ring that completes) but no menu appears: the context menu failure is separate from touch input detection — treat it as a regular right-click failure and follow the shell extension and Explorer restart fixes above.
Mouse driver contributing to right-click failure
On rare occasions: a faulty mouse driver sends incorrect button event codes, preventing right-click from being recognised as a right-click by Windows. This is more likely if right-click failure happened after a mouse software update or driver change.
Test with a different mouse or with the mouse’s manufacturer software disabled. Device Manager → Mice and other pointing devices → right-click the mouse → Uninstall device → disconnect → reconnect → Windows reinstalls the generic HID driver. If right-click works with the generic driver: the manufacturer’s driver was the cause. Rollback the driver or update to the latest version.
Windows 11 Clean Boot for persistent right-click failures
If right-click fails persist through Explorer restart and SFC: a startup application or service is interfering with shell extension loading. Clean boot identifies this:
- Win+R → msconfig → Services → check “Hide all Microsoft services” → Disable all
- Startup tab → Open Task Manager → disable all startup items
- Restart → test right-click
If right-click works in clean boot: re-enable services and startup items in groups to identify the conflict. Security software and system management tools are the most common causes of shell extension interference in clean boot testing.
Group Policy context menu restrictions
In enterprise environments: Group Policy can restrict the desktop context menu to prevent users from accessing system settings. If right-click on the desktop shows nothing or a limited menu on a managed machine: gpedit.msc → User Configuration → Administrative Templates → Desktop → “Remove Desktop context menu” — if enabled: that’s the cause. IT controls this restriction; contact them if desktop right-click is needed for legitimate work purposes.
Context menu extensions from common software
Context menu entries are added by many common applications. Knowing which software adds which entries helps diagnose “disappeared” menu options:
- 7-Zip, WinRAR: adds “Extract here,” “Add to archive” — appears for compressed files and general right-click
- Git clients (Git, GitHub Desktop): adds “Git Bash here,” “Git GUI here” — appears in folders
- NVIDIA/AMD Control Panel: adds “NVIDIA Control Panel,” “AMD Radeon Settings” — appears on desktop
- Antivirus software: adds “Scan with [product]” — appears for files
- Send to menu: all applications registered as “Send to” destinations appear in this submenu
If specific menu entries disappeared after uninstalling software: the extension was removed correctly. If entries are still present after uninstallation: a registry remnant remains. ShellExView shows these orphaned extensions — they can be disabled or the registry entries manually removed.
Right-click on the taskbar — separate behavior
Taskbar right-click is handled by a separate component from desktop and Explorer right-click. If the taskbar context menu is working but desktop right-click isn’t (or vice versa): they’re independent failures. Taskbar right-click → Taskbar settings is always available regardless of desktop shell extension state. If the taskbar menu is also missing: the Explorer restart covers both simultaneously.
ShellExView detailed usage
ShellExView categorises shell extensions by type. For context menu troubleshooting: focus on extensions with “Context Menu” in the “Type” column. Third-party extensions (highlighted in pink in ShellExView by default) are the most likely causes of context menu failures — Microsoft’s own shell extensions (white background) rarely cause problems.
The disable/enable cycle in ShellExView is non-destructive: disabled extensions aren’t deleted, just deactivated. After identifying the problematic extension: the choice is to leave it disabled (losing that context menu functionality) or uninstall the associated software (removing it entirely). Leaving a disabled shell extension from an application you still use removes that extension’s context menu options — weigh the trade-off.
| Symptom | Cause | Fix |
| No right-click response at all | Explorer shell crash | Restart Explorer via Task Manager |
| Menu flashes briefly then disappears | Faulty shell extension crashing | ShellExView — disable recently installed extensions |
| Simplified menu instead of full menu | New Windows 11 context menu design | Use Shift+right-click for full menu; or restore via registry key |
| Menu slow to appear | Too many shell extensions loading | ShellExView — disable unused extensions |
| Works everywhere except one app | Application capturing mouse events | App-specific setting; try Ctrl+click or app’s keyboard shortcut |
| Not working after group policy change | Enterprise policy restriction | Contact IT; gpedit.msc to verify policy status |
Right-click failures are almost universally shell-related — either a crashed Explorer state (fixed in seconds with a restart) or a problematic shell extension (identified with ShellExView in minutes). The Windows 11 simplified context menu design accounts for the remaining reports where the “failure” is actually the new design working as intended. Understanding which of these three situations you’re in resolves the problem before any deeper investigation is needed.
For users who right-click frequently and rely on specific context menu items for their workflow: the new Windows 11 two-step context menu is a genuine productivity issue, not just a cosmetic change. The registry command to restore the classic menu (above) is a supported workaround that many power users apply immediately after a Windows 11 installation or upgrade. It doesn’t break any functionality — it just restores the previous behaviour. Microsoft may change this in a future update, but as of current Windows 11 versions: the registry key approach works reliably.
Context menu in Windows PowerShell and Terminal
PowerShell and Windows Terminal windows have their own right-click behaviour. In a Terminal window: right-click typically pastes from clipboard (configurable in Terminal settings). If right-click in Terminal is producing unexpected results: Terminal settings → Actions → right-click behaviour can be changed from “Paste” to “Context menu” if you want a context menu there instead. This is separate from Windows Explorer’s context menu and has its own configuration.
OneDrive shell extension impact
OneDrive installs a shell extension that adds status overlays and “Share,” “Sync,” and “View online” options to the context menu for files in the OneDrive folder. On machines with many files or OneDrive sync issues, this extension can slow down or intermittently block the context menu while it tries to resolve file sync status. If right-click is slow specifically in OneDrive folders: pausing OneDrive sync temporarily → test right-click speed. Updating OneDrive to the current version often resolves this as Microsoft frequently patches the shell extension for performance issues.
A practical note on shell extension management: Windows doesn’t provide a built-in way to manage third-party shell extensions. Every time you install software that adds to the right-click menu: it modifies the registry without asking. Over years of software installation and removal: the shell extension list accumulates entries from software you may no longer have installed, removed software that left registry remnants, and obscure features from installed applications. Running ShellExView annually and disabling entries from uninstalled software or features you never use keeps right-click performance responsive and reduces the chance of extension conflicts causing failures.
If right-click issues appeared specifically after a Windows 11 feature update: Microsoft occasionally ships updates that temporarily affect shell extension compatibility. In these cases: the problem usually self-resolves with the next cumulative update as Microsoft patches the regression. Reporting via the Windows Feedback Hub (Win+F) during this period helps Microsoft prioritise the fix. In the meantime: using Shift+F10 as the keyboard shortcut for context menu bypasses the broken right-click mouse event path and provides a functional context menu while the shell issue persists.
One underused keyboard alternative worth knowing: Shift+F10 opens the full classic context menu for whatever is currently selected, without needing to right-click at all. On keyboards with an Application key (looks like a menu icon, usually between right Alt and right Ctrl): pressing it directly opens the context menu for the current selection. These keyboard shortcuts provide reliable context menu access even when mouse right-click is malfunctioning, and they always produce the full classic menu rather than the new Windows 11 simplified version — making them genuinely useful both during troubleshooting and as permanent habits for keyboard-oriented users.
Why does my Windows 11 right-click menu appear then disappear instantly?
A shell extension is crashing during the menu’s render. Windows tries to show the menu, an extension errors, and Windows hides the menu rather than showing a partially broken one. The fix: identify which extension via ShellExView (NirSoft, free) — start by disabling all non-Microsoft extensions, then re-enable one at a time. The crashing one will appear in Event Viewer logs around the time right-click fails.
How do I restart Windows Explorer without restarting my PC?
Ctrl+Shift+Esc opens Task Manager. Find ‘Windows Explorer’ in the Processes tab. Right-click → Restart. The screen flashes briefly as the taskbar reloads. Takes about 2 seconds. This is the single most useful Windows 11 fix — resolves taskbar issues, file explorer freezing, right-click not working, and Start menu problems.
Why does right-click work on desktop but not in File Explorer?
Different contexts have different shell extensions. Desktop right-click uses one set; File Explorer right-click uses a different set including file-type-specific handlers. If only File Explorer fails, the broken extension is one that registers for file types — common culprits are cloud storage clients (Dropbox, OneDrive), media tools, and antivirus products.
Does the new Windows 11 right-click design affect this?
Windows 11 introduced a shortened right-click menu with a ‘Show more options’ link to access the classic menu. The shortened menu is more stable; the classic menu (Shift+Right-click or ‘Show more options’) has the same shell extension issues that affected Windows 10. If your problem only occurs with the classic menu, the shell extension cause is confirmed.
Can a Windows update break right-click?
Yes occasionally — particularly major feature updates that change how shell extensions interact with the new menu. After a Windows update with right-click broken, first try Explorer restart. If that doesn’t help, the update broke an extension you have installed — update the offending app to its latest version (vendors usually release compatibility updates quickly). Our guide on Windows 11 Start Menu Not Working covers an adjacent issue.
Will resetting Windows fix right-click problems?
Yes, but it’s massive overkill. A Windows reset reinstalls Windows and removes most third-party apps — eliminating the shell extension causing the problem but also destroying your software configuration. The ShellExView approach finds and disables just the problem extension in 10 minutes without losing anything. Reset only if you’ve tried other fixes and prefer a clean slate. See also Windows 11 Context Menu Slow for a related case.
