MSIX Framework package installed via winget cannot be uninstalled via winget
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
Línea de trabajo
Start by reproducing the supplied winget uninstall command and reviewing the non-elevated lookup path mentioned in the issue, especially FindPackagesByPackageFamily. Then compare it with the elevated lookup behavior for multiple MSIX identities under one package family. Done means WinGet either removes the intended WASDK package or reports a clear unsupported or ambiguous-package error.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Relevant area(s)
WinGet CLI
Relevant command(s)
winget uninstall
Brief description of your issue
I was trying to use winget to install the 2.0.1 Windows App SDK package for a test automation scenario. When testing uninstall with the private version of the manifest, winget reports success, but the packages are still installed.
From an end-user perspective, I would expect a piece of software that I installed with winget to also be uninstallable by winget.
WinGet’s non-elevated path seems to use FindPackagesByPackageFamily(..., PACKAGE_FILTER_HEAD, ...), which does not resolve this framework package. Also, elevated lookup can encounter multiple packages under the shared package family. The installer deploys several MSIX identities (framework, Main, Singleton, and DDLM), while the WinGet manifest exposes only one PackageFamilyName.
See also #6525
Steps to reproduce
winget uninstall --manifest C:\data\test\wasdk-2.0.1-corrected --version 2.0.1 --disable-interactivity --silent --verbose-logs
where the corrected manifest has this edit:
diff --git a/manifests/m/Microsoft/WindowsAppRuntime/2/0/2.0.1/Microsoft.WindowsAppRuntime.2.0.installer.yaml b/manifests/m/Microsoft/WindowsAppRuntime/2/0/2.0.1/Microsoft.WindowsAppRuntime.2.0.installer.yaml
index 399985db33e..baf7279229e 100644
--- a/manifests/m/Microsoft/WindowsAppRuntime/2/0/2.0.1/Microsoft.WindowsAppRuntime.2.0.installer.yaml
+++ b/manifests/m/Microsoft/WindowsAppRuntime/2/0/2.0.1/Microsoft.WindowsAppRuntime.2.0.installer.yaml
@@ -11,7 +11,7 @@ InstallerSwitches:
Silent: --quiet
SilentWithProgress: --quiet
UpgradeBehavior: install
-PackageFamilyName: Microsoft.WindowsAppRuntime.2.0_8wekyb3d8bbwe
+PackageFamilyName: Microsoft.WindowsAppRuntime.2_8wekyb3d8bbwe
AppsAndFeaturesEntries:
- DisplayName: WindowsAppRuntime.2.0
DisplayVersion: 2.0.1
Expected behavior
WinGet removes WASDK 2.0.1, or returns a clear unsupported or ambiguous-package error.
Actual behavior
Found WindowsAppRuntime.2 [Microsoft.WindowsAppRuntime.2]
Starting package uninstall...
Successfully uninstalled
Exit code is 0 , but the package remains installed:
Microsoft.WindowsAppRuntime.2 2.0.1.0 x86
Microsoft.WindowsAppRuntime.2 2.2.0.0 x64
The verbose log contains:
No package found with family name:
microsoft.windowsappruntime.2_8wekyb3d8bbwe
Environment
Windows Package Manager v1.29.290
© 2026 Microsoft. All rights reserved.
Windows: Windows.Desktop v10.0.26689.1002
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.29.289.0
WinGet Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User) %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root C:\Program Files\WinGet\Packages
Portable Package Root (x86) C:\Program Files (x86)\WinGet\Packages
Installer Downloads %USERPROFILE%\Downloads
Configuration Modules %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules
Links
---------------------------------------------------------------------------
Privacy Statement https://aka.ms/winget-privacy
License Agreement https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
Admin Setting State
--------------------------------------------------
LocalManifestFiles Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride Disabled
LocalArchiveMalwareScanOverride Disabled
ProxyCommandLineOptions Disabled
ConfigurationProcessorPath Disabled
DefaultProxy Disabled
- Lenguaje dominante
- C++
- Estrellas
- 26.6k
- Forks
- 1.8k
- Merge medio
- 3 d 10 h
- PR fusionados (30 d)
- 41
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/winget-cli
-
Issue-Docs Needs-Triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
microsoft/winget-cli#6692 ·
Los mantenedores suelen responder en 2 días
-
Issue-Docs Possible-Duplicate
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
microsoft/winget-cli#6493 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
WinGetSourceCreator: PackWithMappingFile should verify makeappx.exe exists before invoking itAbiertoIssue-Feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
microsoft/winget-cli#6427 ·
Los mantenedores suelen responder en 2 días
-
Issue-Docs msstore
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
microsoft/winget-cli#6331 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Command-Source Issue-Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
microsoft/winget-cli#6148 ·
Los mantenedores suelen responder en 2 días
Todos los issues de microsoft/winget-cli
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
stratum-mining/sv2-tp#167 ·
Los mantenedores suelen responder en 1 día
-
Sign up button opens the Sign in page instead of the Sign up page for Enterprise edition serversAbiertoauth bug ui/ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
MerginMaps/mobile#4795 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
HarperFast/rocksdb-js#1118 ·
Los mantenedores suelen responder en 1 día
-
bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
26.04 bug dark-mode Easy Hack impress symptom: visual
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
CollaboraOnline/online#16421 · 1 comentario ·