microsoft / microsoft/winget-cli
Fail to upgrade HexRays.IDA.Free exits WinGet instead of continuing with other upgrades
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
doing winget upgrade I saw
Name Id Version Available Source
...
IDA Freeware and Hex-Rays Decompilers (… HexRays.IDA.Free 7.6 7.7 winget
...
so I did
winget upgrade --all -h
but when it reached that IDA entry it failed (had been installed sometime in the past manually) it failed (said I should ask manufacturer for an app for my Windows [note I'm on 64-bit, so not sure what was that which failed showing a dialog that is usually shown when you run 64-bit on 32-bit Windows], could it be ARM or 16-bit stuff or some corrupted image?)
the bug though is that WinGet exited at that point (whereas at some installers before where it had low disk space [say for Docker which was big] it just continued when their installers failed after succesful download)
Steps to reproduce
need to have specific software and version of it installed most probably, see description
upgrading multiple items fails upon reaching that (and exits WinGet)
Expected behavior
expected to continue with next item (was just at 9/36 updates)
Actual behavior
see screenshot, it fails to continue

Environment
Windows Package Manager v1.2.10271
Windows: Windows.Desktop v10.0.22000.675
Package: Microsoft.DesktopAppInstaller v1.17.10271.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing winget upgrade --all -h with the listed WinGet and Windows versions, using an installed HexRays.IDA.Free package or another failing upgrade. Trace how the bulk-upgrade command handles an installer failure and verify that later upgrades continue instead of WinGet exiting.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100