Monstieur

I've had this issue even before the firmware update. The solution was to unplug the fans, power on & off, and plug in the fans again. I had to do this a few times till all the fans were detected. It's been stable ever since.

Same issue with my Dark Core RGB Pro SE and the new M65 Ultra Wireless as well. The scroll wheel sensor cannot handle higher speeds and slows down.

iCUE crashes for me whenever I change the default output device from MacBook Pro Speakers to my RME Fireface UCX II. If the default devices is already changed, iCUE won't launch at all. I don't know why iCUE is messing with audio to have such a dependency.

This issue is still unresolved with the last iCUE update.

I'm guessing this is temperature related and the LEDs flap after expanding / contracting during storage. In my case the defective LED stated working after I tapped it a few times and applied pressure on it. It didn't fail again, but I returned the kit several days later because this binned Dominator B-Die kit couldn't even do 4000 C17 unlike my cheap B-Die Vengeance 3200 C16 kit.

iCUE crashes instantly when I change my audio output device on macOS from MacBook Pro Speakers to RME Fireface UCX II. It's messing with the audio system when it shouldn't be. I cannot launch iCUE at all while my RME Fireface UCX II is the selected output device as iCUE crashes on launch.

The link to v4 for macOS is somewhere on the forums. The iCUE homepage for macOS has not been updated from v3.

I tried the latest iCUE v3 and recently upgraded to iCUE v4.

I have a MacBook Pro 16-inch 2019 and am running macOS Big Sur fully updated. My Dark Core RGB Pro SE and the wireless dongle are successfully detected, but the K100 is not. Everything is connected through a Thunderbolt dock, and the K100 works fine on Windows through the dock.

When is macOS support for the K100 expected? I cannot configure the keyboard or use functions like Sniper mode with the G keys on macOS as the K100 is not detected in iCUE v4.

I have the same problem. I can't configure it on macOS as it isn't detected in iCUE v4.

I can now select individual keys in Hardware Lighting. Previously Hardware Lighting always affected the whole keyboard. This was an annoyance because the rear LEDs reflected on my TV when not using my PC. I can now disable them. I'm not sure if this is a firmware feature or iCue 4 feature. I also see 8000 Hz as a polling rate.

Corsair.Service.exe keeps querying the registry and opening files every second. The memory usage also bloats from 20 MiB to 1450 MiB in a few hours. I've attached a log file from Procmon.

Connecting them in parallel should be easy enough with the right adapters. A series connection would require modding the other end of the RGB strip.

I just bought a CMT64GX4M4K3600C16 from Amazon and one of the LEDs has a purple tint and appears dim. All colour combinations are tinted on that LED. I'm returning it until this issue is confirmed fixed.