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
PowerToys steals my number keys! #410
Comments
Same issue. After installing my whole top row stopped working and after a keypress, it showed a Fancyzones layout for a sec. Top row meaning number keys for qwerty. |
I'm also having this issue. My keyboard is a Logitech PRO model Y-U0031 in case that's relevant. |
@Johannestegner @Misoun215 @zachalig When it happens again, instead of quitting PowerToys can you please follow these steps? |
@enricogior - I did as you suggested and my number keys worked after disabling the Shortcut Guide.
|
@zachalig |
It did it for me also. Thanks. Keep up the great work. Awsome program. |
Haven't had the time to test this yet, but it does seem very promising, will test asap and report back here :) |
@Johannestegner |
Seems to work here too! Thanks :) |
@Misoun215, @Johannestegner |
Oh, I did have to restart the application, but after that I haven't noticed the problem. Maybe just luck? |
@Johannestegner |
Absolutely, I'll let you know if it happens :) |
Also having this issue. I have to turn off FancyZones then turn it on again to fix it. |
Hi @VincentJoshuaET |
I'm also having this problem, I never noticed it on v0.11, but I've had it on v0.12 and now on v0.13 |
I had this issue with 0.12, even with the shortcut guide off. (I turned the shortcut guide off shortly after install. Still had the issue.) Just downloaded 0.13. Haven't seen the issue yet, but it's only been installed for about 5 minutes. |
Hi @Fifteen15Studios |
Can also confirm this is still happening on 0.13, even with the shortcut guide off. |
I have this issue on 0.12.0 and 0.13.0 on a second monitor. |
Yeah, keep on happening here again too on 0.13.0. |
Also, I know one way for me to reproduce it... Whenever I start "Neverwinter Online" my num-row dies if the tool is running. Could it be connected to DX or something like that? |
Grrrrrrr! I've no idea how, but the "Hold Shift Key" turned itself on again. (?) Changing the setting wasn't enough to de-hijack (the settings stuck, the bug continued), nor was exiting and re-starting the program. A reboot solved it. Very odd. |
One more clue maybe: I only have FancyZones enabled. When this occurs for me, if I hit shift + any number, the zones flash briefly. Could this be tied to shortcuts to swap active zones layout? Because there is a setting to flash them when this happens. Or maybe just keyboard shortcuts in general, where some state or handler can get stuck, therefore always intercepting number keys. |
Hi @MHHenriksen |
Same problem on Asus Zenbook UX370UAR, windows 10 home 1903 18362.476 The problem also affects external keyboard. The strange thing is that i can use my numbers on the lock screen to unlock windows via pin, but i immediately lose my numbers when i'm into windows. |
Not so strange, I'd say. That sounds like a password snooping protection mechanism :F |
I have this issue as well, and now found a way to reproduce it for me: |
Hi @iSnackyCracky |
Any chance that release will be happening soon? I love the new PowerToys, but I have a triple monitor setup with one in portrait, using PT to make two 50% zones top and bottom, and I use Chrome and often drag tabs from one window/monitor to another. This issue has been driving me NUTS, and I've been watching this issue like a hawk hoping for a resolution. Thanks for the great revamp on a nostalgic project! |
Hi @WillPresley |
This was probably fixed by #673, marking as "resolved". |
Ah I'm so glad I finally found this. I thought it was an issue with my Logitech G Hub software! |
Can confirm... also happening for me. |
So far I haven't experienced this issue anymore since I upgraded to v 0.14. |
This is now fixed in PowerToys 0.14.0 https://github.com/microsoft/PowerToys/releases |
Got this bug in 0.20.1 version. I didn't have ShortcutGuide and FancyZones enabled. Tried to switch on/off this settings, but it helped for only for a short time (~10 sec). |
Just want to chime in here for those of you scratching your heads like I was when seeing a bunch of results about PowerToys, and you have PowerToys installed but not running. Even if the program is not running (i.e. it's not in the system tray, and even if you launch the program and shut it down again) it may still be the reason you've lost functionality. Uninstalling PowerToys and reinstalling it fixed the issue for me, but if it comes back I will be trying the other solutions listed here while the team continues to address the core issue. |
@AeroDeveloper |
Sorry to resurrect this issue, but just reporting that I saw this in 0.59.1 - may have happened when performing the update from 0.59.0 to 0.59.1 - I did the update but didn't reboot the system afterward and it was stuck in the state described here. Once I rebooted, it seems to be fixed. I did disable the Shortcut keys PowerToy, but FancyZones is the main reason I'm using this. And nothing changed it (not disabling anything, not closing the program, nothing until I reboot the system. And of course, sadly I cannot reproduce now. Will report back if it happens again, but for now, for anyone stumbling across this issue, in addition to toggling different ones on and off, make sure your app is in a stable state and try turning it off and on again. |
The problem still occurs : | |
Description
From time to time while using my computer, PowerToys disables my numb-keys (the normal keyboard ones not numbpad).
I'm quite sure that it is PowerToys due to the fact that when I turn it off, the keys are working as usual again.
I have yet to find the reason or a way to reproduce it, but I will update this issue if/as soon as I do.
Environment
Microsoft Windows [Version 10.0.18362.356]
PowerToys 0.11.0
Steps to reproduce
None found yet.
Expected behavior
Number keys working as usual.
Actual behavior
Number keys not working at all.
The text was updated successfully, but these errors were encountered: