winget-cli: 0x8a15000f : Data required by the source is missing

Make sure you don’t have any firewalls blocking the winget.azureedge.net and azureedge.net subdomain and domain. Most “privacy” tools for Windows block this by default.

Perhaps try booting up Windows Sandbox or other virtual machine software and see if it’s reproducible there. If it’s not reproducible, then the issue comes from your host machine and is likely caused by the above.

Also, https://winget.azureedge.net/cache - without /source.msix added to the end of the URL - is not meant to be accessible, so seeing ResourceNotFound is expected here, as long as doing ping winget.azureedge.net causes no issues and that the website is online and not offline.

If you go to https://winget.azureedge.net/cache/source.msix and install the source.msix file, does any error pop up on your screen? And what happens when you do winget search edge if it’s installed?

I see this issue on Windows 11 specifically when running winget from an Administrator command prompt. If the command prompt is not run as Administrator, the issue does not occur for me.

My specific error when running as Admin: Failed when searching source: winget An unexpected error occurred while executing the command: 0x8a15000f : Data required by the source is missing

谢谢各位的帖子，让我从一个小白不断摸索成长，你们坚持的精神感染了我，本来我打算从做系统的，可是我没放弃，你们每个人的建议我都尝试过，可是总失效，最后，一条奇葩的命令改变了这种现状：winget uninstall winget
winget uninstall winget winget uninstall winget 重要的命令说三遍！！

Try this in the powershell:

Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.Winget.Source_8wekyb3d8bbwe

Worked for me

For clarification In my case, just running PowerShell with a “normal” user, but selecting “as Administrator” did not help. I literally meant: Start the windows-session as local Administrator. My last log-in as local admin was quite a while ago. So while logging in, I got greeted with the typical “Please wait. We’re running updates for you.” After that, I ran PowerShell (within the admin-session) and the problem disappeared.

Since then, I’m able to do a “winget source update” as a normal user. I’m living in Germany.

I’m not an expert. But I thought this might help.

In my case, I could resolve the issue as follows:

1. Log-in with local administrator
2. powershell -> winget source update

i also have this problem on windows 11 pro 0x8a15000f : Data required by the source is missing

winget source list
Name     Argument
-----------------------------------------------------
msstore https://storeedgefd.dsx.mp.microsoft.com/v9.0
winget  https://cdn.winget.microsoft.com/cache

“winget source reset” - did not help

winget -v
v1.3.2691

Experiencing this issue now. Found the root cause to be that https://winget.azureedge.net/cache/source.msix is returning a 404 error. A 404 error should be communicated to the user in a more direct way than a generic “data is missing” message.

Edit - additional info:

Windows Package Manager v1.1.13405
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22000.348
Package: Microsoft.DesktopAppInstaller v1.16.13405.0

Edit 2 - https://winget.azureedge.net/cache/source.msix is no longer returning a 404 error, and winget functionality is restored on my system. Probably a temporary issue server-side. Should still be better communicated to the end user.

We’ve largely gotten past the issue with the zero-byte file being returned by the CDN. I’m going to go ahead and close this issue as resolved. We’ve created the following Issue to track improving the error message as well as logging:

• #2058

I suspect that the issue is happening during the source update, based on the 0% showing in your output. The logs from winget source update winget would probably be the most helpful to understand why it is failing silently. Alternatively, winget is basically doing this:

1. Download from https://cdn.winget.microsoft.com/cache/source.msix

2. PS> Add-AppxPackage

It is possible that this would give more direct logging/errors about my suspicions.

My guess is that something is wedged on the machine related to the Microsoft.Winget.Source package, and that manually removing it would help to unstick it. winget source remove winget would also attempt to remove that package in theory, but I’m not sure that I would trust winget to find the package to remove since it can’t find it to use.

This worked for me, thanks!

I should point out that both > winget source update --name winget & > winget source update winget require admin privileges to work, and so if you intend to run them over SSH, you’ll need to ensure your SSH session starts with elevated privileges by following Step 1.

Try this in the powershell:

Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.Winget.Source_8wekyb3d8bbwe

Worked for me

This is the only solution that worked for me ! It solved the issue. Winget works correctly now.

That error led me to this issue which recommends flag -usewindowspowershell

PowerShell 7.3.1
PS C:\temp> import-module appx -usewindowspowershell
WARNING: Module appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax.
PS C:\temp> Add-AppxPackage .\source.msix
PS C:\temp> winget upgrade --all

$$$

This is the first time I’ve ever seen winget upgrade --all function properly. What a day to be alive. I’ve always wanted a Windows package manager and this give me hope that it could be a stable thing some day.

Guys they fixed it! 😊😊😊

Have they? I am still having this issue in UK

Guys they fixed it! 😊😊😊

https://github.com/microsoft/winget-cli/issues/1656 I solved it by:

1. change permission of C:\Windows\Temp C:\Users%USERNAME%\AppData\Local\Temp\WinGet
2. run *.Winget.msix (in C:\Users%USERNAME%\AppData\Local\Temp\WinGet ) by click it.

Then, I can use winget install -e --id vim.vim You can find more apps here: https://winget.run/ This issue is a big problem.