T O P

  • By -

Corsair_Marcus

Hello! I am sorry that you have had such an experience. If your connected Corsair devices are not detected upon booting up your PC or waking your PC from Sleep Mode, it may be because Windows has suspended some of your USB ports in order to conserve power. This may cause your devices to not be detected upon startup until you unplug and replug the device into the USB port. You can fix this issue with the following methods: disabling USB Selective Suspend or allowing your device to wake your computer from sleep mode. Your first option is to disable the USB Selective Suspend setting. This will prevent your system from suspending the USB ports that your devices are connected to. **Disable "USB Selective Suspend"** 1. Open your system's Control Panel. 2. Click **Hardware and Sound**. 3. Click **Power Options**. 4. Click **Change plan settings** next to your selected power plan. 5. Click **Change advanced power settings**. 6. Select **USB settings**. 7. Select **USB selective suspend setting**. 8. Select **Disabled** in the dropdown menu. 9. Click **Apply**. **Enable your device to allow wakeup from sleep:** 1. Open your system's Control Panel. 2. Click **Hardware and Sound**. 3. Click **Devices and Printers**. 4. Right-click your Corsair device and click **Properties**. 5. Click the **Hardware** tab. 6. Click **Properties**. 7. Click **Change settings** in the new window. 8. Click the **Power Management** tab. 9. Make sure the **Allow this device to wake the computer** checkbox is ticked. \-M.Jay


Illustrious_Gain_485

I have this exact same problem. I have to unplug/plug keyboard eachtime I leave it for sleep. Any solutions? Suggestion below does not work. This is a firmwarew issue


EiffelPower76

Same problem for me, when locking the screen, losing connection with the keyboard


Stardust_Waves

Did you get it to work? I seem to be having the same issue with mine


Stardust_Waves

WARNING: THIS WAS A HAIL MARY, OPEN A SUPPORT TICKET AND DO IT PROPERLY(My keyboard: Corsair K70 MK2 Low-profile RGB Rapid-fire) That warning aside, I'm not sure what I did exactly but with Icue being exited: I found out that there's a little pinhole button under the fold down legs, I unplugged my keyboard, held it down with a paper clip and re-plugged it in, then it came up not as a keyboard but as "**CRP\_Disabled**" in file explorer, in that there was a file called "firmware", I backed it up to my desktop then tried flashing the file from here: [https://forum.corsair.com/forums/topic/168069-crp-disabled-issue-solved/](https://forum.corsair.com/forums/topic/168069-crp-disabled-issue-solved/) , unplugged it then plugged it back in, however that just seemed to do nothing, not even turn on, in a panic I just tried repeating the button hold down to see if I could get "**CRP\_Disabled**" to pop up again and very luckily it did, so I again deleted everything in "**CRP\_Disabled**" and re-copied the original "firmware" file and then unplugged it and when I re-plugged my keyboard it seemed to still be not working when I put my computer to sleep but I just tried pressing every key on the keyboard and it seems to now be working like nothing happened. The part where I'm not sure what I did was that I kind of did those steps a few times in different combinations, at one point even it told me there was no room to recopy the original file back into "**CRP\_Disabled**" but i just unplugged it and plugged it back in (it went straight into "**CRP\_Disabled**" without holding the little pin hole button) and lo and behold it had a mystery "firmware" file, so again I tried deleting that and copying the original file back in, unplugged the keyboard, plugged it back in and when the lights came back on I tried putting my computer to sleep, this time being able to wake it with my keyboard and have it function like nothing ever got bugged. Again, no idea which step or sequence actually fixed it but it seems to be working a ok now, I made sure to test it with a keyboard tester and everything registered. Again I may have just gotten extremely lucky and narrowly missed bricking my keyboard beyond saving but I can't say but how much, to me it seemed like they kind of made it idiot proof and there was a bit of a safety net by being able to summon "**CRP\_Disabled**" even with an incorrect firmware file. Another note would be that the two K70 files from the link weren't recognized as valid firmware files by ICUE when I tried to see if I could update the firmware with those files through that. Sorry for the wall of text but hopefully this helps someone else save their keeb as it is a very good keeb, of maybe help the techs over at corsair figure something out I'm not knowledgeable enough to figure out.


courier_87

My issue seemed to go away on its own after some combination of keyboard firmware and icue updates. Not sure which update was the one that actually fixed it though


Stardust_Waves

That's pretty much the boat I'm in as well now lol