Fix a Mouse That Double-Clicks on Its Own

A single click that fires twice is visible in a text field or in a click counter. Testing in Notepad removes any application-level cause.

Get-ItemProperty 'HKCU:\Control Panel\Mouse' | Select-Object DoubleClickSpeed,DoubleClickHeight,DoubleClickWidth,MouseSensitivity
Get-ItemProperty 'HKCU:\Control Panel\Mouse' | Select-Object * -ExcludeProperty PS*
notepad.exe

A macro tool or a vendor utility can send a second click. Closing those processes and testing again separates software from hardware in one step.

Get-Process | Where-Object { $_.Name -match 'razer|logi|ghub|corsair|icue|autohotkey|powertoys' } | Select-Object Name,Id,Path
Get-CimInstance Win32_StartupCommand | Where-Object Command -match 'razer|logi|corsair|autohotkey' | Select-Object Name,Command
# close them, then test in Notepad again

A generic driver can report duplicate events from a flaky device. The device's status and driver version show whether Windows sees a problem.

Get-PnpDevice -Class Mouse,HIDClass | Select-Object FriendlyName,Status,Problem,InstanceId
Get-CimInstance Win32_PnPSignedDriver | Where-Object DeviceClass -eq 'MOUSE' | Select-Object DeviceName,DriverVersion,DriverDate
Get-PnpDeviceProperty -InstanceId (Get-PnpDevice -Class Mouse | Select-Object -First 1).InstanceId -KeyName 'DEVPKEY_Device_LastArrivalDate' -ErrorAction SilentlyContinue | Select-Object Data

A worn switch bounces at the moment of release. Clicking slowly at the very edge of the button usually reproduces it more often than a fast click.

# click slowly on the far edge of the left button
timeout /t 30
# compare with a second mouse on the same port
Get-PnpDevice -PresentOnly -Class Mouse | Select-Object FriendlyName,InstanceId

A marginal USB connection can duplicate HID reports. Another port and a wired connection are the control test for a wireless mouse.

Get-PnpDevice -PresentOnly | Where-Object { $_.Class -in 'USB','HIDClass' } | Select-Object FriendlyName,Status
Get-CimInstance Win32_USBControllerDevice | ForEach-Object { [wmi]$_.Dependent } | Where-Object Name -match 'Mouse' | Select-Object Name,Status
powercfg /devicequery wake_armed

A switch that bounces is a hardware fault. Replacement is the fix; a debounce tool only hides it and adds latency to every click.

Get-ItemProperty 'HKCU:\Control Panel\Mouse' | Select-Object DoubleClickSpeed
Set-ItemProperty 'HKCU:\Control Panel\Mouse' -Name DoubleClickSpeed -Value 500 -Type String
Get-PnpDevice -Class Mouse | Select-Object Status,Problem
# if bouncing persists with another mouse, the port or the driver is the cause