Display the path to an installed package

[sohang3112]

Description of the new feature / enhancement

After installing a package using winget install <PACKAGE>, running winget show <PACKAGE> should also show the absolute path of the installed executable.

Proposed technical implementation details

winget show <PACKAGE> outputs several fields (like Version, Description, etc.) describing the package.
Another field Installed Path should also be added, that shows the absolute path of the installed executable.

[Trenly]

I don’t know that this should be included in show, since show is used to display information from a manifest or other source. However, I could definitely see this being a useful option for winget list, if it were configurable through user settings and off by default

[denelon]

We have some work coming up to:

• Improve Uninstall Confidence #2252

For that feature, we are considering adding a path to main executable. That would likely help in this case.

[wmstack]

I suggest that the subcommand should be called which, or at least that both which and show should be aliases for the same command. For example, that is how it is in Scoop, and that is how e.g., Linux does it with the which command. Having a show command alone would be counter-intuitive to already-existing users of other package managers, which is not ideal. Which (pun) is historically how binaries where located in Linux, and so I think that is the most appropriate name for the command.

[fredx30]

This thread was the first hit when i went looking for a default install dir for winget. 📦 👍

[alex-jitbit]

I agree, I just installed winget install ntop and it took me ages to realize that winget had just thrown it into %LOCALAPPDATA%\Microsoft\WinGet\Packages\gsass1.NTop_Microsoft.Winget.Source_8wekyb3d8bbwe silently, without adding any PATH. Had to run an entire disk search.

[denelon]

There are some subtle behaviors here. I'll try to clarify them just to help everyone's understanding.

Use case 1:
If you are in "Administrative" mode when you install, or if you have "Developer mode" enabled, WinGet creates a symbolic link in a common directory to the package.

Use case 2:
If you are in "User" mode, then we have to add unique entries to the path per package.

In either case, the first time you install a portable package, the package will not immediately be available on the path. You will need to restart the terminal to be able to run the package.

For use case 1, after you have installed the first portable package and restarted the terminal, the path entry for the symbolic links is in place, so subsequent installations shouldn't require a terminal restart.

For use case 2, we have to add unique path entries, so each portable package will require a restart of the terminal to get the refereshed "Path" environment variable.

[alex-jitbit]

@Danelon I did restart the Windows terminal. I even checked the PATH env manually, the program was still not there. I don't know if it's winget or the package author, but providing a way to manually investigate problems like this manually would be helpful

[denelon]

I ran winget install ntop in user mode in Windows Terminal (PowerShell).
I was given the message that I needed to restart my terminal.

I restarted and ran ntop.

If this isn't the behavior you're seeing (in user mode), please run winget --info and share the results, then run wignet install ntop --verbose-logs and share the results.

Do you have developer mode enabled or disabled?

[alex-jitbit]

@denelon I can confirm that after restarting Windows Terminal completely (not just closing the tab and opening a new one) it works as expected. Sorry I wasted your time and thanks for the help.

[denelon]

No worries. 😊
I know there are several subtle things impacting what we all want as the "best experience". I'm always open to digging in, troubleshooting and helping clarify what the product can and cannot do. The path environment variable has been one of the trickiest ones to deal with properly. I've put comments on several different issues attempting to clarify everything.

Honestly, I'm happy people care enough to complain and point out our weaknesses so we can help everyone fall into the "pit of success". I'm not shy about tackling hard problems, but there are always infinite wants and limited resources.

[MyrddinE]

I just installed Python via WinGet, and am unable to easily tell where the executable was installed. Unlike ntop, it doesn't modify the path itself. Moreover, I have multiple Python versions installed, and having the path discoverable would be very useful to me. It seems a notable oversight that this piece of information is unavailable.

I believe a command-line tool should have command-line centric information (like the path) more readily available.