Xploder270

Why on earth would you even prompt me to auto-update to iCUE4, even though my trusty VOID Wireless isn't supported anymore?

Thank you for your response. Can you forward my request of adding Void support to the decision makers please?

Void Pro\Void Elite seems to even use the same USB dongle. Please Corsair, explain why you don't support the original version anymore. I have many Corsair products but that is something that is definitely putting me off. They even built in support for third party products like Asus SDK and Nvidia SDK and can't manage to have their own stuff in there? My Void is not even 4 years old at this point (bought new on Amazon in May of 2017) and shows no signs of age. unacceptable...

Why wouldn't you support the Void Wireless anymore? Is it that different from the Void PRO/Void Elite? Really disappointed :(

Looks like this has been fixed server-side, as checking for updates is working for me now.

I can't update my firmware in iCUE anymore. After launch it says that there's a firmware update available for my Commander Pro but I can't download it and in fact cannot check or download any firmware for my devices (using STRAFE RGB, Void and Commander Pro). Error message is "The firmware update is not available or failed to load for []" Using iCUE 3.18.77 but I had the same problem last version. I already reinstalled iCUE and wiped my settings in the process. I can use the updater when downloading a firmware for my Strafe manually. Unfortunately, there's no manual update available for the Commander Pro. Running Win10 1903 Release Preview Ring. Disabled Windows Firewall. Logs: 2019-07-29T10:28:32 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image" 2019-07-29T10:28:32 I cue.firmware.index: "Commander Pro" firmware update, expected version: 0.9.212 update available, on device: bootloader: 0.5 firmware: 0.8.210 2019-07-29T10:28:32 C cue.common.download: Cannot (re)open ' '! 2019-07-29T10:28:32 C cue.firmware.download: Image download failed.

The temperature sensor on my Commander Pro shows 2 decimal places now. Other than that? :dunno:

I'm having this problem with Division 2. After a play session, the iCUE client is either just frozen/crashed or I can't apply settings to my Commander Pro (new fan curves can be set but they never get applied while sensors/rpm still update). Restarting the corsair service doesn't work for bringing back control for my CP. I need to reboot. Division 2 runs at 100% CPU a lot and sometimes lags out other applications like Discord. This could be the culprit. I have iCUE SDK disabled and don't use the iCUE integration ingame. This happens with both stock iCUE and CPUIDSDK dll's renamed.

There is absolutely no difference within USBDeview before and after CUE launch/disconnect sound. I also refreshed the program to be sure.

Same exact issue here and I've described the issues this causes in the USB problems thread (http://forum.corsair.com/v3/showthread.php?t=167807) Here's a screenshot of USBDeview running if this helps: http://imgur.com/35L1F5t Running CUE 2.15.83