When a touchpad right-click stops responding, the most common culprits are a disabled tap-to-click gesture, a secondary-click setting toggled off in the OS, or a hardware click zone misconfigured by the driver. Left-click continuing to work rules out a dead touchpad — the surface is receiving input, but the system is not mapping it to a right-click event. Working through the three layers below (OS settings → driver → physical interaction) resolves the problem in almost every case.
How right-click is generated on a touchpad
Unlike a physical two-button mouse, a touchpad has no dedicated right-click button. Instead, it generates a right-click event through one of two physical actions: a two-finger tap anywhere on the surface, or a click in the lower-right corner of the pad (on older non-clickpad designs). Which action the OS responds to depends entirely on how the touchpad driver and gesture settings are configured.
On a Windows Precision Touchpad, Windows handles the gesture layer directly. On a standard (legacy) touchpad, the vendor driver — Synaptics, Elan, or ALPS — translates the physical tap into a right-click event before Windows ever sees it. If that translation step is disabled or misconfigured, the OS receives nothing, even though the pad detects the contact.
The three layers to check
Start from the highest-level setting and work down. Most right-click failures are resolved at layer one.
- Layer 1 — Windows Touchpad Settings — Open Settings, navigate to Bluetooth & devices, then Touchpad. Scroll to "Taps" and confirm "Tap with two fingers to right-click" is enabled. On systems with a legacy driver, this section may be sparse or absent — proceed to layer 2.
- Layer 2 — Vendor driver control panel — Synaptics and Elan both install their own settings applet in Control Panel or the system tray. Look for a "Two-Finger Tap" or "Secondary Tap" option. These settings are independent of the Windows Touchpad page and override it on legacy hardware. If the vendor panel is missing, the driver may have been replaced by a generic HID driver after a Windows Update — reinstalling the OEM touchpad driver from the manufacturer's support site restores the panel.
- Layer 3 — Physical click zone — If the pad uses a physical bottom bar rather than a true clickpad, the right-click zone is the lower-right third of that bar. Test by pressing there firmly and listening for a distinct click. A soft or absent click can mean the click mechanism has worn down or a bottom screw has worked loose.
Less obvious causes worth checking
Two scenarios regularly catch users off-guard:
- A stuck Shift or Ctrl key — Some apps intercept right-click shortcuts at the application level. A modifier key physically stuck in a pressed state can redirect the event. Press and release each modifier key once, then retry.
- The browser or remote desktop capturing events — Remote Desktop, VMs, and some browser extensions consume pointer events before the webpage or OS action fires. Reproduce the problem in a different context (File Explorer, Notepad) to confirm the failure is system-wide rather than app-specific.
- macOS "Secondary click" toggle — On macOS, go to System Settings (or System Preferences on older versions), select Trackpad, and confirm "Secondary click" is enabled and set to "Click or tap with two fingers." Apple sets this to off by default on some configurations.
What to look for in a browser-based test
A browser touch tester records both the pointer event type and the button index it carries. A left-click generates button: 0; a right-click generates button: 2. If the Event Log shows only button: 0 entries no matter which gesture you use, the two-finger tap is not reaching the browser as a secondary-click event — the driver or OS setting is not translating it correctly. If button: 2 does appear but the context menu never opens, the browser itself is suppressing the default action (common on some canvas elements), which is a separate issue from the hardware.
One limitation worth stating: a browser tool tests what events reach the page, not what happens in native UI. A right-click that works in File Explorer but fails on a webpage points to browser-level event handling, not a driver or hardware problem.
Quick check: use the tester above and two-finger tap on the canvas — then look at the Event Log panel. If you see acontextmenuorpointerdown button:2event, your driver is generating the right-click correctly. If neither appears, the fix is in Settings or your touchpad driver.