winget-cli: 0x8a15000f : Data required by the source is missing
Brief description of your issue
Receive error message 0x8a15000f : Data required by the source is missing
when doing pretty much anything with Winget.
Steps to reproduce
winget upgrade --all --verbose-logs
Expected behavior
winget downloads the package, and the sources are reachable
Actual behavior
C:\Users\xx> winget source list
Name Argument
-----------------------------------------------------
msstore https://storeedgefd.dsx.mp.microsoft.com/v9.0
winget https://cdn.winget.microsoft.com/cache
C:\Users\xx> winget search Windows.PowerShell
Failed when searching source; results will not be included: winget
No package found matching input criteria.
C:\Users\xx> winget upgrade --all --verbose-logs
Failed when searching source: winget
An unexpected error occurred while executing the command:
0x8a15000f : Data required by the source is missing
Environment
Windows: Windows.Desktop v10.0.19045.2604
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.10173.0
Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 1
- Comments: 26 (2 by maintainers)
Commits related to this issue
- Homemaker: Force winget update A fresh Windows 11 Pro install ran into https://github.com/microsoft/winget-cli/issues/3068 — committed to albertdev/dotfiles by albertdev 3 months ago
For me, the fix for 0x8a15000f was to run the following command in PowerShell:
Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.Winget.Source_8wekyb3d8bbwe
It’s a bug in the old version. You can fix by updating it. You can use this script below:
Tried all of the above fixes without any luck. (Fresh Win11 Pro install)
Only thing that worked for me was the following:
Add-AppPackage -path "https://cdn.winget.microsoft.com/cache/source.msix."
Afterwards the error was resolved and I was able to use winget.
This helps me a lot, the problem solved!!
Had the same issue on a fresh install of Windows 11. The installation from CDN fixed it for me.
Could it be that the issue is linked to doing an offline installation? (I did connect my WiFi only after the installation, so that I could set up a local account.)
I have an error when running that command
I have the same issue, if I am building a golden image through packer. I have set of winget commands as a part of install-sw.ps1 script. If it runs unattended as a part of the packer build, it fails with same error. If i finish the build just before the script runs and execute it in real RDP session, it works.
So the context of real login vs. winrm login seems to be the right lead. I do not have the workaround 😦
Have, same issue here. As a hint to reproduce: Running the commands in administrative shell (as scheduled task when logged in as a “normal” user) I get the errors. When logging in with Athe local adminstrative account I am able to winget upgrade (nothing else) successfully. After relogging in as the “normal” user the task runs fine. It seems it has something to to with anything in the user context, what is set after a “real” login of the admin…