Jump to content
Corsair Community

K70 RGB not detected by CUE on Windows startup


MrMustard
 Share

Recommended Posts

Dear friends at Corsair

 

I have recently bought me a new K70 RGB keyboard. As lovely as it is, I have had a few major problems with Corsair Utility Engine co-operating with my new keyboard.

 

When I start my computer, and log in to Windows, the Corsair Utility Engine detects my M65 mouse, but not my keyboard, so I have to take the USB's out and put them back in every time I start my computer in order to make CUE detect my keyboard.

 

Sometimes when I have locked my Windows and I lock back in, CUE may not detect my M65 mouse or my keyboard, so I have to reconnect them.

 

Is there any solution for this problem? I paid 179 euros for this keyboard, and I didn't expect it to make me reconnect it every time I start Windows. If there is no solution, I might return it to the store.

 

OS: Windows 10 Pro 64-bit

Motherboard: Asus m4a78-pro (all drivers are latest version)

Link to comment
Share on other sites

Have you tried a different USB port?

Is the BIOS up to date?

Are both USB ports from the keyboard connected to a USB 2.0 port?

Try the devices on another computer. Do they work fine?

 

I just tried plugging it into different ports and booting the computer, still wasn't recogniced on the startup. My BIOS should be up to date, and all the usb ports in my motherboard are usb 2.0. At the moment I do not have a spare computer to test my keyboard on, but I shall go try it on my friends's pc in a few days.

 

I have been wondering, whether the problem could be my old motherboard. I am renewing it in a few months, but could it be, that my motherboard is so outdated that it is conflicting with new softwares like CUE?

Link to comment
Share on other sites

I just tried plugging it into different ports and booting the computer, still wasn't recogniced on the startup. My BIOS should be up to date, and all the usb ports in my motherboard are usb 2.0. At the moment I do not have a spare computer to test my keyboard on, but I shall go try it on my friends's pc in a few days.

 

I have been wondering, whether the problem could be my old motherboard. I am renewing it in a few months, but could it be, that my motherboard is so outdated that it is conflicting with new softwares like CUE?

Try booting it up with only the keyboard USB plugged in, and not the extra one. Once Windows starts up, connect the second one so that lighting effects and stuff can work.

 

This should cause Windows to realize what's going on, and hopefully enumerate them properly in future boot-ups.

 

Also, if it's that message box that says "No device found" or something like that, it's a known issue with CUE. It bugs the heck out of me, too, but the keyboard actually works fine, and once CUE figures itself out it'll be okay. Just wait for a little bit and it tends to sort itself out.

Link to comment
Share on other sites

Try booting it up with only the keyboard USB plugged in, and not the extra one. Once Windows starts up, connect the second one so that lighting effects and stuff can work.

 

This should cause Windows to realize what's going on, and hopefully enumerate them properly in future boot-ups.

 

Also, if it's that message box that says "No device found" or something like that, it's a known issue with CUE. It bugs the heck out of me, too, but the keyboard actually works fine, and once CUE figures itself out it'll be okay. Just wait for a little bit and it tends to sort itself out.

 

I am still yet to try connecting my keyboard to another computer, but seems that starting my pc with only the keyboard usb and plugging the other one in later does not have any effect for future startups. It still requires me to plug it in and out when starting windows.

Link to comment
Share on other sites

Put the STRAFE into BIOS mode and see if that does anything.

 

To put it into BIOS mode.

Press F1 then the Windows lock button.

 

When the STRAFE is in BIOS mode, the scroll lock indicator will start flashing. To exit out of it, press the same keystrokes to get into it.

Link to comment
Share on other sites

Hello folks!

 

Same problem here, bought a new K70 RGB an ran into some issues.

 

When I boot my System, the K70 is not detected an can't be use. I've got the CUE message to update the Firmware, but when I start this updateprocess, It stops at 3%.

(Info: I have updated the Firmware a serveral times before)

 

But if I restart the CUE two times, the K70 works, also when I press serveral keys for 4 to 12 times.

When the K70 is detected and I reboot the system, there are no problems and the K70 works fine.

 

Next problem, I can't use the K70 during the bootmechanism (normal boot or reboot) to get into the Mainboard BIOS. Thats really bad...

 

I have replugged the USB to serveral ports, two USB 2, one USB 3 and USB 2 and only one USB 3. Reinstall the CUE, repair the CUE, nothing helps.

 

