“Command Not Found" cannot detected my powershell

[Yeson38]

Microsoft PowerToys version

0.77.0

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

General

Steps to reproduce

I updated my powershell to 7.4.0 weeks ago

but it didn't detected

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Other Software

Powershell 7.4.0

[jaimecbernardo]

Interesting, might be because you have a release candidate?
What do you get if you type in $PSVersionTable in your PowerShell? Can you please get a screenshot of that as well?
And by the way, is Command Not Found working for you?
/needinfo

[Yeson38]

[Tosch-IT]

Check whether the directory where the pwsh.exe is located is included in the path variable. I also had a Powershell profile in Windows Terminal without the pws.exe directory in the path variable, and "Command not found" couldn't find it either. After I added it, Powershell was detected by “Command not found”.
Alternatively, if Powershell 7 was installed from the store, uninstall Powershell and reinstall it via Winget. It doesn't seem to work with the version from the store (yet), even if powershell was recognized.

[Starstrike]

I'm experiencing that same issue that Tosch-IT mentioned. I use the store version (because store updates it easily and I don't need to manually install updates). Even though I can open a cmd and type pwsh.exe to start powershell, PowerToys can't find it. Is there any workaround for this besides uninstalling the store version and using a version that has to be manually updated?

[Yeson38]

这是来自QQ邮箱的自动回复邮件，以确保您发送的邮件已经收到，请勿重复发送。谢谢您的邮件，并祝您生活愉快。This is an automatic reply which means your email was received. Please do not send it repeatedly. Thanks for your email ＆ wish you a good day.