Hide MSIX components with no match from `winget list`

Offen
#6,663 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
cpp
Bereich
backend, cli

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Issue-Feature
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.

https://github.com/microsoft/winget-cli/blob/afc9a471496c4cd80ac363df269362f84ea5a457/src/AppInstallerRepositoryCore/Microsoft/ARPHelper.cpp#L418-L423

But it only skips PackageSignatureKind::System MSIX packages.

https://github.com/microsoft/winget-cli/blob/afc9a471496c4cd80ac363df269362f84ea5a457/src/AppInstallerRepositoryCore/Microsoft/PredefinedInstalledSourceFactory.cpp#L139-L146

Proposed technical implementation details

Hide these packages from winget list when they have no available match.

  1. In PredefinedInstalledSourceFactory, mark MSIX packages as components when the manifest sets AllowExternalContent, or when no application has a visible app list entry.
  2. In ReportListResult, skip uncorrelated installed packages that are marked as components.

Questions:

  • Do we need --include-components to 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
Vorherrschende Sprache
C++
Sterne
26.6k
Forks
1.8k
Ø Merge
3 T. 10 Std.
Gemergte PRs (30 T.)
41

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/winget-cli

Alle Issues in microsoft/winget-cli

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.