You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new experimental feature listDetails enables a new option for the list command, --details. When supplied, the output is no longer a table view of the results but is instead a series of show like outputs drawing data from the installed item.
An example output for a single installed package is:
> wingetdev list Microsoft.VisualStudio.2022.Enterprise --details
Visual Studio Enterprise 2022 [Microsoft.VisualStudio.2022.Enterprise]
Version: 17.14.21 (November 2025)
Publisher: Microsoft Corporation
Local Identifier: ARP\Machine\X86\875fed29
Product Code: 875fed29
Installer Category: exe
Installed Scope: Machine
Installed Location: C:\Program Files\Microsoft Visual Studio\2022\Enterprise
Available Upgrades:
winget [17.14.23]
When there are multiple results, the identity line is prefixed with the standard (N/M) format string used in multi-package operations elsewhere.
If sixels are enabled and supported by the terminal, an icon for the installed package will be shown. This currently models the mechanism used by winget-pkgs to extract the icons and by the show command to select the appropriate one to display. It is using the same code in the same manner and should be representative of what would be shown to the user if it were doing the full round trip through the repository/cache/show command.
I'm finding that winget show doesn't sixel icons any longer, but winget list --detailsdoes? was that intended (and related to this PR?)
winget show is reliant on the winget-pkgs validation+cache service to extract icon information and merge it into the resulting manifest. If there are issues in that complex chain of events there may not be an icon available to show.
winget list --details leverages the same code that is run during validation's detonation phase to extract the icon, but does so on your local machine in real time. Seeing an icon with list --details means that this code is working for the install and so it probably should work for the package in winget-pkgs... but again there are many more moving parts to get that icon out to the world.
Totally makes sense. Chatted with Demitrius - sorry to randomize you John!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Issue-FeatureThis is a feature request for the Windows Package Manager client.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
microsoft-github-policy-service
bot
added
the
Issue-Feature
Change
The new experimental feature
listDetailsenables a new option for thelistcommand,--details. When supplied, the output is no longer a table view of the results but is instead a series ofshowlike outputs drawing data from the installed item.An example output for a single installed package is:
When there are multiple results, the identity line is prefixed with the standard
(N/M)format string used in multi-package operations elsewhere.If sixels are enabled and supported by the terminal, an icon for the installed package will be shown. This currently models the mechanism used by winget-pkgs to extract the icons and by the
showcommand to select the appropriate one to display. It is using the same code in the same manner and should be representative of what would be shown to the user if it were doing the full round trip through the repository/cache/showcommand.