Issues with Corsair Peripherals?
Issues with Corsair Peripherals?
Hi there! I've been experiencing some problems with these Corsair accessories lately:
With the K70 MK.2 Keyboard, the volume wheel feels less responsive than before. It sometimes increases or decreases volume while scrolling, and I'm not sure if this is due to wear and tear. I've owned this keyboard since 2020.
With the Glaive RGB Pro Mouse, I encounter double-click issues, and the scroll wheel behaves similarly to the keyboard by randomly scrolling in the opposite direction at times. I've reset the mouse several times and reinstalled iCUE.
Lastly, with the SP120 Fans, the lighting occasionally malfunctions. They are connected to the rainbow wave lighting link so all peripherals share the same effect. However, the fans sometimes flash out or return to the beginning of the sequence unpredictably. This problem appears more frequently at times.
I've already sent a support ticket to Corsair, but I think they might just suggest reinstalling iCUE again. I was wondering if anyone else has faced similar issues and found solutions!
Thanks a lot!
Corsair mice come with specific problems tied to their models.
For example, the Corsair Sabre RGB mice may cause double or triple-click issues on the left click button after about a year of use, even though you only press it once. This has occurred with three Sabre RGB models I've owned. The first one to experience this was mine (being older), which I returned via RMA and received a replacement under warranty. My second RMA mouse also developed the same problem after roughly a year. My partner's Sabre RGB mouse showed the issue too, after about 1.2 years.
We stopped using those Corsair models and now prefer the Corsair Nightsword RGB mice.
The Nightsword RGB has its own distinct model-related quirks. Around one year of heavy use, the middle button no longer registers clicks—scrolling still works but the scroll button down fails. This has happened twice with two Nightsword RGB units. The first was mine, as I rely heavily on the middle button. I returned it under warranty and got a replacement. Since RMA processes can be slow, I bought another Nightsword RGB to use until the replacement arrives (I can't operate my PC without them). The second one now also shows the same problem; the middle button is inconsistent. After RMA succeeded, I acquired a brand new Nightsword RGB, but haven’t had time to install it yet (my second one still functions). My partner’s Nightsword RGB has not developed this issue, and she rarely uses the middle button.
It seems the problem might be related to wear and tear—loss of sensitivity or incorrect registering.
I also own a Corsair Strafe RGB with Cherry MX Silent switches, which I’ve used since early 2017 (about 8 years). I attribute some issues to spilling liquids on it, which has made the G button unresponsive (I’ve rewired the G key in iCUE settings). All other keys work properly.
Over time, only a few single-key problems have emerged. For instance, the red LED won’t activate with the correct Shift, and color distortion appears under A, F, C, M, left Alt, and right CTRL—easily noticeable when changing colors to white.
I do have a replacement keyboard (Corsair K100 RGB with OPX switches), but I haven’t replaced it.
My Strafe RGB keyboard still functions well overall.
My partner uses a Corsair Strafe RGB MK.2 with Cherry MX Silent switches, purchased in Q3 2019 (6 years old). She hasn’t reported any problems so far.
Of course, the headsets—specifically the Void Pro RGB USB and Void RGB Elite USB—have their own issues. The cables or rubber insulation parts tend to degrade over time. My Void Pro cable has been repaired multiple times, and my Void Elite headset also has a damaged cable patch. I still have a replacement headset (Void Elite), but haven’t changed it yet.
Other Corsair accessories we own—ST100 RGB for both of us and the MM800 RGB Polaris—have remained functional.
My main reason not to replace my peripherals is the iCUE update glitch. I’m currently on version 4.24.193, but when trying to upgrade to v5.x, the automatic updater fails, claiming I have an outdated version (v3.14) and can’t remove it. This process also erases all custom macros and settings. Setting it up is frustrating, especially if I switch to Windows 11 or 12 later.
This issue likely stems from iCUE itself.
For lighting peripherals, occasional glitches have appeared. Since I use rainbow wave for my keyboard (KB) most of the time, and iCUE crashes, the wave effect stops. I then have to restart iCUE manually.
Still, Corsair SP120 RGB fans are quite old.
🤔
They were released even before my Corsair ML120/140 Pro LED fans launched. My oldest ML Pro LEDs are from early 2017 and have never had any problems, even after many years.
I checked the original SP-series was released in 2015, while the SP RGB series came later in 2016.
In summary, nothing lasts forever.
Thanks for the update on this issue! It seems I’ve been using both the keyboard and mouse since 2020. (Checked my Amazon account quickly) It looks like the mouse might need a replacement. The keyboard is fine except for the scroll volume wheel, which I resolved by spinning it really fast—it seems to have stopped the problem.
Most of my other Corsair products are working perfectly, just a few minor hiccups here and there.
Appreciate the feedback!
I've mainly used Corsair products. My mk2 LP has worked without any problems, and I got it in 2020, but my experience doesn't represent yours. I'd agree.
@Aeacus
The wear and tear is probably the reason. Still, just to be safe, I'd try using the iCue uninstaller in the program folder and reinstall it fresh (not a repair). iCue can become very buggy over time, and this approach often fixes many issues.
Regarding the SP120, what profile did you select in iCue? Choosing SP RGB from the drop-down might cause fan problems. I saw a discussion on Corsair forums where someone mentioned selecting the 8-Led option to keep the fans working properly. It seems this is linked to older SP120 models. The newer versions don't have this option listed, so going with 8-led is recommended.
Do you use any other hardware with a different software package, such as Asus Armoury Crate? They can also affect functionality significantly. Stick to one or the other. iCue allows installing plugins for various manufacturers, so make sure you install the ones that match your needs.
Hey, good shout! I own an MSI 3080 and a NZXT Phantom AIO, both with their own lighting software that might be causing some issues. I'll check it out!
Setup is mostly straightforward—8-LED configuration works well. Initially, the SP fans didn't show up, which confused me. Since I use a Corsair 5000X, I added a few more SP Elite fans to complete the setup. Thanks for the help!
We also use NZXT CAM in our setups (managing AER140 RGB fans, HUE+ and LED strips), but it hasn't caused any conflicts with iCUE for us. Of course, that doesn't guarantee it won't in another system.
We also have MSI GPUs, yet I haven't set up the MSI app to manage the GPU LEDs (and my MSI monitor LEDs) because I prefer the default LED settings. Additionally, I don't want multiple software installations just to control different eyecandy, as that can lead to conflicts.
Regarding NZXT CAM, it tends to consume a lot of CPU resources. Even when it's not actively doing much, it still uses around 25% of my CPU compute power. That's quite significant.
Recently, after the OS boots and CAM loads, while loading my LED profile, I've decided to permanently close CAM. HUE+ maintains the LED profile even when CAM isn't running, and I don't need CAM to waste 25% of my CPU power for no reason (compared to iCUE, which uses only 3-4%).
I've already reported this to NZXT and they forwarded it to the dev team. After four or five updates, the problem still persists. Therefore, I'm considering opening a new ticket about it.
Are your devices equipped with internal memory? That was a clever way to bypass some issues. It meant I didn't have to launch conflicting software, so they remained in their default mode. Currently, fingers crossed, my ASUS motherboard is connected via iCue. Don't ask how—it just worked one day, and I haven't adjusted it since. I've been spending hours trying to solve it, and then suddenly it was fixed. Lol
Our mice (Corsair Nightsword RGB) also support it, as do NZXT HUE+ (which manages the LEDs of AER140 RGB fans and LED strips). Other Corsair accessories lack built-in memory and will return to their default settings when iCUE is closed (for example, KB marcos won't function, headset EQ profiles don't work, and surround sound won't operate).