Download request failed. Returned status: 404

denelon commented 6 months ago

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.

denelon commented 6 months ago

This was previously reported for Citrix.Workspace in:

151181

I was able to get a solid reproduction today with Microsoft.Azd.

PckgrTom commented 6 months ago

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?

stephengillie commented 6 months ago

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:

Create PR in new branch, to remove highest manifest version.
- These frequently get Sequence contains no elements and need manual help. Feel free to @ me.
Removal PR is approved and merged.
Create PR in new branch, to readd highest manifest version.
Readd PR is approved and merged.
- Some of these need troubleshooting help.

This got Microsoft.Azd to show again, and hopefully should work for every package. I believe this is only a workaround as a larger fix is implemented.

Oddballalex36 commented 6 months ago

doing any of the steps others have done does nothing im still getting the 404 error when i try to upgrade software through winget

KitKat31337 commented 6 months ago

This is also affecting winget export

3xploiton3 commented 6 months ago

lucivskvn commented 5 months ago

Recently, I got this issue when try to use “winget upgrade --all”

Download request status is not success. 0x80190194 : Not found (404).

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

https://github.com/microsoft/winget-cli/blob/master/doc/troubleshooting/README.md#executing-winget-exits-with-no-message

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).

danielfdickinson commented 3 months ago

FYI I did updates on some machines over the past few hours and have started seeing this error. I therefore suspect one of these has a bad manifest:

danielfdickinson commented 3 months ago

Note that the error (for me) is only occurring with winget update --scope machine --all as an administrator. winget update --all as a standard user works (with UAC prompting for the machine scoped packages).

I did notice that winget update --scope machine showed gnupg.gnupg where winget update does not.

RoscoP commented 3 months ago

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: okibcn.nano #163901

microsoft / winget-pkgs

Download request failed. Returned status: 404 #152915

151181