eds89

I was on version 5.9.105 and had this issue. Did a manual check for updates (looks like I was quite behind as version 5.11 was available), and after the update the entry in startup items reappears and it now works as it should. Perhaps the auto check for updates was also broken in that version, so not only did it have this startup issue, but it wouldn't automatically update to a version that resolved it?!

Perfect thank you very much!

Hi, I have an RM650i with a type 4 pro cable kit, and was wondering if these would all work with an HX1000i? Compatibility page says HX1000i is type 3 for 24 pin, but online people have said it is in fact type 4? Not sure which is true. Cheers Eds

Was there ever a solution for this issue, as I still randomly get it from time to time. Minor, but majorly frustrating!

I do apologise. I thought I was trying to save a profile that had static lighting, however I was accidentally selecting a profile with "animated" lighting in. Selected the right profile and bingo, it works :)

How can that be true, when I used to be able to do it with normal CUE? I would be able to set one specific profile as the default to be stored on the device. The fact there is a button that specifically says: "Save static lighting, DPI, and performance to device" would suggest Corsair thinks it is possible. The fact that the keyboard comes with the default rainbow wave pattern on the device and can be displayed before you ever even install CUE kind of indicates that as well surely?

Using iCUE, I have tried to save my lighting profile to my device as default profile stored on device memory. Every time my machine turns on however, keys remain un-illuminated until iCUE starts. Anyone else see the same issue?