Details output option for list

[JohnMcPMS]

Change

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.

[denelon]

[florelis]

Why not just call the version that takes a container after this?

[DHowett]

I'm finding that winget show doesn't sixel icons any longer, but winget list --details does? was that intended (and related to this PR?)

[JohnMcPMS]

I'm finding that winget show doesn't sixel icons any longer, but winget list --details does? 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.

[DHowett]

Totally makes sense. Chatted with Demitrius - sorry to randomize you John!

[eabase]

💔
Doesn't show Install location on all apps!

# winget list --details -e 'dotPDN.PaintDotNet'

Paint.NET [dotPDN.PaintDotNet]
Version: 5.1.12
Publisher: dotPDN LLC
Local Identifier: ARP\Machine\X64\{B33D3774-REDACTED}
Product Code: {b33d3774-REDACTED}
Upgrade Code: {04a40f40-REDACTED}
Installer Category: msi
Installed Scope: Machine
Installed Architecture: X64
Installed Locale: en-US
Origin Source: winget

[JohnMcPMS]

💔 Doesn't show Install location on all apps!

# winget list --details -e 'dotPDN.PaintDotNet'

Paint.NET [dotPDN.PaintDotNet]
Version: 5.1.12
Publisher: dotPDN LLC
Local Identifier: ARP\Machine\X64\{B33D3774-REDACTED}
Product Code: {b33d3774-REDACTED}
Upgrade Code: {04a40f40-REDACTED}
Installer Category: msi
Installed Scope: Machine
Installed Architecture: X64
Installed Locale: en-US
Origin Source: winget

@eabase If you run reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{B33D3774-REDACTED} (replacing the part that you redacted), does it show an install location? I can't show you if they don't record it.