P.S.A. Original CDN will be retired #3652
Comments
denelon
added
the
Public-Service-Announcement
microsoft-github-policy-service
bot
added
the
Needs-Triage
denelon
changed the title
|
Some users may see HTTP 429 Server Busy errors temporarily as we work on the CDN changes. |
|
We're getting blocked messages from the CDN. 
|
|
It should be back up now. |
|
Hi, Any updates? |
|
I am getting occasional successes When it succeeds, the log shows the following: When it fails, the log shows: I am using WinGet, version [1.6.2631] on Windows 11 |
|
Can you share the response from https://cdn.winget.microsoft.com/cache/source.msix when this happens? |
|
Chrome and firefox are happy and can download it. Winget failes, saying it can't download it. Is there a possibility to get more details? |
|
I also have problems with updating the winget source. I also tried resetting the source with winget source reset --force however this doesnt seem to fix the problem. The error message in log is as follows: winget source url: |
|
I am also getting errors when attempting to update my winget sources, From the same Powershell Core console using Invoke-WebRequest, I get a 200 OK for https://cdn.winget.microsoft.com/cache/source.msix, so the DNS resolution seems to work fine outside of winget. Running v1.7.2491-preview on Windows 10 from Germany. |
Getting the same error, browser says Service Unavailable |
|
@primeinc same here. Did you find a way to fix it? |
|
@denelon When it's not working, I see 429ers like you posted #3652 (comment) |
|
@dan-mba @primeinc I've written my solution to "Failed in attempting to update the source: winget" here: #3525 (comment) It should work, but not the first time I had to coax winget to keep updating 🙈 |
|
Hmmm, now I'm getting request blocked (Service unavailable) answers from that URL... |
|
Got this error since my first request this day... |
|
Since yesterday evening (around 5pm - UTC+2), I've been getting the error Current Location: Dunkerque, France Sources:Logs:EnvironmentGestionnaire de package Windows v1.6.2631
Copyright (c) Microsoft Corporation. Tous droits réservés.
Windows: Windows.Desktop v10.0.22621.2361
Architecture du système : X64
Package : Microsoft.DesktopAppInstaller v1.21.2631.0
Répertoires Winget
-----------------------------------------------------------------------------------------------------------------------------------------
Journaux %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
Paramètres utilisateurs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Répertoire des liens portables (utilisateur) %LOCALAPPDATA%\Microsoft\WinGet\Links
Répertoire des liens portables (ordinateur) C:\Program Files\WinGet\Links
Racine de package portable (utilisateur) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Racine du package portable C:\Program Files\WinGet\Packages
Racine de package portable (x86) C:\Program Files (x86)\WinGet\Packages
Téléchargements du programme d’installation D:\Users\Lusiiky\Downloads
Liens
---------------------------------------------------------------------------------------------
Déclaration de confidentialité https://aka.ms/winget-privacy
Contrat de licence https://aka.ms/winget-license
Avis de tiers https://aka.ms/winget-3rdPartyNotice
Page d’accueil https://aka.ms/winget
Conditions générales du Windows Store https://www.microsoft.com/en-us/storedocs/terms-of-sale
Paramètre administrateur État
---------------------------------------------------
LocalManifestFiles Désactivé
BypassCertificatePinningForMicrosoftStore Désactivé
InstallerHashOverride Désactivé
LocalArchiveMalwareScanOverride Désactivéhttps://cdn.winget.microsoft.com/cache/source.msixNow: Fixed? Before: https://cdn.winget.microsoft.com/cacheTitle: Console: |
|
I'm getting the same error as @Lusiiky, in 2 computers |
|
Same here (Germany) - ip is 37.201.XX.XX |
|
Can confirm this, I have the same error as @Lusiiky |
Same issue. My location is German, IP 88.69.183.xxx I don't think it is the WinGet Version or that the entire CDN is down. We probably would see more tickets. Could it be that a specific mirror for a local IP range is the culprit? |
|
Same issue affecting multiple machines here in the UK. |
|
Same issue in Brazil, multiple computers under different ISPs |
|
@denelon - I ran the following:
These commands are run on Windows 10. This thread mentions installing the latest version of winget will solve the problem, but in my case I do have the latest version and it is still throwing this error. How I fixed: Questions:
|
|
OMG. Dear Microsoft, you became a joke... so do your datacenter-corporate-bullshit and please, please just pay open-source project authors to do things efficiently - scoop. |
|
Thank you, @shalinikhare27 , for This fixed the |
|
I came here from #1656 and none of the solutions here worked, but I found a solution, I want to share, that also could give some insights into the origin of my problem and maybe similar problems of others. Winget and Teams simultaneously did not work starting from today. Winget having the problem with the source as described thouroughly above and in the other thread, and Teams (New) was nearly reacting, couldn't send or receive messages and showed the following message in the top: "We’ve run into a server error. Some functions might not work right now but you can continue to use the app." Even the Microsoft Store App told me I was offline and was unable to operate. Looking for a solution especially regarding teams I cam across following thread: https://answers.microsoft.com/en-us/msteams/forum/all/new-teams-weve-run-into-a-sever-error-every-day/275e8bb1-d260-4f06-a4e1-7eaa19852e35?page=3 and the last proposed solution to change Windows Internet Properties -> Connections -> LAN Settings -> Automatic Configuration and setting "Automatically detect settings", resolved all issues. Teams, winget and the Microsoft Store worked as nothing ever has happenend. |
|
@daniatic the "Automatically detect settings" can be a very risky option, particularly for "mobile" computers. This instructs the computer to use the WPAD protocol, which can lead to disclosure of credentials to third parties, MitM attacks etc. Evaluate the need to use this option very carefully before using it. |
|
@StevieLamb thank you very much for this information! I will try turning it off again and hope that Teams and winget keep working. Do you have any ideas why this setting could affect the proper workings of these two apps? |
|
@daniatic I'm somewhat confused it was suggested as a resolution to you, and that it in fact helped you: that setting should only be useful if:
If these things are true for you then at least it makes some sense, but in that event I'd recommend talking to whoever administers the proxy about how it should be configured so you can avoid using WPAD. If these things are not true then I'm afraid I'm stumped as to why enabling this setting fixed your issue. |
|
Then we stay in the dark... This is my private notebook and I used it in my private home network, where there is no proxy or similar. Even in the office there is no proxy of which I know of. No matter where I was these days it did not work until I changed that setting and without restart or any other intervention it just worked afterwards. I disabled it the moment you told me and for now it still works. |
|
I cannot run “winget upgrade” or “winget source update”. They all return an error or fail with a cancel status when I try to update the winget source. After I turn on WARP (you can download it at cloudflarewarp), I can run “winget source update” and then “winget upgrade” and all winget commands run normally. I think you can use any VPN app. But with a free VPN app like WARP, we cannot choose which server or country to use, so it just randomly works sometimes and sometimes it does not. Then I release that, when I do not turn on WARP VPN, if I ping cdn.winget.microsoft.com, it will ping 127.0.0.1 (I don’t know why). Even if I run ipconfig /flushdns, it still pings to 127.0.0.1. But when I turn on WARP VPN and ping cdn.winget.microsoft.com, it pings to another IP address than 127.0.0.1. So, I edit the host file and add “152.199.21.175 cdn.winget.microsoft.com”. All winget commands work fine without turning on WARP. I hope this helps if you cannot fix the source error by using all other advice. You can use this PowerShell command to add a host entry: # Get the path of the host file
$file = "C:\Windows\System32\drivers\etc\hosts"
# Get the content of the host file as a string
$hostfile = Get-Content $file
# Append the entry to the host file
$hostfile += "152.199.21.175 cdn.winget.microsoft.com"
# Set the content of the host file back to disk
Set-Content -Path $file -Value $hostfile -Force |
|
Guys, i was getting a "Failed in attempting to update the source: winget No applicable update found." error and the only way i managed to have winget working properly was by following this exact steps from Microsoft: |
|
For anybody who still can't get this working... I have a brand new Win 11 PC just unboxed today. Winget refused to update, I was having the same errors listed above. The official Microsoft Install winget page says at the top "get App Installer from the Microsoft Store" (If it's already installed, make sure it is updated with the latest version.) I did indeed have a version already installed, so I updated it. After updating, I am able to 
|
|
A fresh Windows 11 install is STILL affected. Why is this issue not pinned? Also, fix your product already. How can you screw up in such a way that the user has to repair the stock Windows to actually use it? Rhetorical question, nothing new with Microsoft. |
When I asked for a PS script to update Winget, I got told "Use the Windows Store". Yes, thanks for making Winget useless on a clean install Microsoft, now I need to keep software binaries in my install scripts. Basically I just got told "you are using it wrong" |
|
@dustojnikhummer There are good reasons why I avoid Windows as much as possible and suggest against using it these days. Still have to deal with this telemetry bloat hog Windows shtt show. From stupid decisions in .NET (like not preinstalling .NET Core) to Candy Crush in the Start Menu. This OS is cancerous, unreasonable and degenerated (you can't even put the taskbar on top anymore) and I only install it as VM to compile software for it to serve users who don't know what they are doing to themselves. Whenever possible I pick mingw as part of my compiler toolchain to avoid having to use Windows for more than testing. |
Yes, very helpful in corporate environment, thank you... |
|
I had this problem yesterday (winget not working due to wrong CDN), here is my description and solution: ChrisTitusTech/winutil#1082 (comment) the TLDR is to install |
|
very tired, winget, windows. searching for many posts still getting stuck |
and others
We will be retiring the CDN used by earlier versions of WinGet.
Please upgrade to WinGet 1.6 or WinGet 1.7-preview (or later as new releases come out).
You can update "App Installer" via the Microsoft Store.
You can also use https://aka.ms/getwinget to install the latest available stable version.
For preview builds, you can use https://aka.ms/getwingetpreview.
New Windows installs (Azure Virtual Desktop for example) may have an earlier version of WinGet (delivered via App Installer) and they may not function correctly to download the default "winget" source. Updating the client to the latest version via the Microsoft Store, or GitHub will mitigate the issue.
Several users have reported issues with getting source updates to function after installing the latest version of WinGet. We're looking into the root cause.
If you run
winget source update --forcein an administrator terminal/shell it should resolve the issue.If that doesn't work, try
powershell -command Add-AppxPackage https://cdn.winget.microsoft.com/cache/source.msixLatest Update:
CDN Migration is complete
The text was updated successfully, but these errors were encountered: