Razer Cynosa Chroma number key double pressing+issues downloading software | Razer Insider
Skip to main content

I’m having issues with my number “6” key automatically pressing the “5” key as well. So anytime I want to press the “6” it comes out as “56”.
I’ve tried it on a different computer, different ports, unplugging for awhile and replugging, cleaning with air etc. I was going to try to reinstall the drivers but they get stuck on the first screen saying to plug the device into the computer- the keyboard is plugged in directly via the cord, and unplugging and plugging back in while the update is up does not register it.

I’d appreciate some help with this, the keyboard doesn’t qualify for official support anymore. It’s not detrimental since it’s just the one key,  but it’s really annoying. 

I also posted - same keyboard, same issue. My numpad 6 is generating *6 and my 9 is generating 93. Worked just fine for 2 months.

 

Very bad business. In my case, makes the keyboard worthless since I need to do so many numpad entries.

 

Hard to justify even investing in a Razer product down the road. First and last I guess.

I also posted - same keyboard, same issue. My numpad 6 is generating *6 and my 9 is generating 93. Worked just fine for 2 months.

 

Very bad business. In my case, makes the keyboard worthless since I need to do so many numpad entries.

 

Hard to justify even investing in a Razer product down the road. First and last I guess.

My issue is not with the numberpad 6, but with the 6 key that’s in the top horizontal bar. I was using the keyboard for almost 2 years without issues though, and my main keyboard is also a Razer BlackWidow and I’ve had no issues with it for nearly a decade. So I don’t think it’s  brand thing, but maybe it was a model issues- I think the Chroma Cynosa was their first fore into the multi-tonal keyboards instead of just the straight green ones.

I also posted - same keyboard, same issue. My numpad 6 is generating *6 and my 9 is generating 93. Worked just fine for 2 months.

 

Very bad business. In my case, makes the keyboard worthless since I need to do so many numpad entries.

 

Hard to justify even investing in a Razer product down the road. First and last I guess.

My issue is not with the numberpad 6, but with the 6 key that’s in the top horizontal bar. I was using the keyboard for almost 2 years without issues though, and my main keyboard is also a Razer BlackWidow and I’ve had no issues with it for nearly a decade. So I don’t think it’s  brand thing, but maybe it was a model issues- I think the Chroma Cynosa was their first fore into the multi-tonal keyboards instead of just the straight green ones.

My keyboard is fixed. The fix is to open it up, clean up contacts and reset the ribbon connector(s) for any keys glitching. I had to do this twice, but the second time is holding good. I watched 3 or 4 YT videos about the issue, which taught me how to disassemble the keyboard, remove the membrane, clean the contacts, and remove then reset the affected ribbon connector for the trace array that controlled my numpad.

This is not a software or firmware issue - don’t go down that rabbit hole. It’s electrical connections and circuitry. I believe the ribbon connectors for the 4 or 5 different key arrays do not make good connections - therefore vibrations and/or jolts to the keyboard can knock them out of critical alignment.

Search YT for ‘Cynosa chroma typing fix’. Make sure to watch any that go over ribbon connector cleaning/resets.

None of these are likely under warranty any longer, so you have nothing really to lose. The fix can take up to an hour or longer, but the bulk of the time is digging out all of the screw covers and unscrewing the hidden screws (there’s 15).

I’ve taken apart thousands of things in my lifetime, so this was a breeze for me. Doesn’t make it any less aggravating, though, and I didn’t enjoy wasting my entire night - but ultimately it IS fixed (for right now).

YMMV, and I’d be happy to assist you (or anyone) who is having any issues doing this fix.

Cheers

I also posted - same keyboard, same issue. My numpad 6 is generating *6 and my 9 is generating 93. Worked just fine for 2 months.

 

Very bad business. In my case, makes the keyboard worthless since I need to do so many numpad entries.

 

Hard to justify even investing in a Razer product down the road. First and last I guess.

My issue is not with the numberpad 6, but with the 6 key that’s in the top horizontal bar. I was using the keyboard for almost 2 years without issues though, and my main keyboard is also a Razer BlackWidow and I’ve had no issues with it for nearly a decade. So I don’t think it’s  brand thing, but maybe it was a model issues- I think the Chroma Cynosa was their first fore into the multi-tonal keyboards instead of just the straight green ones.

My keyboard is fixed. The fix is to open it up, clean up contacts and reset the ribbon connector(s) for any keys glitching. I had to do this twice, but the second time is holding good. I watched 3 or 4 YT videos about the issue, which taught me how to disassemble the keyboard, remove the membrane, clean the contacts, and remove then reset the affected ribbon connector for the trace array that controlled my numpad.

This is not a software or firmware issue - don’t go down that rabbit hole. It’s electrical connections and circuitry. I believe the ribbon connectors for the 4 or 5 different key arrays do not make good connections - therefore vibrations and/or jolts to the keyboard can knock them out of critical alignment.

Search YT for ‘Cynosa chroma typing fix’. Make sure to watch any that go over ribbon connector cleaning/resets.

None of these are likely under warranty any longer, so you have nothing really to lose. The fix can take up to an hour or longer, but the bulk of the time is digging out all of the screw covers and unscrewing the hidden screws (there’s 15).

I’ve taken apart thousands of things in my lifetime, so this was a breeze for me. Doesn’t make it any less aggravating, though, and I didn’t enjoy wasting my entire night - but ultimately it IS fixed (for right now).

YMMV, and I’d be happy to assist you (or anyone) who is having any issues doing this fix.

Cheers

Thank you for the information, it’s unfortunate to hear that’s what you had to do to fix it 😕.
I will save your post for reference in case it starts bothering me enough to try it- thank you for your time!

Reply


CookiesCookie settings