nimraynn

I originally posted in another thread that I came across from Google that seemed recently active, but it looks like this thread is more active so thought best to post here. I am experiencing the same issues with my M65 Elite. I purchased it from Amazon UK on 12/08, it's now 14/10 so we're talking as near as makes no difference two months old. The problem has existed for at least a week, if not two, now so we're talking a month and a half to develop the fault. That's horrendous. I agree that it's a hardware problem. For my particular setup, I have my personal gaming PC running Windows 10 & iCUE along with my Lenovo work laptop that is running Windows 10 without iCUE. Corporate policy means I cannot, nor do I have any desire to, install iCUE on this machine. I have no need for customisations on my work laptop as I'm just using it as a basic mouse here. The fault exists on *both* machines, so I think that can rule out iCUE causing any problems and potentially any driver issues. Also should cut out any OS issues being two different machines. Both running Windows 10, but different versions. Work machine is on 1809. Personal machine is on whatever the latest and greatest is. 20H2? 2009? Something like that. A great post by SteemSucker about how to replace the microswitches. It sounds like this is spot on the money for where the problem lies. Unfortunately I don't have enough faith in my soldering skills to even consider giving this a try... but also on principal, why should I have to do this? I've already paid good money for the mouse in the first place, it would be nice if it worked in the first place. It seems this is a known and fairly well documented issue, yet there doesn't appear to be any official acknowledgement from Corsair. Also interesting to see regarding the China vs. Taiwan manufacturing differences. I have checked the label on mine and it is a made in China model. I'm currently considering which option I want to take... send an RMA through and get another device sent through which will inevitably have the same defect as it seems they all do.... or request a refund from Amazon UK and use that money to purchase a similar mouse from a different brand. I like the design and general feel of this mouse so I'm a little reluctant to return it and purhcase a different brand, but I don't know if I have much choice if I'm going to end up RMA'ing the device every 2-3 months. Edit And a new, really useful feature just happened... It just locked up completely. RGB lights still happily flickering away, but no responsiveness at all. Disconnect and reconnected fixed it, but I seem to remember reading another poor customer in this thread who had the same experience. Hopefully this is less common than the left click issue.....

I am also having the same issue with a nearly brand new M65 ELITE. I purchased it on 12 August. It's now 14th October, so it's slightly over two months old but it's been doing this for at least two weeks now, gradually getting worse. I love the mouse as a whole, it's a really good design... but this left click issue is making it so frustrating to work with. I use the mouse daily, switching between two different machines... my personal gaming PC and my Lenovo work laptop. Both of them exhibit the same experience so it's definitely the mouse hardware at fault, not something in the machine or software. I have tried doing a "hard reset" on the mouse, I assume it has some firmware in it for some reason... this didn't make a blind bit of difference. Double click is where it's at its worst. I can happily sit in Outlook and have to double click an e-mail 6 times before it actually opens. Sometimes it takes at least two or three clicks for it to even select the e-mail. At the moment, I'd say it's probably registering 75% of general clicks, but when it comes to double clicks, it registers about 30% of those. Being someone who works at their computer all day, this is very very frustrating. I will likely look to RMA it very shortly, but I'm not overly comfortable with the idea of getting a replacement as judging from the search results that led me to this thread, it seems to be a very very common issue with Corsair mice in general... so I'm not confident in the product enough to feel a replacement will be any better and would probably RMA'ing the RMA replacement only a few months later. Considering the number of reports I'm seeing, it would be good if Corsair could actually investigate this problem, confirm it and FIX IT rather than just telling everyone to RMA their product for a replacement.