Mouse clicks not registering most times

I'm not sure where else to post this as this isn't exactly a hardware issue, and I'll explain in a bit why.

My mouse has been ignoring a good amount of clicks. Or I should say, Windows is. Because some apps do register them, because it visually reacts to my clicks, but it doesn't activate, regardless. Does that make sense? Anyway, the weird thing is that this still happens with other mice. So I'm fairly certain this is a software-side issue. I have tried two other mice with the same result (two Logitech M510 wireless mice and an Onn wired "gaming mouse"), but tested my main mouse on another PC, with no issues on that one.

Here's what else I've tried:
Updating the drivers (no updates from MS Update, and Logitech only seems to have software to manage the mouse but no drivers? Huh?). I had this same issue with a wireless Logi keyboard, too. Software but no drivers.
Removing the mouse and the drivers completely, and reinstalling them. No changes there, either.
Checking my settings in Control Panel and in System Settings. Even adjusted double-click speed, cursor size, etc. No change.
Short of reinstalling Windows, is there anything else I could try?


(Mostly) Relevant info:
Windows 10 Pro v20H2, OS build 19042.964
Windows Feature Experience Pack 120.2212.2020.0
Installed on 10/‎25/‎2020

Wireless Mouse M510
Firmware ver 062.001.00015
Logitech Options ver 8.54.106

Mouse: HID-compliant mouse (3 listed in Device Manager, all the same info)
Driver ver 10.0.19041.1
Driver date 6/21/2006

Has anyone had this issue before? I can't seem to find any solid info on what the cause is or any possible solutions (that I haven't already tried), and it's driving me nuts.

Whackbag said:

Did you view & remove any hidden mouse drivers in device manager, shouldn't matter but worth a try. And what does it say under the Event tab of the "sort of working" installed one, any errors there?...Is this a usb issue maybe?

If your mouse works fine on other machines but other know to be good mice are doing the same thing on yours.

Just checked and sure enough, yeah, there were some residual drivers from "hidden" devices, so I removed those.

Sadly, still having issues with it. And I checked Event Viewer a while back after this had started happening, and I couldn't find anything pertaining to the mouse. Checked it again and it was just logs of me removing the excess mouse drivers.

I come back hoping that someone responded to this with a solution, but alas, no dice. My disappointment is immeasurable, and my day is ruined.

You could try the USB mouse in Safe mode to see if the symptoms change there.

Personally, I would reinstall the display driver by getting another copy from the maker.
- Your reported symptom is that a visual-related signal is not being passed into Windows correctly hence my suggestion.
- If the symptom does not appear in Safe mode then this would reinforce the logic behind this suggestion but, as I say, I'd do it now anyway.

Denis

Try3 said:

You could try the USB mouse in Safe mode to see if the symptoms change there.

Personally, I would reinstall the display driver by getting another copy from the maker.
- Your reported symptom is that a visual-related signal is not being passed into Windows correctly hence my suggestion.
- If the symptom does not appear in Safe mode then this would reinforce the logic behind this suggestion but, as I say, I'd do it now anyway.

Denis

I'll give that a shot. Just to be sure, I'll even run DDU beforehand, reboot, and reinstall the driver I downloaded from NVIDIA. In doing so, I can also test the safe mode accuracy as you suggested, since using DDU in safe mode is recommended.

So I gave it a week, and sad to say, no improvement, not even a slight change....

Megahertz said:

How old is the mouse?
I had a mouse that wasn't reacting to the left clicks but was to the right clicks. And sometimes it was bouncing (many clicks).
It was the mouse micro switch. Once replaced, the mouse worked normally.

It's still fairly new (like, four months old? Maybe five?)

Been doing this for a good while now, though.

I did find out something interesting, though. It also behaves like this in the BIOS, too, of all things.