Powertoys: Windows Walker activates with Windows-Z

Created on 2 Apr 2020 · 9Comments · Source: microsoft/PowerToys

As well as the standard hotkey Ctrl-Windows, I already have another shortkey for Windows-Z which now both get triggered. Where can I remove the shortkey Win-Z for Windows Walker please?

Windows 10

Environment

Windows build number: [run "ver" at a command prompt]
PowerToys version: 
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Expected behavior

Actual behavior

Screenshots

Needs-Author-Feedback Product-Launcher

Source

Rolograaf

Most helpful comment

@Rolograaf
Put
#MenuMaskKey vkFF
anywhere in your script. (though for sanity's sake, best at the top)
The ctrl-key is the default masking key, it is sent so as to not trigger the win-startmenu.

This sets the masking key to something that's not assigned to anything.
vk07 will open the GameBar at least since January, so that's why that advice no longer works.

DavidGretzschel on 5 Apr 2020

❤1 👍1

All 9 comments

To make sure I understand your question, do you mean that Window Walker is invoked on your machine when you do the combination Win + Z?

betsegaw on 3 Apr 2020

@Rolograaf
Did you use AutoHotkey to turn win+z into a shortcut for something?
Because AutoHotkey will send out extraneous ctrl+presses with windows+shortcuts, which then will trigger WindowWalker since this happens when the windows-key is still depressed.

https://autohotkey.com/board/topic/20619-extraneous-control-key-presses-generated-by-or-hotkeys/

In any case, I don't do anything with win+z and I can't trigger WindowWalker with it on 0.16.
However this little script is giving me the same problems:
#q:: run, explorer.exe %USERPROFILE%\Desktop
#w:: run, explorer.exe %USERPROFILE%\OneDrive
#e:: run, E:\

DavidGretzschel on 4 Apr 2020

Okay sorry, did not expect it was a AutoHotKey bug, since I used that script without issues before WindoWalker...

Rolograaf on 4 Apr 2020

Thanks for confirming that I was right with it being AHK.
Would have been really embarassing, if I guessed wrong here :)
Not so much an AHK-bug, but just some odd behaviour that usually doesn't cause issues.
Except until now with the Rise of PowerToys, I suppose.
I made a discussion about this here:
https://www.autohotkey.com/boards/viewtopic.php?f=76&t=74220&p=320784#p320784

DavidGretzschel on 4 Apr 2020

👍1

Okay I found that this should be a new option to solve this, but I am not sure how
https://documentation.help/AutoHotKey-Functions/_MenuMaskKey.htm

Rolograaf on 4 Apr 2020

@Rolograaf
Put
#MenuMaskKey vkFF
anywhere in your script. (though for sanity's sake, best at the top)
The ctrl-key is the default masking key, it is sent so as to not trigger the win-startmenu.

This sets the masking key to something that's not assigned to anything.
vk07 will open the GameBar at least since January, so that's why that advice no longer works.

DavidGretzschel on 5 Apr 2020

❤1 👍1

Put
#MenuMaskKey vkFF

Works Perfectly, Thanks for this practical powertoy!

Rolograaf on 6 Apr 2020

This was a super helpful thread as I was having the exact same problem having mapped an AutoHotKey command to: Windows-Z. Although this solved my issue, I'd like to suggest that an enhancement is considered for WindowWalker: don't hard-code Windows-Ctrl - allow the user to configure the Hot Key combination that makes Window Walker visible.