MSIX Framework package installed via winget cannot be uninstalled via winget
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 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.
Written by the indexing model from the issue text.
Description
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
- 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