Jaybonaut

3.15.101 does not fix it.

Found out if I just flip the switch on the back to another position and then back, it reactivates and works. Ugh.

No dice on the update. It seems completely random. Sometimes one reboot will do it, sometimes 2 reboots will not see any devices.

Numlock is lit, the other two are not. EDIT: noticed there was an update. Updating to 3.14.104. Firmware is still 3.08. I will reboot and check back tomorrow.

Setting is 1 on a K70. No.

Killed iCue.exe, Corsair.Service.CpuIdRemote64.exe, Corsair.Service.DisplayAdapter.exe, and Corsair.Service.exe. I then relaunched iCue, which reactivated all the others, No Device Detected (after confirming on boot that's how it started. Rebooting again to see if I get lucky (seems to be 50/50.) Is there a way to delay it during boot perhaps that might ensure it works?

Is it called the CorsairService? I can confirm the 3.14.100 update does not fix the issue.

Yeah I don't get it.

Good, glad others are chiming in with this issue, hopefully a resolution is on the way.

Seems random. I assume there is a bug with the software. I can boot and have it not detect, reboot, it's fine, next boot, fine, next boot, not detected, reboot, fine, etc.

Nope, nevermind. Upon another reboot

Seems to be working after additional reboots. Weird.

I have a RGB K70. iCUE is 3.13.94, firmware is now 3.08. I think I was running 2.xx and an older firmware although I don't know what version it was prior to the update. On a whim I thought I would look up new profiles as I had been running the same one for quite a long time. This led to me checking for those two updates (firmware and software) through the iCUE software I had. Now all of a sudden I am running into this issue listed in the topic. I have uninstalled it and reinstalled, repaired, etc. The one thing that works is going into Device Manager and uninstalling the 'Corsair composite virtual input device.' Upon reboot it works..... ...however, upon the next reboot it does not. I have to repeat the process. Is there anything I can try? Running Win 10 1809. I would appreciate any assistance. Do I need to dig into the registry? etc. :sigh!: