Shortcut of PT Run stops working

[mesteves]

Microsoft PowerToys version

0.87.0

Installation method

PowerToys auto-update

Running as admin

No

Area(s) with issue?

PowerToys Run

Steps to reproduce

After the upgrade when I try to launch any application as Admin (example Visual Studio), it doesn't launch it, and subsequent call to PT Run won't work, either by shortcut or even in the PT button for the effect.

✔️ Expected Behavior

PT Run to work as expected

❌ Actual Behavior

PT Run fails lauching app's in Admin mode, and after the first attempt, PT Run also fails to run and search does not open.

Other Software

No response

[similar-issues-ai[bot]]

We've found some similar issues:

• #19125 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[davidegiacometti]

/bugreport

[mesteves]

Attached the "report bug" file

PowerToysReport_2024-12-30-13-51-07.zip

[mesteves]

Related with #36643

[jennifer-grodner]

I'm running into this issue as well.

[bicole]

I'm currently seeing this issue as well with v0.88.0, with the default Alt+Space keyboard shortcut. I even tried changing it to Windows+R and I noticed that it is handled (in that Windows Run doesn't show), but the PowerToysRun popup never appears. Not sure if it's related to the other plugins I have configured or not right now. I also tried rebooting and resetting the keyboard shortcut, but the behavior remains the same.

Attached is my bug report.

I've noticed that PowerToysRun opens multiple instances as well (via TaskManager) and is NOT closed/killed when PowerToys is Quit via the taskbar shortcut menu. Not sure if this is related at this time. I will open a new issue once this is resolved if the multiple instances issue remains after this is fixed.

PowerToysReport_2025-02-12-13-58-22.zip

I was able to root cause the issue to be the use of the 3rd Party Winget Plugin for PowerToys Run. I'll open an issue with the plugin directly since this is no longer an issue unless I am using that plugin.