Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Resolved Question

My left mouse button stopped working with Win 10 v1803

May 14, 2018 2:13PM PDT

My left mouse button stopped working after installing the Windows 10 v1803 update. At first I thought the system was hanging up but then I realized that it just wasn't responding to the left mouse button. I was using a Logitech MK330 wireless keyboard and mouse which worked fine up until today. I was able to work around the problem by using a combination of my right mouse button and keyboard but that was definitely sub-optimal and did not work in every situation. I was able to check the mouse drivers in the device manager and it said that the latest versions are installed. I ran out to BestBuy and bought a new M310 mouse which seems to be working ok for the moment but I don't have high confidence that the problem won't return. Does anyone have any ideas on how to fix this short of buying a new mouse?

Discussion is locked

johnwidder has chosen the best answer to their question. View answer
- Collapse -
Clarification Request
Were you able to test this
May 14, 2018 2:22PM PDT

1. On another PC.
2. Without ANY Logitech drivers.

- Collapse -
My left mouse button stopped working with Win 10 v1803
May 14, 2018 3:20PM PDT

I don't have another PC to test it on. The driver says that it is a Microsoft driver, not Logitech. I checked the Logitech website in the hope that they might have their own driver but no luck. I think that most of the common drivers for Win 10 are supplied by MSFT.

- Collapse -
Until it's tested on another PC or another OS
May 14, 2018 3:29PM PDT

It can be coincidental.

- Collapse -
Clarification Request
info
May 14, 2018 3:51PM PDT

Best Answer

- Collapse -
try this unifying receiver software
May 14, 2018 3:49PM PDT
- Collapse -
re: try this unifying receiver software
May 15, 2018 5:12AM PDT

I'll give it a try. Thanks!

- Collapse -
re: try this unifying receiver software
May 15, 2018 6:26AM PDT

I installed the Logitech unifying receiver software and it didn't help resolve the problem with my first mouse but at least it allowed me to pair my new mouse with the existing receiver so I don't have to use up two USB ports with separate receivers. It didn't exactly solve my problem but I have a solution that works so I'll call that good enough. Thanks for your help!

- Collapse -
re: try this unifying receiver software
May 15, 2018 6:52AM PDT

One more thing - after I got the new mouse working with the old receiver I took the old mouse apart and checked the switches for the left and right buttons with an ohm meter. Both switches appear to be working properly. The switch is by far the most likely point of failure for a hardware problem so I think it is extremely unlikely that the mouse is the source of the problem. Hopefully MS will fix the problem in a future update.

- Collapse -
Good test but needs one last test.
May 15, 2018 7:57AM PDT

That's one good test but until this is tested on another PC or device we can't be sure it's not some cracked trace, solder joint or chip failure.

- Collapse -
re: Good test but needs one last test
May 17, 2018 5:40AM PDT

Cracked traces, solder joints, and chip failures usually show up as infant mortality failure modes early in a product's life. I've been using this mouse for several years. I'm not saying it's impossible, only that it's unlikely. In any event I don't have any other computers to test this mouse on, and since I have a solution I'm considering this closed. Thanks to everyone for your help!

- Collapse -
Answer
Interesting, MS Installs A New Mouse Driver Version for 1803
May 14, 2018 7:42PM PDT

A check on this computer, where I use a USB Logitech mouse and keyboard, shows a different Microsoft driver version than was there before. Checking the "Properties/Driver" for both the "HID compliant" mouse and keyboard in Device Manager, I see the "Driver Version" as 10.0.17134.1.. But, and this is the interesting part, the "Driver Date" is still 6/21/2006.

The new driver version is the same as new "build number" release for version 1803 but that's not the driver version that was there before. I'm just curious if the new driver is actually different from the previous one. Unfortunately, even though the driver version has a new number, the "Roll Back Driver" button is greyed out here, making it tough to simply roll back to the previous version to test for a fix.

Hope this helps.

Grif

- Collapse -
that's too outdated
May 14, 2018 8:05PM PDT

The drivers for "unifying receivers" didn't even arrive till some time after 2010, and in Linux till 2012.

- Collapse -
sorry, it was 2009
May 14, 2018 8:08PM PDT
- Collapse -
You're Assuming The Driver is From 2006
May 15, 2018 3:40PM PDT

Although the driver date indicates it's from 2006, the driver version number is actually from 2018. Clearly, when MS installed all the files for its latest Windows 10 1803 update, it changed the default driver version number to the same number as their 1803 build number, 10.0.17134.1. That happened this month, May.

So, whether the driver is actually a new driver with a new version number and an incorrect, old driver date..... or an old driver from 2006 that they changed the version number on, who knows? Unfortunately, I don't have the previous version of Windows 10 to check.

Either way, interesting...

Grif

- Collapse -
well, if it was....
May 15, 2018 8:38PM PDT

....canned food, would you eat it? Wink

- Collapse -
I Did That Once In College....
May 17, 2018 12:34PM PDT

...and I got really good at the porcelain hug... Most of the weekend.

Grif