-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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 Run not finding PowerShell script shortcuts in User Start Menu #4212
Comments
Great catch, we'll work on this |
Thank you for reporting! I've created countless shortcuts in |
v0.19 fixed the issue for me. I can now find the shortcuts to PowerShell scripts in the tool. Thanks! |
I still have the issue, any shortcuts inside my user's start menu folder don't appear in power toys run results. |
@justanindieguy PowerShell script shortcuts, correct? |
Yes, that's correct. |
I just popped one on my desktop and it loaded in 0.21.1, @justanindieguy still an issue? |
Going to close this, if it isn't fixed, please comment. |
Environment
Windows build number: 10.0.19041.264
PowerToys version: 0.18.2
PowerToy module for which you are reporting the bug (if applicable): Run
Steps to reproduce
If you have PowerShell scripts (or other scripts) that you create shortcuts too and put in the Start Menu folder(s) they are not found.
Other apps in those locations are found. I have quite a few admin scripts that I can run from Windows 10 Search (Win + Q, just Win, etc.). For example, I created a folder in C:\Users\UserID\AppData\Roaming\Microsoft\Windows\Start Menu\Programs and created shortcuts to all of my PowerShell scripts in there. Windows 10 search finds them, PowerToys Run does not. Even after days (incase it was index timing) they are still not found.
Expected behavior
Anything in the Start Menu folders (All Users, Current Users) should be available to be run, including shortcuts, etc.
Actual behavior
PowerToys Run does not find shortcuts to PowerShell scripts (and maybe others, but the scripts are what I've tested on several machines).
Screenshots
The text was updated successfully, but these errors were encountered: