vy-bot
commented
3 years ago Seen something that might have the same root cause. After pressing the lock button, one or more of the modifier keys seem to be "stuck" in the pressed position (CTRL for sure). Pressing CTRL fixes the issue.
This is not an issue when creating a custom lock button in admin mode using " \gl ". Unfortunately this doesn't lock the key. Maybe a custom modifier " \L " to lock the key? Would be nice, also could use it for extra security after login in some cases.
Environment: Windows 10, entry speed is set to 10, admin mode enabled.
Strange issue after updating the v2.1.0-prodc firmware. Was previously on v0.2beta8, and used the Lock Button feature without problem.
Running Windows 10
Also, the "?" tooltip popup info incorrectly describes the feature:
But the online manual correctly states the instruction as a single press (which I guess eliminates the use of the slot for that button). I choose button # 5. I have not set either slot 5a nor 5b.
Holding down the button per this tooltip does NOT lock the OnlyKey or the computer.
Tapping the button does still work to lock the OnlyKey and computer... but that is when something strange happens.
For a few minutes, I am unable to type keypad numbers (such as to unlock the system using a Windows Hello PIN) I have also noticed (by switching the unlock login screen to login as another user, typing into the non-masked username field) that caplocks are not reporting correctly on my USB keyboard. I am unable to toggle the Numlock unless I am holding down the shift key.
All of this weirdness seems to subside after about a minute or so. Longer if I had tried holding down the Lock Button on the OnlyKey a few times before finally tapping.
Removing the Onlykey does not fix this. Sysadmin mode is disabled too.
I am not sure what is causing this... but it is very strange behavior.
Perhaps OnlyKey is sending other non-character keystrokes during the Lock operation. Maybe to be cross compatible with MacOS?