Jump to content
Corsair Community

K70 RGB - Saved profiles do not save hardware lighting despite overwriting onboard profile


Recommended Posts


Hardware lighting does not apply unless iCue is launched. This is despite saving the profile onto the first slot of the keyboard.

Device: K70 RGB MK.2

Steps to replicate:

  1. Open iCue
  2. Setup Hardware lighting for keyboard
  3. Go to Device Settings
  4. Save the profile with hardware lighting onto the first slot of the keyboard.
  5. Set same profile to Default in iCue
  6. Shut down computer
  7. Boot up computer

What should happen:

Keyboard should light up as per onboard profile


What actually happens:

Keyboard has no lighting, as if it was listening to Lighting Effects (which is blank) instead of Hardware Lighting.

I have to boot up iCue everytime to and go into Hardware Lighting to load up the effects I've saved onto the keyboard.

Also, whilst in iCue, if I click onto any other Corsair device, my Hardware Lighting disappears and I have to go back into the keyboard and select Hardware Lighting again to recall the settings.


Why this doesn't make sense:

Whenever I click away from Hardware Lighting, iCue itself says "save the current profile in your device memory if you want Hardware Lighting to work when iCue is off". That does not work.

What's the point of saving an onboard profile if you can't recall it after your turn off your computer or click anywhere else in iCue? 



This looks like a firmware or software issue, where saving an onboard profile seems to load Lighting Effects instead of Hardware Lighting. I've tested this by setting Lighting Effects and it does load that on start up. Hardware lighting needs a fix. 





  • Like 1
Link to comment
Share on other sites

  • 1 month later...

I just joined this forum to report this same issue. I built a new PC: Asus Crosshair VIII Dark Hero, Ryzen 5900x, Asus 6900 XT Strix, 32GB TridentZ 3600Mhz RAM, Sound Blaster AE-9, Seagate Firecuda 530, and a Corsair H150i Elite Capellix to which I added three LL120 fans from my previous build added to the radiator for a push/pull configuration,  all inside an Obsidian 500D SE RGB from my previous build. I am also using two Corsair branded RGB strips. They were on the other side of the case and I had forgotten about them. I moved them to the top and front of the inside of the case by the mobo and radiator, and connected them to the 12v aRGB header. So other than the RAM, all RGB is Asus or Corsair. All fans are connected to the Commander Core. The previous build had two corsair RGB nodes and a Commander pro, but I removed them for this build.

I am using the latest iCUE, and the latest Armoury Crate.  All of my Asus RGB components start up with the RGB settings set in Armoury Crate. However, the Corsair fans and the strips do not load with settings. The strips are through Crate, but are doing the same thing as the fans. I have to do what OP does to get my iCUE profile loaded. I also have to run Armoury Crate to get the Corsair led strips to sync up with the Asus Aura settings.  My previous build was working fine, with my iCUE profile loading up when I booted into Windows.  So it seems to be an issue with the latest version of ICUE and Corsair RGB components. It is annoying to have to boot up both programs to get the Corsair components to load the chosen RGB settings.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...