PowerToys Run keyboard "Alt + Space" not working when switching from non Admin to Admin mode.

[ChayimEliazer]

ℹ Computer information

• Windows build number: 2004 19041.423
• PowerToys version: v0.20.1
• PowerToy module: PowerToys Run

PowerToy module:

📝 Provide detailed reproduction steps (if any)

1. Clicking "Alt + Space" When PC user interface language is "Hebrew"

✔️ Expected result

Should open the "Run Field Search Box"

❌ Actual result

Happens nothing

[crutkas]

and it works if it isn't in "Hebrew", correct?

[ndbeals]

I'm not using Hebrew (English Canada with English US fallback) and it only works when ran in user mode (without admin elevation).

Though for me, when running in administrator mode, no keyboard shortcuts work.

[LiorBanai]

Same version. tested both Hebrew an English. works correctly.
@ChayimEliazer , try deleting %localappdata%/Microsoft/powertoys content (it will reset the settings). I had issue with settings not working and reapplying them solve non responding key pressed.

Edit: Actually, running in Admin mode Alt+Space does not work (independent of UI language)

[LiorBanai]

the PowerToys settings UI running in admin mode ignores itself: the window context menu is opening and not the shortcut.
ALT + Space when the setting UI is not in focus works.

in Non admin mode PowerToys settings UI respects the settings and open the search box even when the window itself is in focus.

[ChayimEliazer]

and it works if it isn't in "Hebrew", correct?

After checking, the problem is also in English UI. The problem goes on and off by switching Admin and regular mode.

[ChayimEliazer]

the PowerToys settings UI running in admin mode ignores itself: the window context menu is opening and not the shortcut.
ALT + Space when the setting UI is not in focus works.

in Non admin mode PowerToys settings UI respects the settings and open the search box even when the window itself is in focus.

It does not work at all even when settings is not in focus.
I switched from Admin mode to regular mode and it did start working, then switched back to Admin mode and it was working exactly as you mentioned in all details, then switched back to regular mode and switched back to Admin made it stopped working at all again. Seems there's a bug in Admin mode.

And after checking the problem is also in English UI. The problem goes on and off by switching Admin and regular mode.

After it stopped working at all by switching from Non Admin to Admin I opened PowerToys via Desktop icon Then also clicked the system tray icon and it started working again, seems there's some bug insisting Admin mode.

[Gongxter]

I'm kinda having the same issue but it is more related to which application is currently in the focus/foreground and if it is run as Administrator.
@ChayimEliazer I Guess your PowerToys is running as Administrator. Somehow if and application with admin rights is in the foreground/focus Run is not getting triggered.
You can simply try this with google chrome, just run it once as Administrator and once without and try alt+space.
I have no solution or workaround for this.

[enricogior]

This problem is caused by the bug described in #5860

[jmahlers]

I have a similar issue. For me, when PowerToys is run in admin mode, the shortcut fails in any non admin mode window. It does work in windows with administrator privilege. When PowerToys is run in user mode, the reverse happens.

[jmahlers]

Upon reading #5860, I found a work around. Rather than using the restart as admin option, by closing PowerToys and running it as admin from the Windows menu (after waiting >10 seconds) the feature works.

A key part is waiting those 10 seconds. If opened immediately, the error continues.

[enricogior]

There are two scenarios for this problem:

1. PowerLauncher.exe is not started when PowerToys.exe starts, this is now tracked in [Run] PowerLauncher.exe is NOT running when PowerToys starts #9017
2. PowerLauncher.exe is running but not responding to the shortcut key, this is now tracked in [Run] PowerLauncher.exe is running, but the shortcut key doesn't work #9018

Closing this as duplicate, please refer to #9017 or #9018 depending on your case.
Thanks.