Open Trenly opened 2 years ago
Did this get fixed in WinGet 1.8?
Nope, issue persists on WinGet 1.8
List by ID:
~ winget list --id Microsoft.PowerShell
Name Id Version Source
-----------------------------------------------
PowerShell Microsoft.PowerShell 7.4.3.0 winget
List by name query:
~ winget list powershell
Name Id Version Available Source
-------------------------------------------------------------------------------------
PowerShell Microsoft.PowerShell 7.4.3.0 winget
PowerShell 7-x64 Microsoft.PowerShell 7.4.2.0 winget
Nope, issue persists on WinGet 1.8
List by ID:
~ winget list --id Microsoft.PowerShell Name Id Version Source ----------------------------------------------- PowerShell Microsoft.PowerShell 7.4.3.0 winget
List by name query:
~ winget list powershell Name Id Version Available Source ------------------------------------------------------------------------------------- PowerShell Microsoft.PowerShell 7.4.3.0 winget PowerShell 7-x64 Microsoft.PowerShell 7.4.2.0 winget
Out of curiosity, can you also try winget list Microsoft.PowerShell
without the --id
argument?
So I could not reproduce this behavior with all packages. For most packages, WinGet correctly displays all installed side-by-side versions, whether you list by name or use --id
. I could only reproduce this behavior with side-by-side versions that differ in installer type.
In the example above, the two installations of PowerShell are PowerShell MSIX and PowerShell MSI. I could also reproduce this with installing side-by-side versions of another package Coder.Coder, that offers two installer types: Nullsoft and Portable. (I'm sure there would be other examples, but these were the ones already installed on my machine)
@Trenly, and to answer your question, listing with just Microsoft.PowerShell
behaves the same as listing with --id Microsoft.PowerShell
i.e.,
~ winget list Microsoft.PowerShell
Name Id Version Source
-----------------------------------------------
PowerShell Microsoft.PowerShell 7.4.3.0 winget
Brief description of your issue
I am well aware of the uninstall issues with side by side packages and the CLI not being able to disambiguate between package versions. However,
winget list
shouldn't need to disambiguate and should be unaffected by side-by-side installs.Using
winget list <PackageId>
fails with side-by-side applications, even though listing by name succeedsSteps to reproduce
Install multiple versions of a single package identifier. Run
winget list <PackageId>
Expected behavior
All versions of the package identifier to be listed
Actual behavior
Logs.zip
Environment