-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interception causes keyboard to become unresponsive if it is unplugged #93
Comments
If reconnecting many times, it's not supported in free version. See #25. |
This should definitely be mentioned in the readme. $2200 is a steep price and way out of my price range and it would have been nice to know about this issue prior to starting development. |
Hey @oblitum, why don't you simply create an unsigned driver? |
Unfortunately this means I'm back to square one on my project. |
While interception is installed on my computer; if I unplug and then re-plugin a keyboard, the keyboard becomes unresponsive. The lights still work, ICUE (Corsairs lighting service) still detects the keyboard, but no key-strokes work at all. I have to fully restart the system to get the keyboard to come back.
I am using Interception in a macro application I've developed that allows for a second keyboard to become a holistic macro keyboard. I am 100% confident that it is not my code that is causing the problem as the issue is present regardless of whether or not my application is running or has been run since the last time I restarted the computer.
Is there any fix for this or is anyone else running into the same issue?
Windows 10 Pro (v1903)
Corsair K70 RGB, Logitech 2 in 1 wireless track pad + keyboard.
Latest release of Interception.
The text was updated successfully, but these errors were encountered: