Hide MSIX components with no match from `winget list`

Aberta
#6,663 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
cpp
Domínio
backend, cli

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
C++
Estrelas
26.6k
Forks
1.8k
Merge médio
3d 10h
PRs com merge (30d)
41

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/winget-cli

Todas as issues de microsoft/winget-cli

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.