K65 PLUS Wireless - 2b10

[UngraguGaming]

What kind of device is it?

Keyboard

What is the name of the device?

K65 PLUS WIRELESS 75% RGB Mechanical Gaming Keyboard

Link to Corsair's Product Page

https://www.corsair.com/us/en/p/keyboards/ch-91d401l-na/k65-plus-wireless-75-percent-rgb-mechanical-gaming-keyboard-ch-91d401l-na

Additional Details

Report lists it as being detected as follows:

Bus 001 Device 004: ID 1b1c:2b10 Corsair CORSAIR K65 PLUS WIRELESS Keyboard

There's also something I noticed about it's "bcountrycode" (I do not know what this is) being not supported.

I'm not sure if this is important or not, but I'll include this anyways. The keyboard has limited onboard memory in wireless mode, and as a result, it tends to default to preset lighting effects when not plugged in.

Generated Report

ckb-next-report-1715650343.gz

[MSalman6]

Hi, I've just received the keyboard, and it is very buggy (some keys don't work, and it makes auto inputs) when using the onboard memory. I've tried it on Windows, Ubuntu, and even on mobile.

It only works properly with iCUE installed on Windows and is completely useless everywhere else.

Is ckb-next only for controlling the RGB on the keyboard, or will it help in this case?

[ddc]

Hi, I've been using this same keyboard, but I haven't come across any of those issues you described. I'm most of the time on Linux.

Version is: CH-91D401L-NA Bus 001 Device 008: ID 1b1c:2b10 Corsair CORSAIR K65 PLUS WIRELESS Keyboard

ckb-next only for controlling the RGB on the keyboard would be nice

[wedgevic]

Hi, I've just received the keyboard, and it is very buggy (some keys don't work, and it makes auto inputs) when using the onboard memory. I've tried it on Windows, Ubuntu, and even on mobile.

It only works properly with iCUE installed on Windows and is completely useless everywhere else.

Is ckb-next only for controlling the RGB on the keyboard, or will it help in this case?

I have run into the exact same thing. Regardless of whether I'm on Windows, Linux, or even MacOS, whenever I press period or the right arrow, I get a consistent string of characters (none of which include the original character) unless I have iCue enabled. I'm hoping that this will allow me to fully use my keyboard since this has been really annoying me

maybe the string could be some sort of protocol meant to communicate with iCue, but I'm not sure

[MSalman6]

Hi, I've just received the keyboard, and it is very buggy (some keys don't work, and it makes auto inputs) when using the onboard memory. I've tried it on Windows, Ubuntu, and even on mobile.

It only works properly with iCUE installed on Windows and is completely useless everywhere else.

Is ckb-next only for controlling the RGB on the keyboard, or will it help in this case?

I have run into the exact same thing. Regardless of whether I'm on Windows, Linux, or even MacOS, whenever I press period or the right arrow, I get a consistent string of characters (none of which include the original character) unless I have iCue enabled. I'm hoping that this will allow me to fully use my keyboard since this has been really annoying me

maybe the string could be some sort of protocol meant to communicate with iCue, but I'm not sure

Force updating the firware from the iCue software for both the keyboard and receiver did fix the issue with the period key but now I have issue of frequent disconnections over the dongle although it sits very close.

You can also try resetting the keyboard by following relevant guide on their site

[earthly-alien]

I also have very frequent disconnects. To the point I have to keep the keyboard on wired mode, otherwise it's way too disruptive. Happens only on Linux, under Windows it seems fine. The only way to get it working again after it disconnects is by unplugging and plugging back the dongle.

[MSalman6]

I also have very frequent disconnects. To the point I have to keep the keyboard on wired mode, otherwise it's way too disruptive. Happens only on Linux, under Windows it seems fine. The only way to get it working again after it disconnects is by unplugging and plugging back the dongle.

Yes, I also have to unplug and plug the dongle to get it working again.

Though after the very recent firmware update it hasn't happened.

[earthly-alien]

I haven't tried yet (I just keep the kb plugged all the time now), but I'll give it a shot. Thanks for the heads up.

[wedgevic]

I have run into the exact same thing. Regardless of whether I'm on Windows, Linux, or even MacOS, whenever I press period or the right arrow, I get a consistent string of characters (none of which include the original character) unless I have iCue enabled. I'm hoping that this will allow me to fully use my keyboard since this has been really annoying me maybe the string could be some sort of protocol meant to communicate with iCue, but I'm not sure

Force updating the firware from the iCue software for both the keyboard and receiver did fix the issue with the period key but now I have issue of frequent disconnections over the dongle although it sits very close.

You can also try resetting the keyboard by following relevant guide on their site

I use the keyboard wired since I lost my adapter a while back, but unfortunately resetting it and re-flashing the firmware did not fix it for me. I will be opening a Corsair support ticket and update if they find any fix

Edit: The support was unfortunately not able to get it fixed, I'll have to RMA it

[earthly-alien]

I also have very frequent disconnects. To the point I have to keep the keyboard on wired mode, otherwise it's way too disruptive. Happens only on Linux, under Windows it seems fine. The only way to get it working again after it disconnects is by unplugging and plugging back the dongle.

Yes, I also have to unplug and plug the dongle to get it working again.

Though after the very recent firmware update it hasn't happened.

Unfortunately, even after updating firmware my keyboard still loses connection occasionally.