fightinfilipino

seeing this problem too, ONLY on USB devices plugged into the headers on the Commander Pro. right now i have a Lightning Node pro plugged in to the Commander Pro USB header. system specs: Asus Crosshair VIII Dark Hero; 5950x; 32GB 4x8 Corsair Dominator RGB kit; running v3801 BIOS (due to there being other issues with 3904); latest chipset drivers from AMD site (not Asus). have tried: 1) PCIe to 3.0 (did not fix) 2) setting Lightning Node pro to not shut off in USB device settings (did not fix) 3) moving devices off the Commander Pro and directly plugging them to Mobo headers (this is the only option that works in my current setup) i’m about ready to throw in the towel and buy an internal powered USB hub. and i was considering not getting Corsair parts after hearing of everyone else’s bad experience with iCue, the H110 nonsense, and other bad reputational stuff i’ve been reading on Corsair lately, but i already had a Corsair keyboard and was already on the iCue ecosystem. now i feel like i made a huge mistake. support team folks: if we’re still under warranty, can we ask Corsair to replace the Commander Pro with a Lighting Node Pro and be done with it? would rather just get the USB hub from somewhere else instead of dealing with Corsair denying any issue on the Commander Pro.

in terms of constructive feedback - can your hardware and software teams in the future make your products such that this kind of obsolescence for Corsair RGB products does not happen? i get EOL for products is a thing, but considering how fragmented RGB platforms on PC are already, things like this just make it worse. i am less likely to buy Corsair because of things like this.

i know this is an old post, but just wanted to comment that this tip is GOLD. it fixed the issue i was having with my M65 RGB mouse not being detected on startup AND it seems to have fixed some other odd USB device issues.

i'm having this exact same problem on my Win10 machine. it occurs when my monitor automatically turns off for power saving. disabling and enabling the "SDK" option fixes the problem temporarily, but it reoccurs when the monitor turns off again from power saving.

why don't these come default with Corsair's keyboards? considering that other high end manufacturers (Ducky, Coolermaster, Vortex, to name a few) include PBT keycaps for the same price point as Corsair's main line, this seems like a corner-cutting choice.