microsoft / microsoft/winget-cli
[Side-By-Side] List by package identifier fails
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
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
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with multiple installed versions of Microsoft.WindowsSDK, then compare winget list Microsoft.WindowsSDK with listing by package name. Start at the winget list <PackageId> CLI path and its installed-package matching behavior. Done means listing by package identifier returns all installed versions without affecting name-based listing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100