My Windows 11 computer repeatedly behaves as though the middle mouse button is being held down, even when I am not touching it. This makes some games unplayable and makes normal use difficult. I have already tried another mouse and keyboard, removed and reinstalled the mouse drivers, restarted the computer, and checked that I do not have any obvious macros configured in iCUE or Corsair software. Clicking the middle mouse button itself does not seem to do anything. I only have one mouse, keyboard, monitor, and speakers connected, so I would prefer to troubleshoot this rather than reinstall Windows.
3 Answers
Run a full malware and virus scan as a precaution, especially if the input tester shows the button being pressed even when the mouse is untouched. If the scan is clean, try a clean boot or temporarily disable background utilities such as Corsair software and other peripheral-management programs. A clean boot can help identify software that is generating or remapping the input without requiring a Windows reinstall.
Disconnect every peripheral except the mouse, keyboard, and monitor, then test again. Controllers, drawing tablets, wireless receivers, and other USB devices can sometimes send unexpected input. Since you have already tried that and the issue remains with only the basic devices connected, the next step is to use an online mouse and keyboard tester to confirm whether Windows is continuously receiving a middle-button signal.
The online input test is useful here because it separates a physical mouse problem from a Windows or software problem. If it shows the middle button constantly pressed but does not register when you physically click it, Windows is likely receiving a stuck or remapped input from a driver or background utility. Check the tester after booting into Safe Mode; if the problem disappears there, disable startup applications and reinstall or remove any mouse, keyboard, gaming, or overlay software one at a time.

The scan found no threats. I also checked that there were no obvious macros configured, but the problem is still happening.