Hide MSIX components with no match from `winget list`

Abierto
#6,663 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp
Área
backend, cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
C++
Estrellas
26.6k
Forks
1.8k
Merge medio
3 d 10 h
PR fusionados (30 d)
41

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/winget-cli

Todos los issues de microsoft/winget-cli

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.