WinGet source update fails with 0x87E80034 - MSIX manifest deployment error
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start with the WinGet CLI source update path and its tests; the report does not name specific files or tests. Reproduce winget source update --name winget on the stated Windows 11 environment and trace the failure after the package download to the MSIX deployment error. Done means the source package installs and registers successfully so searches work.
Written by the indexing model from the issue text.
Description
Relevant area(s)
WinGet CLI
Relevant command(s)
No response
Brief description of your issue
WinGet 1.29.380 consistently fails to update its default winget repository on Windows 11. The entire 3.62 MB source package downloads successfully, but the operation immediately reports "Cancelled". Manual installation of the Microsoft-signed source MSIX package fails with HRESULT 0x80073CF0 and underlying error 0x87E80034 (MsixvcStagingSession::GetManifestReader). The issue persists after resetting WinGet sources and App Installer, running DISM and SFC, restarting Windows, and verifying package integrity, signature, and folder permissions. Microsoft Store application updates work normally. No third-party antivirus is installed.
Steps to reproduce
- Open Windows PowerShell.
- Run: winget source update --name winget
- Wait for the 3.62 MB download to finish.
- WinGet reports 'Cancelled'.
- Running winget list reports that the winget source could not be updated or searched.
Expected behavior
WinGet should download, install, and register the repository source package successfully, allowing normal application searches, installations, and upgrades.
Actual behavior
WinGet downloads the entire 3.62 MB source package, then reports 'Cancelled'.
Manual installation using Add-AppxPackage fails with HRESULT 0x80073CF0.
Underlying deployment error:
MsixvcStagingSession::GetManifestReader failed with error 0x87E80034.
The failure persists after resetting WinGet sources and App Installer, running DISM and SFC, restarting Windows, and verifying package integrity, signature, and folder permissions.
Environment
[winget --info]
Windows Package Manager version: 1.29.380
Windows: Windows.Desktop version 10.0.26300.9711
System Architecture: X64
Package: Microsoft.DesktopAppInstaller version 1.29.380.0
Other software:
Microsoft Defender Antivirus (enabled)
Windows Firewall (enabled)
No third-party antivirus reported.
Microsoft Store works and successfully updated multiple applications.
WinGet source:
Name: winget
URL: https://cdn.winget.microsoft.com/cache
Type: Microsoft.PreIndexed.Package
Deployment failure:
HRESULT: 0x80073CF0
Underlying error: 0x87E80034
MsixvcStagingSession::GetManifestReader failed.
- 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
-
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 2/5 1-3 hours Newbie friendliness 75/100
stratum-mining/sv2-tp#167 ·
Maintainers usually reply within 1 day
-
better error message bug low priority semantics strings
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Sign up button opens the Sign in page instead of the Sign up page for Enterprise edition serversOpenauth bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4795 ·
Maintainers usually reply within 2 days