Skip to content
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

Fails to update program, error 0x801901a0 #1060

Closed
Masamune3210 opened this issue Jun 1, 2021 · 6 comments · Fixed by #1138
Closed

Fails to update program, error 0x801901a0 #1060

Masamune3210 opened this issue Jun 1, 2021 · 6 comments · Fixed by #1138
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Milestone

Comments

@Masamune3210
Copy link

Masamune3210 commented Jun 1, 2021

Brief description of your issue

Just got winget installed after joining the package manager beta, tried upgrade --all and it keeps dying trying to upgrade QuickPar with a Requested range not satisfiable (416) error

Steps to reproduce

Attempt to upgrade QuickPar, would assume the same issue occurs if you try to install it from scratch but I haven't tried it

Expected behavior

For it to download the setup and the upgrade to complete

Actual behavior

Error on setup download

Environment

[winget --info]
Windows Package Manager version v1.0.11451
Windows: Windows.Desktop version v10.0.19043.985
Package: Microsoft.DesktopAppInstaller version v1.11.11451.0

Any other software?

Was running it in a PowerShell instance inside of the new Terminal, don't know if that would change anything or not

@ghost ghost added the Needs-Triage Issue need to be triaged label Jun 1, 2021
@denelon
Copy link
Contributor

denelon commented Jun 1, 2021

@Masamune3210 I'm not sure, but this might have something to do with Delivery Optimization attempting to download the file with "range" requests. You might try to change your settings to "network": "wininet" and see if that helps.

@denelon denelon added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Author-Feedback Issue needs attention from issue or PR author and removed Needs-Triage Issue need to be triaged labels Jun 1, 2021
@Masamune3210
Copy link
Author

Im sorry, I am unfamiliar with how to do that, I'm probably just misunderstanding how to use the config file

@ghost ghost added Needs-Attention Issue needs attention from Microsoft and removed Needs-Author-Feedback Issue needs attention from issue or PR author labels Jun 2, 2021
@denelon
Copy link
Contributor

denelon commented Jun 2, 2021

winget settings will launch the settings file with your default editor. If you have something like Visual Studio Code configured to handle JSON files, it also supports JSON schemas. That means you would get intellisense and tooltips.

From there, you would add the line above (probably ending in a comma if you have other settings).

@Masamune3210
Copy link
Author

tried but not sure if I added the config right, result was the same

`{
"$schema": "https://aka.ms/winget-settings.schema.json",

// For documentation on these settings, see: https://aka.ms/winget-settings
// "source": {
//    "autoUpdateIntervalInMinutes": 5
// },

} "Network": "wininet"`

@denelon
Copy link
Contributor

denelon commented Jun 2, 2021

You put it past the end. Here is an example:

{
    "$schema": "https://aka.ms/winget-settings.schema.json",

    // For documentation on these settings, see: https://aka.ms/winget-settings
    // "source": {
    //    "autoUpdateIntervalInMinutes": 5
    // },

    "network": {"downloader": "wininet"}
}

@Masamune3210
Copy link
Author

Ok, yeah now that the config file is fixed the file is correctly downloaded and the upgrade works correctly

@ghost ghost added the In-PR Issue related to a PR label Jun 9, 2021
@ghost ghost added Resolution-Fix-Committed and removed In-PR Issue related to a PR labels Jun 9, 2021
@denelon denelon added this to the v1.3-Client milestone Jun 21, 2022
@denelon denelon removed the Needs-Attention Issue needs attention from Microsoft label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants