A button that does nothing feels like hardware failure, but very often it is not. This guide separates the two in a few minutes, cheapest checks first.
Start by finding out what the browser sees
Run the mouse button test and press every button. The diagram lights up as each one registers.
This single step tells you a great deal, because the browser sees the raw button number your mouse reports, before your operating system decides what it means. So:
- The button lights up here but does nothing in your applications — the hardware is fine. This is a binding or driver problem.
- The button does not light up here either — the signal is not reaching the browser at all. That could still be software intercepting it upstream, but hardware is now genuinely possible.
If the button does not register at all
Work through these in order. The first three cost nothing.
1. Close your vendor software
Logitech Options, Razer Synapse, Corsair iCUE, SteelSeries GG and their equivalents remap buttons by default on many profiles. When a button is bound to a macro or an application shortcut, the browser never receives a button press — the software consumes it.
This is overwhelmingly the most common cause of dead side buttons. Close the software entirely, or reset the button to its default mouse function, and re-test.
2. Try a different USB port
Front-panel ports are wired through extension cables and are noticeably less reliable than rear motherboard ports. Unpowered hubs are worse still, especially with several devices sharing them.
Plug directly into a rear port and re-test.
3. Try a different cable
If your mouse has a detachable cable, swap it. Cable failure near the strain relief — where the cable leaves the mouse body and flexes constantly — is common and produces intermittent faults across every input on the device.
4. Test on another computer
This separates the mouse from your system in one step, and it is worth doing before any disassembly. If the button works elsewhere, the fault is in your system configuration, not the mouse.
5. Check for physical obstruction
Press the button and compare how it feels to its neighbours. A button that feels mushy, or that does not click, usually has debris under the plunger rather than a failed switch.
Blow compressed air around the button edges. On many mice you can work a small amount of isopropyl alcohol in around the plunger and click repeatedly to flush debris out.
6. Now suspect the hardware
If the button fails on a second computer, with vendor software closed, on a rear USB port, with a known-good cable, then it is genuinely a hardware fault. The likely candidates are a failed switch, a cracked solder joint, or a damaged ribbon cable inside the mouse.
Cracked solder joints are worth knowing about because they are easy to fix if you can solder and completely invisible otherwise. Open the mouse and inspect the switch pins under good light for a hairline ring around the joint.
If the button registers but does nothing in applications
The hardware is confirmed working, so this is entirely a software problem.
Check the binding. Open your vendor software and look at what that button is assigned to. Disabled and unassigned are easy to set accidentally when switching profiles.
Check per-application profiles. Most vendor software supports different bindings per application. A button that works on the desktop but not in one game usually has an application-specific profile overriding it.
Reinstall the driver. In Device Manager, uninstall the mouse under Mice and other pointing devices, then unplug and replug it. Windows reinstalls the driver cleanly.
Check whether the application supports it. Side buttons in particular are not universally supported. Some applications simply ignore buttons 4 and 5.
Middle click specifically
Middle click deserves its own note, because it fails differently.
The wheel click is a separate switch from the wheel rotation mechanism. Your wheel can scroll perfectly while the click underneath it is completely dead — these are independent parts and independent failures.
Middle click is also commonly intercepted. Browsers reserve it for autoscroll and for opening links in new tabs, and some extensions capture it before a page can see it. If middle click fails only in the browser, try a private window with extensions disabled.
While you are testing
If you have the mouse apart or you are already troubleshooting, it is worth running the other checks. The double click test catches switch chatter that has not yet become obvious, and the scroll test checks the wheel encoder. Both faults develop gradually, and catching them early is what makes them cleanable rather than terminal.