Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Side-By-Side] List by package identifier fails #2726

Open
Trenly opened this issue Nov 28, 2022 · 4 comments
Open

[Side-By-Side] List by package identifier fails #2726

Trenly opened this issue Nov 28, 2022 · 4 comments
Labels
Area-Matching Issue related to correlation between installed package and manifest Issue-Bug It either shouldn't be doing this or needs an investigation. Side-by-Side Issue related to side by side package installation

Comments

@Trenly
Copy link
Contributor

Trenly commented Nov 28, 2022

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 succeeds

Steps 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

PS C:\WINDOWS\system32>  winget list microsoft.windowssdk
No installed package found matching input criteria.
PS C:\WINDOWS\system32>  winget list windowssdk
No installed package found matching input criteria.
PS C:\WINDOWS\system32> winget list "Windows software development kit"
Name                                                      Id                   Version          Available
------------------------------------------------------------------------------------------------------------
Windows Software Development Kit - Windows 10.0.18362.1   Microsoft.WindowsSDK < 10.0.22000.832 10.0.22621.2
Windows Software Development Kit - Windows 10.0.19041.685 Microsoft.WindowsSDK < 10.0.22000.832 10.0.22621.2
Windows Software Development Kit - Windows 10.0.22000.832 Microsoft.WindowsSDK 10.0.22000.832   10.0.22621.2
Windows Software Development Kit - Windows 10.0.22621.1   Microsoft.WindowsSDK 10.0.22621.1     10.0.22621.2
PS C:\WINDOWS\system32> winget list Microsoft.WindowsSDK
No installed package found matching input criteria.

Environment

PS C:\WINDOWS\system32> winget --info
Windows Package Manager (Preview) v1.4.3132-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.2251
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.3132.0
@ghost ghost added the Needs-Triage Issue need to be triaged label Nov 28, 2022
@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage Issue need to be triaged labels Nov 29, 2022
@denelon denelon added this to the v1.5-Client milestone Feb 14, 2023
@denelon denelon added Area-Matching Issue related to correlation between installed package and manifest Side-by-Side Issue related to side by side package installation labels Feb 22, 2023
@denelon denelon modified the milestones: v1.5-Client, v.Next-Client Jun 6, 2023
@denelon
Copy link
Contributor

denelon commented Jul 3, 2024

Did this get fixed in WinGet 1.8?

@denelon denelon added the Needs-Author-Feedback Issue needs attention from issue or PR author label Jul 3, 2024
@mdanish-kh
Copy link
Contributor

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

@Trenly
Copy link
Contributor Author

Trenly commented Jul 6, 2024

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?

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention Issue needs attention from Microsoft and removed Needs-Author-Feedback Issue needs attention from issue or PR author labels Jul 6, 2024
@mdanish-kh
Copy link
Contributor

mdanish-kh commented Jul 7, 2024

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

@denelon denelon removed the Needs-Attention Issue needs attention from Microsoft label Jul 9, 2024
@denelon denelon removed this from the v.Next-Client milestone Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Matching Issue related to correlation between installed package and manifest Issue-Bug It either shouldn't be doing this or needs an investigation. Side-by-Side Issue related to side by side package installation
Projects
None yet
Development

No branches or pull requests

3 participants