-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CDN Is Experiencing Errors - Download request status is not success / 0x80190193 : Forbidden (403) #5122
Comments
[Policy] Issue-Bug |
As I mentioned in the other issue that was closed, WinGet shouldn't have these issues. Linux solved package mirrors over a decade ago yet Microsoft decided to make what should be a simple process, like switching repo mirrors, into an EEE strategy. The "packages" are simply static assets, yet WinGet doesn't even have a way to use a folder as a repo source. Instead, the only documented tool for creating a repo is winget-cli-restsource which requires Azure for the backend. WinGet "packages" are static files (manifests). Why on earth do you need Azure Cosmos DB or anything but simple web server, or folder, to create your own repo... or in this case, to mirror one? |
I get the very similar error:
FYI: So it seems it is not related to a specific package, at least to me. I don't have any of the mentioned packages installed. |
|
Mozilla.Thunderbird is working now, by the way. |
GnuPG.GnuPG is now working too! |
There is an ongoing issue where the manifests for certain packages are not available for download from the CDN. This results in operations such as
winget upgrade
being unable to process the data. When this happens the WinGet CLI returns the errorDownload request status is not success / 0x80190193 : Forbidden (403)
.This issue is being created as a top-level issue to track the resolution of the CDN issues.
Packages Known to be Affected
GnuPG.GnuPG
Mozilla.Thunderbird
AnyDeskSoftwareGmbH.AnyDesk
GitHub.Atom
Microsoft.Azure.AZCopy.10
Docker.DockerDesktop
The text was updated successfully, but these errors were encountered: