Download request failed. Returned status: 404

[denelon]

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]

This was previously reported for Citrix.Workspace in:

• [Package Issue]: Citrix.Workspace #151181

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

[PckgrTom]

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]

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]

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]

This is also affecting winget export

[3xploiton3]