Open remidebette opened 6 months ago
Try to validate in Windows Sandbox instance and there's nothing unusual. Failed to reproduce the issue.
Hi, thanks for trying to replicate. It still happened for the upgrade to this version on my local yesterday
It still happened for the upgrade to this version on my local yesterday.
Did you install the package with another installer type? Installer types are incompatible with each other in winget.exe
.
I am also experiencing this on several systems, though it doesn't seem to be related to the "upgrade --all" action. I noticed it happening regularly over the last few months, so I started trying to upgrade Helm.Helm on its own and the install still freezes. I'm not finding that it installs successfully. It seems more like the database THINKS it installed successfully and no longer finds an available upgrade. But if I look in the packages install path, the old executable and all support files are still there. If I run "helm version" it shows the old version, but winget thinks it's current. My best guess, based on where the install/upgrade hangs, is that the package is unzipped, the database is updated, but it fails to copy files to the destination directory. The big question for me is why it freezes/hangs instead of throwing an error or timing out. The logs show nothing as it doesn't progress past successful operations. I have ONE virtual machine that I know of that isn't having this problem, so when I get time I'll see if I can find a difference.
@davejdyer @remidebette Would you be able to recall when did you first install the package Helm.Helm
and was the install made through an older version of WinGet? There is a known issue where winget install/uninstall/upgrade
would "freeze" for these types of packages (nested portables), which I'll reference below. The issue also contains a workaround to unblock this behavior, could you see if your issue can be solved with those steps?
@mdanish-kh - I can confirm that the workaround mentioned in winget-cli#3279 fixes this problem with Helm.Helm for me. I'm not certain of the exact timeline when it was added to each machine, but it was rolled out slowly over time so many were likely before whatever the version line was that began the issue. It's further muddied by the fact that the Helm package specifically had a different issue at some point where the PATH variable wasn't updating properly, so it was added and removed several times making it hard to tell.
I don't have many to fix, but this would be a major pain to clean up for anyone with a large install base with older portables. Hopefully someone can find a good fix, though clean-up scripts with PoSh wouldn't be too hard.
Thanks for your help!
Please confirm these before moving forward
Category of the issue
Installation issue.
Brief description of your issue
winget upgrade freezes
Steps to reproduce
When executing
winget upgrade --all
And Helm.Helm is part of the packages to be upgraded
Actual behavior
The package install succeedes but then the upgrade does not pursue and there is no more logging in the terminal.
If doing a new upgrade, winget will take over from the next package, and helm is indeed installed successfully
Expected behavior
The upgrade should simply continue without human interviention
Environment
Screenshots and Logs
No response