Hide MSIX components with no match from `winget list`
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start with PredefinedInstalledSourceFactory.cpp, ARPHelper.cpp, and ReportListResult, then trace how installed MSIX packages are enumerated and correlated. Check how package manifests expose AllowExternalContent and visible app list entries, and how ARP SystemComponent entries are filtered. The issue is done when uncorrelated MSIX components are hidden from winget list; consider the enumeration performance concern raised in the issue.
Written by the indexing model from the issue text.
Description
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
winget list currently shows MSIX packages that aren't really apps - identity packages registered by Win32 installers, shell extensions, and headless runtime/data packages. They can't be correlated to a source, so they show as MSIX\<full name> rows instead. Usually a Win32 entry already represents the product and it's correlated instead.
On my machine, 69 of the MSIX rows have no source. Three of them are apps. Some examples:
Adobe Acrobat MSIX\AdobeAcrobatDCCoreApp_26.1.0.0_x64__33qsgwvbc… 26.1.0.0
Adobe Acrobat (64-bit) Adobe.Acrobat.Pro 26.002.22031 winget
EpmShellExtension MSIX\Microsoft.EpmShellExtension_1.0.0.0_neutral__… 1.0.0.0
Microsoft Edge Microsoft.Edge 157.0.4341.42 winget
Microsoft Edge MSIX\Microsoft.MicrosoftEdge.Stable_152.0.4191.53_… 152.0.4191.53
PowerToys (Preview) x64 Microsoft.PowerToys 0.102.3001.0 winget
PowerToys PowerRename Context Menu MSIX\Microsoft.PowerToys.PowerRenameContextMenu_0.… 0.102.3001.0
PSTokenizerShared MSIX\WindowsWorkload.PSTokenizerShared.Data.3.5_1.… 1.2508.888.0
Windows Package Manager Source (winget) V2 MSIX\Microsoft.Winget.Source_2026.1108.637.6_neutr… 2026.1108.637.6
| Unmapped MSIX rows | Count | Identifier |
|---|---|---|
| Packages with external location (Adobe CoreApps, Edge, Office helpers, OneDriveSync, PowerToys context menus, VS Code, EpmShellExtension, WinMerge, Local AI Manager) | 15 | AllowExternalContent |
Headless packages (WindowsWorkload.* AI components, winget's own source packages, OpenAI.CodexPrimaryRuntime.*) |
51 | No Application element, or every app has AppListEntry="none" |
| Apps with a Start entry (Command Palette, Windows Security, an Edge PWA) | 3 | None I can find |
winget list already hides ARP entries with SystemComponent set.
But it only skips PackageSignatureKind::System MSIX packages.
Proposed technical implementation details
Hide these packages from winget list when they have no available match.
- In
PredefinedInstalledSourceFactory, mark MSIX packages as components when the manifest setsAllowExternalContent, or when no application has a visible app list entry. - In
ReportListResult, skip uncorrelated installed packages that are marked as components.
Questions:
- Do we need
--include-componentsto show the skipped entries? We don't for ARP, so I lean towards no - This approach reads each package's manifest during enumeration, would have to make sure it's not too slow
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 1.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from microsoft/winget-cli
-
Issue-Docs Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/winget-cli#6692 ·
Maintainers usually reply within 2 days
-
Issue-Docs Possible-Duplicate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/winget-cli#6493 · 1 comment ·
Maintainers usually reply within 2 days
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6427 ·
Maintainers usually reply within 2 days
-
Issue-Docs msstore
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/winget-cli#6331 · 1 comment ·
Maintainers usually reply within 2 days
-
Command-Source Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6148 ·
Maintainers usually reply within 2 days
All issues in microsoft/winget-cli
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day