choco hangs at around 90% when downloading a package update from the community server

[Schroedingers-Cat]

Over the last weeks, I noticed a new behavior across all my Windows devices managed via chocolatey. At first, the chocolatey community server won't be seen as source, so no package would be updated. Trying this two to three times in a row, it is finally able to see what packages can be updated. But then, there's a high likelihood that this process will hang:

You have autohotkey.portable v1.1.33.05 installed. Version 1.1.33.06 is available based on your source(s).
Progress: Downloading autohotkey.portable 1.1.33.06... 99%

After some minutes, chocolatey decides to skip the package:

utohotkey.portable not upgraded. An error occurred during installation:
 Timeout für den Vorgang wurde überschritten.
autohotkey.portable package files upgrade completed. Performing other installation steps.
The upgrade of autohotkey.portable was NOT successful.
autohotkey.portable not upgraded. An error occurred during installation:
 Timeout für den Vorgang wurde überschritten.

It hangs most of the time around 90, because the progress hits the 90%-range in an instant. Trying to re-run cup all -y a few times, and it manages to get all package updates at some point.

This is happening on four devices with different versions of Windows 10 (2019-2020 releases) and they are connected to WiFi and Ethernet. I didn't notice these connectivity issues with anything else than choco/chocolatey community server.

[Schroedingers-Cat]

This is still happening on a regular basis with packages from the community server. It happens most of the time when nearing the end of the download. Then all of a sudden, the network usage in the task-manager stops showing any activity for the process and nothing else from chocolatey seems to be doing anything. It just gets stuck and drops a timeout error after some minutes.

It's still happening across multiple machines and different internet connections (private and at work) via ethernet.

[pauby]

@Schroedingers-Cat Is this still an issue? I haven't seen any other reports of this.

[Schroedingers-Cat]

I was observing this on multiple machines on different networks. It used to happen very regularly.

I haven't seen it happening for the last couple of months, so it's probably not an issue anymore.