-
Notifications
You must be signed in to change notification settings - Fork 1.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
Command line tools installed via winget not available in CMD.exe #3067
Comments
Make sure you restart cmd, it only picks up the environment on process start, so if parts of it, like the path, change afterwards, it's not going to know anything about it otherwise |
Sorry, I should have clarified. I opened a new window and this happened. I already know to open a new terminal window. |
@denelon You've improperly marked that issue as a duplicate of this one. It would be useful, yes, to have the environment updated right away to avoid having to restart the terminal, but I have restarted the terminal and these tools are seemingly on my path, yet Windows cmd.exe won't let me use them regardless. This is not an issue with me forgetting to restart command. I'm sorry, I should have clarified that at the beginning. |
it happened to me after installing ffmpeg with "winget install ffmpeg" Editing the PATH to worked for me |
Something tells me that the portable manifest might need to have some way to declare where the binaries are stored in the package, since they can have their own folder structure that isn't exactly the most standardized |
Duplicate of #2909 The fix is implemented in a PR and will ship in the next preview release of WinGet |
The fix (PR #3002) has made its way into WinGet v1.5.1081-preview release cc @denelon |
Brief description of your issue
Hello! I've attempted to install a few command line tools via winget. Specifically,
aria2c
,nano
, andffmpeg
. None are available in cmd.exe. I checked my PATH, and they do show up there:Steps to reproduce
I'm not sure. I just installed these tools and noticed they didn't work, then went looking in my PATH.
Expected behavior
I expected the tools on my PATH to be found by CMD.exe so I could use them.
Actual behavior
Despite appearing on my PATH, CMD.exe can't find them. This is really confusing, I have no idea how this could have happened.
Environment
The text was updated successfully, but these errors were encountered: