bignick277

I'm glad it's helped a few people for the short term until a more permanent firmware fix is released to the public. Thanks for posting your results. As was with my case, the fix only seemed to work for me for about 3 days before the issue came back, which is why I got the firmware fix from James, which I've been testing extensively since then. It's been about a week and a half since I applied the firmware fix and I've not had a recurrence of the issue since. Not even so much as a hiccup. Making this the longest I've gone thus far without the issue coming back. So I think I can say with reasonable certainty that the beta firmware resolves the double-click issue. Hopefully they'll release it to the public soon. For the meantime time, I hope this thread can help some people and James can help those he can until it's released. I'm going to go PM James now with my testing results from the past week and a half. The more confirmations they can get, the quicker they can release. Good luck guys/gals

Yeah, I just got the firmware fix from James about an hour ago. So I will be testing that from here on. Prelim looks good. But again, I think it will take about a week to be sure if it's resolved the issue. In both instances for the issue to appear for me, it took about 3 days for it to rear it's ugly head again. So a little over a week gives a little over double that time for testing.

Crap, bad luck on my front as well. The issue has now returned. It's not that bad at the moment. At least, it's not as bad as it was the first time round. But it's back just the same. Damn. Well hopefully I can get a beta firmware to fix this issue.

Sorry to hear that. I didn't have any delusions that this would fix everyones issue. It's resolved mine for the meantime, but I would still prefer a more permanent fix. I've also contacted James as well for the firmware update. Sorry I couldn't be of any more help.

If the problem didn't go away from simply uninstalling the software (as it did in my case), you may need to actually fully reset the mouse as well. So I would suggest doing the following steps next. 1. You've said that you deleted the roaming folder... Good start 2. Ensure the installation directory is gone as well. C:\Program Files (x86)\Corsair\Corsair Utility Engine 3. Check the device manager and compare it to the images I've posted above. Ensure that the Corsair drivers (they will say corsair on them in the device manager) are gone from the Device Manager. 4. Download the latest CUE software from Corsairs download page here: http://www.corsair.com/en-gb/vengeance-m65-rgb-fps-laser-gaming-mouse-black 5. Fully install the software and start the CUE application. 6. Go to Settings and then click the Device tab. In here you will see the polling rate and it will say if the device is working properly. Just so we have comparable circumstances, Make sure your polling rate is set to 1000hz. (Note: While you're here, click the update button to ensure that you have the latest firmware installed on your mouse.) 7. Go to Profiles and check the Drop Down Box where it says Default. Make sure Default is the only profile listed. If not and you have a listing for HwProfile then select the HwProfile. Note: if you did delete the Corsair folder from Roaming before installing the latest CUE software, then there should be no HwProfile. Only the Default Profile should exist. 8. In the bigger box below the drop down box, click the three line icon next to the Default profile listing and click "Reset all Mode Settings to Default" 9. Next and be careful here, Next to the DROP DOWN BOX, now click the three line icon here and then click "Save Profile to Device Memory" (Note: Once you do this and save the reset profile to the mouse, you will notice what looks like microchip icon appear next to the Default listing and drop down box. This signifies that the default profile is now the profile that's saved to the mouse.) 9.1. It might be a good idea to reboot the computer, just for good measure. You never know. 10. Test your mouse again. If the click issue is still present, then your issue may be more persistent than mine and may require replacement or waiting for a firmware update. If the issue is gone, then you should be able to redo your custom profile settings and save them to the mouse using the method from step 9. Try this and let me know if it makes any difference. So far, since doing this, I've had no recurrences of the issue yet. But I don't want to speak too soon. But so far, it's looking good in my case. The steps I highlighted here are the exact steps I used when troubleshooting my mouse. Hope this helps. Let me know how you get on. Thanks for reporting back. That's great info and gives us extra room for ironing out wrinkles. This may show that some mice may still need full hardware resets regardless of CUE uninstallation.

Hi guys. I've been trying many things trying to narrow down the possibilities for the cause of the double-click issue in the M65 RGB mouse. I've been experiencing the same issue obviously. So I've tried many things and have been using the following site for subsequent click testing: http://textmechanic.com/Online-Tally-Counter.html Testing methodology: Click at a steady pace counting out loud and watch the counter. If it jumps, the problem still exists. Reset the counter by clicking clear all items. I've tried the following things trying to narrow down possible causes and testing. All of the following failed to resolve the issue: Tried different USB ports on different buses. Tried switching mouse to USB 3.0 interface. Tried turning off CUE (Corsair Utility Engine) Even tried setting CUE to not load with windows, turning it off and then rebooting the computer. Tried changing the polling rate Tried disconnecting Corsair USB Vengeance Headset and turning off software Tried turning off other running applications one by one to see if any software running on my computer could be isolated as a possible cause. None made any impact on fault. Tried disconnecting all other USB devices that could be causing a conflict one by one. None of these made any discernible difference. Next I disconnected the mouse from my computer and connected it to my laptop (Which is running Linux Netrunner) and went to the website and continued to test. After several hundred clicks, I could not reproduce the issue on the laptop. So I disconnected it from the laptop and plugged in back on my main computer and tested again. Problem was still there on my main computer. This means the issue is not likely to be with the mouse itself, but more likely with the CUE software and/or drivers or possibly something more specific to Windows (I'm running Windows 7 64bit Ultimate on my main computer). So I checked the device manager on my computer to ascertain what's currently installed for the mouse on my main computer. Here is the device map: http://i977.photobucket.com/albums/ae253/bignick277/DeviceManagerBefore.jpg~original Next I uninstalled the CUE software. Bear in mind, that even if you have the CUE software turned off on your computer and set to not autorun with Windows, there is still a driver component that is installed on your computer for the mouse (installed with CUE) that the computer uses instead of the driver windows automatically installs and uses when you plug the mouse in for the first time and before you install the CUE software. (It is important to bear that in mind to understand what happens next and how that may have an impact on the results of tests following the uninstallation of the CUE software.) During the uninstall process I took note of it uninstalling the drivers for the mouse. Then I checked the install directory to ensure that the CUE software was fully removed from the computer. For the record, the default directory the CUE software and drivers is the following: C:\Program Files (x86)\Corsair\Corsair Utility Engine Once the CUE was fully uninstalled, I found the CUE software settings and configuration data in the C:\Users\(Your Username)\AppData\Roaming directory and deleted the Corsair folder. I then rebooted the computer again, just to be on the safe side. On boot up I checked the device manager again, and this is the device map I got back: http://i977.photobucket.com/albums/ae253/bignick277/DeviceManagerAfter.jpg~original In case it's not apparant, here is an edited screenshot of the before screenshot to highlight the device manager entries that changed after the uninstallation of the CUE software and drivers. http://i977.photobucket.com/albums/ae253/bignick277/DeviceManagerBeforeDifferences.jpg~original So I went back to the click counting site and retested. After hundreds of clicks, I have not been able to reproduce the issue. As a result, this seems to have resolved the issue on my mouse. Here's where things get a little interesting, but it does seem logical given that this issue didn't appear initially until about a couple days "after" I originally set up my mouse. So I reinstalled the CUE software, rebooted again and retested. I have not as yet, been able to reproduce the issue. But I have gotten some weird results from the CUE software. All of a sudden, when I went to polling speed, it was at 125hz and claimed a mouse malfunction. When I set the mouse back to the correct 1000hz, it refreshed and it no longer claims there's a malfunction. I went to the profile page and changed the profile to the Hardware profile, but now all of a sudden, it's not listing a set setting for right click. And now for that reason, I couldn't right-click. So I reset the hardware profile to reset the default settings. Then I set my custom settings back and saved it to the mouse. Went back to the click testing site and tested again. Still can't reproduce the issue after hundreds of clicks. Now given, that this issue doesn't seem to surface until a couple days after setup of the mouse through the CUE. And simply reapplying your settings to the mouse seems to have no affect. But completely uninstalling, deleting software configuration and profile data from the C:\Users\(Your Username)\AppData\Roaming directory and reinstalling the CUE software, and then resetting the mouse and re-applying your custom settings does seem to fix the issue. However, and this is the big however. I can not guarantee that the issue will not resurface a couple days of use later if you keep the CUE software installed. The only way to know for sure, is to test thoroughly. And that's why I'm here. The more people who can test, the better. If you like the CUE software and wish to continue to use it, but are getting the double-click on left issue. Then try the following steps. 1: Fully uninstall the CUE (Corsair Utility Engine) software through Control Panel -> Progams and Features 2: After uninstallation, check to make sure that the CUE software folder was actually removed from the computer. Default Path = C:\Program Files (x86)\Corsair\Corsair Utility Engine 3: Go to C:\Users\(Your Username)\AppData\Roaming folder and delete the Corsair folder. This will remove all of saved software settings and profiles stored on the computer. You should especially do this if you're updating to the newest version of the CUE software. (Note: The AppData folder in Windows is hidden by default. To get it to show up, press the Alt key on your keyboard to get the explorer options to show (File, Edit, View, etc.). Click Tools -> Folder Options. Click the "View" tab. Under the section labelled "Hidden Files and Folders", select "Show Hidden Files, Folders and Drives". Click "Apply" and then click "OK". You will now be able to see the AppData folder in your user directory.) 4: Reboot your computer 5: Reinstall the CUE software. Download the latest version that was released over Christmas if you haven't already. 6: After installation, start up the CUE software and in the Device tab of the Settings Section, check to make sure the polling option is set to the correct setting. Default is 1000hz. 7: In the Profile tab, change default listing to HwProfile1 and check to make sure everything is set correctly. If it's not (such as the issue I had where right click's setting mysteriously disappeared), then left click the 3 lines icon next to HwProfile1 and click reset device to defaults. Once this is done, then reapply your preferred settings. If you can find no issues with the HwProfile1, you might be able to skip this step. It's your call of the level of testing you end up wanting to do. If you are unsure what hardware profile I speak of, you can see what I'm referring to in the following screenshot. It's one of the selectable profiles: http://i977.photobucket.com/albums/ae253/bignick277/CUE.jpg~original Note: If you are using the latest version of the CUE software that was released over Christmas and have deleted the Corsair folder from the AppData\Roaming directory, the "Default" profile will now be the profile that allows you to save your profile to the device. The HwProfile1 profile will no longer exist. 8: In the Profile tab, if you prefer to use software profile settings, then do the same as described in step 7, but also do it for your set software profiles. You may actually be able to skip this step, I don't know. 9: Test using the click counting site I highlighted here. If your issue is gone, great, but please post an initial post here saying as much. Then test over the next week through every day use. If the problem stay gone, great. If it comes back, bad luck. In either case, please report your week results here as well, as that is useful data for helping narrow down the cause of this issue. http://textmechanic.com/Online-Tally-Counter.html If you don't care for the CUE software and would rather just use the mouse with your profile settings permanently on the mouse and you've already properly set your hardware profile the way you like it. Then follow these steps. 1: Fully uninstall the CUE (Corsair Utility Engine) software through Control Panel -> Progams and Features 2: After uninstallation, check to make sure that the CUE software folder was actually removed from the computer. Default Path = C:\Program Files (x86)\Corsair\Corsair Utility Engine 3: Go to C:\Users\(Your Username)\AppData\Roaming folder and delete the Corsair folder. This will remove all of saved software settings and profiles stored on the computer. You should especially do this if you're updating to the newest version of the CUE software. 4: Reboot your computer 5: Test using the click counting site I highlighted here. If your issue is gone, great, but please post an initial post here saying as much. Then test over the next week through every day use. If the problem stay gone, great. If it comes back, bad luck. In either case, please report your week results here as well, as that is useful data for helping narrow down the cause of this issue. Note: In this scenario you will be testing using only the Windows default installed drivers. Not the corsair specific drivers installed by the CUE software. http://textmechanic.com/Online-Tally-Counter.html Analysis of what this could tell us. For the people who continue to use CUE and followed the instructions exactly. If updating to the latest CUE software by uninstalling the software, and then deleting the old version software profile data by deleting the data from AppData\Roaming. Installing the latest CUE software from the site and then resetting the mouse hardware profile before reconfiguring to your custom profile settings resolves the issue permanently, then this could prove that the issue was in the old software, but needed to be properly wiped clean and everything properly reset and cleared for the issue to be solved. Simply updating the software may not have been enough to solve the problem. If the issue only seems to be resolved by completely removing the CUE software and deleting the software profile data from AppData\Roaming and then running the mouse using hardware profile you saved to the mouse and then relying exclusively on Windows default HID drivers, then this could point to an issue with the CUE software and/or drivers itself. If neither of these scenarios resolves the issue, then the issue is most likely in the mouse itself. Either hardware or firmware related, and I we'll just have to wait and rely on Corsair to solve the issue. If both solutions work as permanent solutions, then this will tell us that the issue is with the old CUE software and needs to be properly removed and cleaned out before installing and using the latest CUE software and mouse hardware properly reset as highlighted in the first solution scenario. To those reporting results back to this thread, please highlight which solution you are attempting so we know which solution is definitely working and which is definitely not working. Please report back your initial results of whether or not it seems to have resolved the issue for the moment. After protracted use, if the issue comes back, please report it here. If the issue has not reasserted itself after 1 week, please report highlight that here as well. The more information the better. You guys/gals really are going to be the best source of testing data at this point. I can tell you right now, that I am going testing the first scenario for now. I may not like keeping the CUE software running at all times and prefer to run exclusively from hardware saved custom profiles, but I do like having the software installed so I can change the hardware settings at will, without having to constantly reinstall and uninstall the CUE software. If the issue comes back and persists, I will switch to testing the second scenario. But for the moment, for me at least, the issue seems to be resolved. I will report back if the issue returns and if it doesn't. OK guys. This is the best I can do for the moment. Until I can do more testing, there's not much more information I can provide at this point. But if this helps all of you and helps Corsair with a tangible direction to look at for actually fixing this issue or how to advise people who report this issue in the future, then that would just be great for everyone. Looking forward to seeing all of your results. I'll be reporting back when I have more results. I hope this helps and good luck :D: