Sinceabout a day now, the 6, 8 and 9 number keys (the ones on top of the keyboard, the numpad works fine) only sometimes produce an actual input. However they to work if they are held down as another key is typed and also sometimes they just randomly work for a few seconds.
I don't believe it is a hardware or firmware fault with the keyboard but some kind of software issue as it is resolved by a reboot. I know that there is an option that can prevent the keys on the numeric keypad from working as normal while controlling the mouse pointer but not of anything that could affect the normal number keys.
To clarify why I don't think it is a hardware fault, this is happening infrequently; only three times in the last while and each occurrence has been at least a week apart. I don't see how the keyboard would work fine for ages then suddenly exhibit this behaviour only to work fine again after a reboot.
If you happen to have a Logitech Mouse, it seems that using the Game Detection option (from the logitech gaming app) messes up with this particular section of the keyboard when switching via alt+tab from game apps to desktop too frequently and in a short period of time.
I've noticed this because when i got the mouse (502 Hero), i was using the internal storage option, therefore, i had to manually change the profile and since i didn't know how to add a key to a mouse button (i.e, change dpi function to a letter or number from top keyboard), i think there was no scenarios to make this problem to happen.
My solution in short was just switching the game detecion option to internal storage, top number keys started to function properly again without needing to restart anything, switching viceversa (internal to game) didn't make this problem to reappear. But as a side note i think this can be avoided by not abusing of alt+tab when using different profiles
Update: After shutting down my pc this issue happened again, i forgot that I did exit all razer apps i currently have (synapse and cortex) before doing what is above, therefore, it seems that this issue is related to keyboard management apps, after exiting razer apps again the issue is fixed again.
One thing I recall and noticed last night while trying to fix this is that the keyboard tab (where you can manage keyboard functions, macros, gaming mode and hypershift) in razer synapase, was not working as i wasn't been able to switch profiles, there were no profiles showing, unable to change standard to hypershift.
I checked my laptop keyboard and all of these keys work if directly using my laptop keyboard. if I enable Caps lock from my laptop then the "A" LED on my K70 does illuminate. When I disable Caps lock from my laptop the K70 "A" LED is extinguished. Same goes for num lock.
There have been no other events to trigger a change in behavior from my keyboard, no liquid spills or similar. I uninstalled and reinstalled iCue, to no avail. I "Forced" a K70 firmware update inside iCue but all that does is reinstall the latest firmware 3.24, which I believe is the issue, and no change in behavior.
I have this same problem as well. certain keys like my insert, delete, home, end, pgd, pgu, num, /, ent stopped working. the only solution was to put the k70 keyboard into BIOS by holding down F1 and the lock button above F4 for like 5-10 seconds and puts it into bios settings then it works. We need a fix for this corsair. Thanks!
Close iCUE completely. Go to Bluetooth and other devices in your system settings. Scroll down until you see CORSAIR K70 (or any) Keyboard. Click the device and select Remove device. When asked if you want to remove the device, click Yes. After CORSAIR iCUE K70 (or any) is removed, open iCUE. Open Device Manager from Control Panel. Click Action and select Scan for hardware changes. See if you see anything change in iCUE
It just so happens that I have another K70 RGB MK2 keyboard attached to my sons laptop, only it works perfectly fine. His laptop is using the same iCue software v5.7.106 as well as the same keyboard firmware v3.24. This is really baffling and annoying. I can only deduce that my laptop must have something different that is causing this issue.
OK, so the "BIOS" mode idea does work for me as well. After holding down the F1 and windows lock buttons for about 7 seconds I saw the prompt "installing new device" and clicked on it. The Bluetooth and other devices window opened. While my PC was "installing the new device" I noticed that it removed the K70 keyboard and then installed it again. Once this installation was completed my keys now behave normally again, SWEEEEET.
One thing though, the scroll lock LED is blinking repeatedly, about 1/2 second on and off. Also, I'm seeing the default key rainbow scrolling color pattern. I guess this means that the keyboard is still in "BIOS" mode. I repeated the key sequence F1+lock to disable BIOS mode but that rendered my keys back to the same issues as before.
There are now quite a few complaints about this popping up on the entire K68/70/Strafe family that all share a similar layout and likely very similar firmware and CUE mechanics. I connected my K70 MK.2 LP to see if I could replicate, first with no CUE running (normal operation) and then with CUE 5.7 active. It needed to install the module for the K70 LP and successfully did so. Thus far, no issues with the aforementioned keys.
I don't know what this is. Clearly there is an issue as a dozen different people show up in the same 3-4 day period after a new CUE release. However, the 3.24 FW is old and I don't think that's it. I was surprised my K70 LP was running it already as I have not used it in almost a year. BT and BIOS mode will separate the KB from CUE and I have to think the origin of the problem lies there. You might also quit CUE from the task bar or task manager and see what happens. Generally CUE originating issues stop when the software is not active.
Everyone affected should send in a Support Ticket about the issue. If it's not an automatic issue with every K68/70/Strafe, then they need to find out why and that likely means logs from you. You can turn on debug logging in the CUE gear settings, although I don't think it's going to be generating clear errors there.
The other thing you can try is the ESC key "soft reset" detailed in the general troubleshooting sections. That's the other easy user tool aside from the forced firmware flash. However, doing so will erase the KB onboard memory with your saved profiles, so if you are able to function normally without CUE running I would skip this step to maintain your current level of functionality.
I had this problem as well, I found the following posts on Reddit, and discovered that the Citrix Workspace app was the problem. After uninstalling and rebooting all the keys on my keyboard (k95) were working again!
There definitely was an issue with Citrix at a prior point in time. Hopefully that has not re-appeared, but if you all are running Citrix then that certainly is an avenue of investigation. That also might be part of this since it does not seem to be universal. Could be a specific common program everyone is using or a specific Win 10 build (?), although I think that is less likely.
Had the same problems, what a pain. Read these replies, and deleting Citrix worked for me. I'm so glad that fixed it. I have Windows 10 and a K70 RGB Rapidfire keyboard. This seems to be a very uncommon issue? Very specific. We all should send a ticket about this, interesting that the specific app Citrix can cause such a problem.
And in other channels I'm up to 4 people who have now confirmed they have this issue and Citrix installed. It looks like this is a live issue again. If you terminate CUE or set it not to run on start up, that should get you by in Hardware Mode for now. Corsair and Citrix will need to work this out again.
I had the problem that my WASD keys would only allow one keystroke input even though the key was being depressed. The cursor arrow keys were not working at all. Uninstalled Citrix Workspace and now working fine.
I had to reinstall Citrix workflow app this morning for work, downloaded a version dated 5th Oct for Windows, there was a later version, but I thought i'd start with that. Anyhow it did not affect the keyboard, here's hoping it stays that way now
I am running Ubuntu 10.04, fully updated, from an external USB hard drive.Everything works really well, except the keyboard. The numeric keypad is not working. The keys don't do anything, with or without NumLock on.
I'll post another answer because it took me ages to figure it out. It appears that things have been moved around a bit in recent releases. The "Mouse Keys" tab wasn't there in my Keyboard preferences (Ubuntu 11.10, gnome shell), so @JavierRivera's solution set me on the right track, but didn't solve the problem of turning off the "control pointer using keypad" option. This is where I did find it:
3a8082e126