winget-cli: Publishing is down again (failed to update source)

Brief description of your issue

Same problem that previously occured #2666 has started again. And downloading the msix from https://cdn.winget.microsoft.com/cache/source.msix returns a 0kb file.

Steps to reproduce

Run winget source update

Expected behavior

winget should have updated successfully

Actual behavior

Winget will attempt to update the source when running any command but will return the message Failed in attempting to update the source: winget. If you run winget source update it will respond with Cancelled

Environment

Windows Package Manager v1.3.2691
Windows: Windows.Desktop v10.0.22621.819
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 12
Comments: 46 (9 by maintainers)

Most upvoted comments

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

ResourceNotFoundThe specified resource does not exist.

M43R on Nov 24, 2022

Hey all, we’ve addressed the zero-byte file issue in the CDN.

Publishing has been working consistently since then, so I’m going to go ahead and close this issue.

We’re aware there are users who are still having issues updating the source in some scenarios, so we’ll deal with those on a more case by case basis.

denelon on Feb 22, 2023

We’ve been working with our CDN provider to squash the nasty zero-byte file being cached and served. Is anyone still getting this problem? If you are, can you share the IP address you’re hitting?

denelon on Jan 26, 2023

Update: My problem was solved. It was caused by installing Private Internet Access which automatically turned on it’s “VPN Kill switch” not allowing any traffic to flow via windows built-in networking. Browsers worked fine though which is why I was confused. I turned off the kill switch and everything appears to work fine now.

bepstein111 on Feb 21, 2023

Update: It happened again but installing Cloudflare WARP solved the issue, I think the problem isn’t with winget CDN, but my ISP (Grameenphone), because I’m having same issue with twitter and GitHub (sometimes).

fluentmoheshwar on Feb 21, 2023

Fixed after uninstalling internet download manager.

fluentmoheshwar on Feb 14, 2023

Happy New Year, and i tried testing another thing…

on Win 10, toggling TLS 1.3 on/off in inetcpl.cpl still causes winget errors when TLS 1.3 is on
according to Qualys SSL Labs https://cdn.winget.microsoft.com appears to be serving different content depending on the connection being on TLS 1.2 or TLS 1.3 and also if SNI is negotiated or not negotiated. https://www.ssllabs.com/ssltest/analyze.html?d=cdn.winget.microsoft.com

i cannot make SSLLabs analyze the European side of the CDN - SSLLabs does not let me select 152.199.21.175 and it auto-selects to the North America one, 152.195.19.97… so i added that to my hosts file and tested again with that.

result: Same error happens with winget and 152.195.19.97 present in the hosts file (on Windows 10 22H2)

R-Adrian on Jan 1, 2023

Still not working for me. Getting 0 byte file from the CDN in US.

cdn.winget.microsoft.com resolves to 152.195.19.97 for me.

efie45 on Dec 19, 2022

@denelon It is fixed for me (Hungary, EU).

simkoG on Nov 29, 2022

Still not working for me.

PS C:\Users\User\code\BoxSetup> winget source reset --force
Resetting all sources...Done
PS C:\Users\User\code\BoxSetup> winget source update
Updating all sources...
Updating source: msstore...
Done
Updating source: winget...
Cancelled

Downloading https://cdn.winget.microsoft.com/cache/source.msix through a web browser produces a 0KB file.

MarcoPeraza on Nov 28, 2022

Another workaround is to use a VPN. Use a location far from your current continent.

mgthantzin on Nov 25, 2022

I have the same problem “Failed in attempting to update the source: winget”. After following this solution, Winget will work perfectly.

vtvy on Nov 24, 2022