0x80072ee7 0x80072efd

Brief description of your issue

was getting the above errors for over 2 months and i stumbled on a way to fix it. mind you I'm not the sharpest knife in the draw.

Steps to reproduce

PS C:\WINDOWS\system32> winget source list
Name Argument Explicit

msstore https://storeedgefd.dsx.mp.microsoft.com/v9.0 false
ustc https://mirrors.ustc.edu.cn/winget-source

I tried to add "winget source add winget https://winget.azureedge.net/cache" failed with error 0x80072ee7
I removed https://cdn.winget.microsoft.com/cache from source.
ran winget upgrade
PS C:\WINDOWS\system32> winget upgrade
Name Id Version Available Source

Mozilla Firefox (x64 en-US) Mozilla.Firefox 135.0 135.0.1 ustc
Mozilla Thunderbird (x64 en-US) Mozilla.Thunderbird 128.6.0 128.7.1 ustc
Oh My Posh JanDeDobbeleer.OhMyPosh 24.18.1 24.19.0 ustc
NVCleanstall TechPowerUp.NVCleanstall 1.17.0 1.18.0 ustc
Brave Brave.Brave 131.1.73.105 133.1.75.178 ustc
VeraCrypt IDRIX.VeraCrypt 1.26.18 1.26.20 ustc
TechPowerUp GPU-Z TechPowerUp.GPU-Z 2.61.0 2.62.0 ustc
Discord Discord.Discord 1.0.9012 1.0.9183 ustc
Microsoft Visual Studio Code Insiders (User) Microsoft.VisualStudioCode.Insiders 1.97.0 1.98.0 ustc
Microsoft Visual Studio Code (User) Microsoft.VisualStudioCode 1.97.0 1.97.2 ustc
Windows Terminal Microsoft.WindowsTerminal 1.21.10351.0 1.22.10352.0 ustc
11 upgrades available.
I can now install and update.

Expected behavior

winget upgrade now works ! what did I just do ?

Actual behavior

winget upgrade and install

Environment

win11 pro 23h2

Start by reproducing winget source list and winget upgrade in the reported Windows 11 environment, comparing behavior before and after removing https://cdn.winget.microsoft.com/cache. No source files or tests are named; done would mean identifying why the source change resolves the errors and specifying the expected source configuration or behavior.