Download request failed. Returned status: 404 #152915
Comments
denelon
added
Issue-Bug
microsoft-github-policy-service
bot
added
the
Needs-Triage
|
This was previously reported for Citrix.Workspace in: I was able to get a solid reproduction today with Microsoft.Azd. |
microsoft-github-policy-service
bot
removed
the
Needs-Triage
|
What is the most efficient way to use the workaround? Do we need to fully delete the manifest, wait for it to be approved then submit again or can we modify the current manifest? |
The workflow that has been succesful for me:
This got |
|
doing any of the steps others have done does nothing im still getting the 404 error when i try to upgrade software through winget |
|
This is also affecting |
|
|
|
Recently, I got this issue when try to use “winget upgrade --all” Download request status is not success. I see Denelon said “The work-around is to remove and re-add the manifest” but I can't find how to do it after some reading on the I see command “winget source update” and after I use it now the issue is resolved, and I can upgrade all the package without issue (Just sharing). |
|
Note that the error (for me) is only occurring with I did notice that |
|
No background on this bug, just saw it referenced on my PR. For my PR, I added a new manifest (with a more correct version 7.2-22.1) that has the same download urls as the old manifest. I also removed the old manifest (7.2) in the PR. Maybe that can help narrow down a repro case. ID: |
We've gotten reports from users who are getting an error when they try to run any command where the manifest needs to be downloaded and it fails.
The work-around is to remove and re-add the manifest. The publishing pipeline should be able to test for this scenario to ensure the manifest has been published and the index is correctly pointing to the URL so this doesn't impact customers.
The text was updated successfully, but these errors were encountered: