Repository navigation
Commands should be available to the console after install #222
Description
Activity
For some reason, it looks like
ghisn't available directly in thePATH. It worked for me when I opened a new powershell window.This is likely do to the session needing reloaded. Basically, it added it, but your current PS session doesn't know about it yet. This is normal (same thing happens in all *nix shells).
That being said, it would be nice if
wingetautomatically refreshed the path. Maybe a flag could be added to the manifest file to trigger this.Another option would be to provided a command like
winget session refresh. This is what Chocolatey does (Update-SessionEnvironmentorrefreshenv)Reacted by Rain Sallow (/u/ta11ow), Garett Bass, Josh Parsons, Gabriel Machado, Caltor, Gavin Ray, Fujita Hitoshi, Manish Kumar ⛄, Kim Walisch, Bryan Hoang and 15 moreDan Horrigan (@dhrrgn) I think that you're correct because when I opened a new PS Core shell today, it worked as expected. I was confused yesterday because I opened a new tab in Windows Terminal after installation and received the same error message. When I opened a new and independent PS Core shell, it worked as expected today.
Regarding what you said about *nix above, if I use
dnforaptto install an application, the application is available for immediate use and doesn't require a new window. Are they doing something akin to what you suggest above?- changed the title
[-]GitHub CLI installs but isn't available on path[/-][+]Commands should be available to the console after install[/+]on May 20, 2020 Dan Horrigan (@dhrrgn) is correct, we don't currently reload the session. I'm going to change the title to indicate the feature request.
I ran into a similar problem when trying to install python:
winget install pythonAfter the Python installation wizard launched and finished, the tool reported:
Successfully installed. Butpythonwas not automatically added to my path (reloading the session didn't help here, running$ pythonin the terminal takes me to the "Get Python" page in the Microsoft Store), though thepython.exewas installed to the following location:C:\Users\<username>\AppData\Local\Programs\Python\Python38Am I missing a switch when running the
installcommand above?Reacted by ian Bearman, Poopooracoocoo and Marcin HoroszkoRegarding what you said about *nix above, if I use
dnforaptto install an application, the application is available for immediate use and doesn't require a new window. Are they doing something akin to what you suggest above?I'd imagine that's because they are adding symlinks to a location already on the
PATH, such as/usr/local/bin, so there is no need to update thePATH.Reacted by Yurij MikhalevichActually, I have installed vim, meld and a few other applications and rebooted my computer but still the commands are not available.
Reacted by Akshay Kumar, Blake Chambers, Michael List, Max Coplan, ping and Md. Iftakhar Awal Chowdhury- added this to the milestone
on May 28, 2020 Related #361
After the Python installation wizard launched and finished, the tool reported: Successfully installed. But python was not automatically added to my path (reloading the session didn't help here, running $ python in the terminal takes me to the "Get Python" page in the Microsoft Store), though the python.exe was installed to the following location:
This is now a year later and it looks likewinget install <python>is still broken. Am I missing a workaround? Do I need to open a ticket to the maintainers/repo of the Python package?Reinstalling with the latest Python package (now 3.10) seems to get everything into PATH as expected! Not sure if the fix was within
wingetor within thePythonpackage itself, but I am grateful for the fix regardless! For reference, I ranwinget install Python.Python.3.I have the same problem with GnuWin32.make. Successfully installation but it will not add make to the path automatically. It is seen in the list so it was installed. Is this now a thing, that needs to be changed in winget or in make itself to make this happen?
Reacted by Max CoplanChrizzly (@Chris2011) - While I can't give a definitive answer on this (I'm not a contributor or maintainer), I do think signs point to this being the responsibility of the package itself. So I think the action would be to go to the package maintainer and see about updating the install script for this package.
Reacted by ChrizzlyAaron ("AJ") Steers (@aaronsteers) ok, thx for your opinion :).
Reacted by Aaron ("AJ") SteersSo I think the action would be to go to the package maintainer and see about updating the install script for this package.
Anyone know if there's an easy way to do this in a WiX installer?
This package may help:
winget install WingetPathUpdater winget install github.cli gh # <-- works!It works by adding
winget.cmdandwinget.ps1wrapper scripts, which handle updating thePATHfor you.See also: https://github.com/jazzdelightsme/WingetPathUpdater
Reacted by Tim Balasavage, Choristor, Red, soredake, Jonathan Chemla, Carlos Domingues, Olav Rønnestad Birkeland and Carles Cufí- removed this from the milestone
on Nov 14, 2024 - added a commit that references this issue
on Dec 10, 2024 Duplicate of #549
Somehow back in the day, I missed this one which is the only reason I'm duping it to a newer issue.
microsoft-github-policy-service commented
on Jun 10, 2025 ContributorHello @Tim Balasavage (@tbalasavage),
We've identified this as a duplicate of another issue or PR that already exists. This specific instance is being closed in favor of the linked issue. Please add your 👍 to the other issue to raise its priority. Thanks for your contribution!
Template: msftbot/duplicate/closed
Brief description of your issue
I've installed the GitHub CLI and then attempt to run it but it fails each time.
Steps to reproduce
winget install github.clighExpected behavior
ghbrings up GitHub CLI info.Actual behavior
An error is produced
Environment
Any other software? No