The CUE is "Corsair-Utility-Engine-v1.15.36",

the Firmware is "1.33"

and the Bootloaderversion is "0.11".

 

In Windows 10 "Zuverlässigkeitsüberwachung" (sorry I only know the german word) go to Windows CMD and type: perfmon /rel

I have found out, that the CUE installation was not successfull, each time I have installed it.

 

Here is the Logfile:

 

[2016-02-14T17:36:57]: UserSessionInfo: locked changed to 0.

[2016-02-14T17:36:57]: UserSessionInfo: connected changed to 1.

[2016-02-14T17:36:57]: UserSessionInfo: local changed to 1.

[2016-02-14T17:36:57]: UserSessionInfo: locked changed to 0.

[2016-02-14T17:36:57]: UserSessionInfo: connected changed to 1.

[2016-02-14T17:36:57]: UserSessionInfo: local changed to 1.

[2016-02-14T17:36:58]: UserSessionInfo: locked changed to 0.

[2016-02-14T17:36:58]: UserSessionInfo: connected changed to 1.

[2016-02-14T17:36:58]: UserSessionInfo: local changed to 1.

[2016-02-14T17:36:58]: Device profile (meta) for device vid=46d pid=c332 not found.

[2016-02-14T17:36:58]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13&mi_01&col01#7&28289304&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-02-14T17:36:58]: Device profile (meta) for device vid=46d pid=c332 not found.

[2016-02-14T17:36:58]: Device profile (meta) for device vid=45e pid=28e not found.

[2016-02-14T17:36:58]: Created new device object: K70 RGB; ready: 0

[2016-02-14T17:36:58]: Device profile (meta) for device vid=46d pid=c332 not found.

[2016-02-14T17:36:58]: Device profile (meta) for device vid=46d pid=c332 not found.

[2016-02-14T17:36:58]: Attached to device object K70 RGB: b=1 a=1

[2016-02-14T17:36:58]: Device profile (meta) for device vid=46d pid=c332 not found.

[2016-02-14T17:36:58]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13&mi_00#7&4515542&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-02-14T17:36:58]: Attached to device object K70 RGB: b=1 a=0

[2016-02-14T17:36:58]: Device profile (meta) for device vid=46d pid=c232 not found.

[2016-02-14T17:36:58]: Device profile (meta) for device vid=46d pid=c231 not found.

[2016-02-14T17:36:58]: Device profile (meta) for device vid=46d pid=c332 not found.

[2016-02-14T17:36:58]: Initializing K70 RGB...

[2016-02-14T17:36:58]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:36:58]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:36:58]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:36:58]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:36:58]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:36:58]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:36:58]: Initializing K70 RGB: spent all tries on getDeviceInfo().

[2016-02-14T17:36:59]: Initializing K70 RGB: failed.

[2016-02-14T17:36:59]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:36:59]: Initialized (st=0) K70 RGB.

[2016-02-14T17:36:59]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:36:59]: Device object failed to initialize, so it won't be registered with application susbystems. K70 RGB.

[2016-02-14T17:36:59]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:36:59]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:36:59]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:36:59]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:36:59]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:36:59]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:36:59]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:36:59]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:03]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:03]: Firmware Download: Failed to parse firmware version.

[2016-02-14T17:37:03]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:08]: Firmware Download: Aborting idle process not supported.

[2016-02-14T17:37:22]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:22]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:22]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:22]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:22]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:22]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:22]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:22]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:22]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:22]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:22]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:22]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:22]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:22]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:22]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:22]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:36]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:36]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

[2016-02-14T17:37:36]: Get device info failed. request timed out for K70 RGB

[2016-02-14T17:37:36]: Get device info failed.Device : K70 RGB,Execution result = 0, result = 0, platform error code = 995.

 

 

 

I don't know what to do, I'm very affine with computers but I can't understand this annoying problem...

 

Thank you and sorry for bad english.

Link to comment
Share on other sites

@fireback

 

To get into the BIOS look on the edge of the keyboard there should be a switch, move it to the end on the BIOS setting. Reboot and hit del as you would do normally.

 

The firmware being stuck on 3% is a common issue I just unistalled then reinstalled and picked the force firmware update from server option. Corsair really need to get their stuff together and sort these issues out.

Link to comment
Share on other sites

@fireback

 

To get into the BIOS look on the edge of the keyboard there should be a switch, move it to the end on the BIOS setting. Reboot and hit del as you would do normally.

 

The firmware being stuck on 3% is a common issue I just unistalled then reinstalled and picked the force firmware update from server option. Corsair really need to get their stuff together and sort these issues out.

 

Its not always Corsairs fault.... And they want to fix these issues but a lot of the times its hard to pin point what is causing which issue.

Link to comment
Share on other sites

I received my K70/RED/RED today and have spent the last two hours just troubleshooting the "No Device Detected. Please Connect a Device." issue in CUE. I have tried everything suggested on the forums and then some. I tried it on three different PCs with Win 7,8.1, and 10, different polling rates, different usb slots, system restore, device manager, updated every possible driver, tried old versions of CUE, have restarted and reconnected at each attempt, etc...

 

Edit: Alright so I was under the impression the K70 came with Macro support since Amazon decided to group all the K70s on one page. So what's the point of connecting the K70-non RGB via CUE if there is no extra functionality? If there isn't any and my keyboard works then I might just keep it.

Edited by KaSPY
Link to comment
Share on other sites

I received my K70/RED/RED today and have spent the last two hours just troubleshooting the "No Device Detected. Please Connect a Device." issue in CUE. I have tried everything suggested on the forums and then some. I tried it on three different PCs with Win 7,8.1, and 10, different polling rates, different usb slots, system restore, device manager, updated every possible driver, tried old versions of CUE, have restarted and reconnected at each attempt, etc...

 

Edit: Alright so I was under the impression the K70 came with Macro support since Amazon decided to group all the K70s on one page. So what's the point of connecting the K70-non RGB via CUE if there is no extra functionality? If there isn't any and my keyboard works then I might just keep it.

CUE does not detect the K70 non-RGB, and it doesn't have any effects/macros support either.

Link to comment
Share on other sites

  • 1 year later...
  • 3 months later...

I have the same issue and support cannot figure it out.

 

 

 

Dear friends at Corsair

 

I have recently bought me a new K70 RGB keyboard. As lovely as it is, I have had a few major problems with Corsair Utility Engine co-operating with my new keyboard.

 

When I start my computer, and log in to Windows, the Corsair Utility Engine detects my M65 mouse, but not my keyboard, so I have to take the USB's out and put them back in every time I start my computer in order to make CUE detect my keyboard.

 

Sometimes when I have locked my Windows and I lock back in, CUE may not detect my M65 mouse or my keyboard, so I have to reconnect them.

 

Is there any solution for this problem? I paid 179 euros for this keyboard, and I didn't expect it to make me reconnect it every time I start Windows. If there is no solution, I might return it to the store.

 

OS: Windows 10 Pro 64-bit

Motherboard: Asus m4a78-pro (all drivers are latest version)

Link to comment
Share on other sites

This did not work for me.

 

 

I don't know if someone posted it before, but I may have found an answer for some.

 

Disable all power saving options for your USB ports.

 

Google how to do it, its easy. Worked for me, where I tried everything.

Link to comment
Share on other sites

Dear friends at Corsair

 

I have recently bought me a new K70 RGB keyboard. As lovely as it is, I have had a few major problems with Corsair Utility Engine co-operating with my new keyboard.

 

When I start my computer, and log in to Windows, the Corsair Utility Engine detects my M65 mouse, but not my keyboard, so I have to take the USB's out and put them back in every time I start my computer in order to make CUE detect my keyboard.

 

Sometimes when I have locked my Windows and I lock back in, CUE may not detect my M65 mouse or my keyboard, so I have to reconnect them.

 

Is there any solution for this problem? I paid 179 euros for this keyboard, and I didn't expect it to make me reconnect it every time I start Windows. If there is no solution, I might return it to the store.

 

OS: Windows 10 Pro 64-bit

Motherboard: Asus m4a78-pro (all drivers are latest version)

I agree these keyboards are real expensive and need to have better support.

Link to comment
Share on other sites

  • 9 months later...
Someone mentioned a button/switch on the keyboard, I looked on the keyboard itself next to where the cable connects, low and behold I find a physical switch with the word BIOS next to it. After moving it back to 1, back in biz. I must have run something along it that moved it, or my cat who likes to lay in front of it moved it. I need to get in the habit of thoroughly inspecting my devices for physical switches as I found a mute switch on a headset of mine after more time troubleshooting than ideal.
Link to comment
Share on other sites

 Share

×
×
  • Create New...