Repository navigation
[FEATURE REQUEST] Set maximum number of retries #1585
Description
Please confirm these before moving forward
- I have searched for my feature proposal and not found a work-in-progress/duplicate/resolved/discarded issue.
- This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use this template
Describe the new feature
Sometimes updates fail. I think there should be a maximum number of retries before WingetUI stops trying to update a package and stops complaining. Most of the time the issue doesn't resolve itself but needs user intervention so it's not like more retries make it more likely for the update to succeed.
Default could be three failed retries for example.
Another idea would be to space out subsequent retries. First retry after a failed attempt could be after 1h, next retry after 3h and the next after 6h for example.
Describe how this new feature could help users.
It would be less annoying.
Reacted by Sven Lowry
Activity
rumplin commentedon Nov 26, 2023
I would suggest default should be "Always try" and then the user could specify how many tries to apply.
SiJiL82 commentedon Aug 5, 2026
Definitely in need of this - I'm running UnigetUI on a small home server that I very rarely remote in to (maybe once every 2 weeks).
Every time I log in, I get stacked UAC prompts back to back from UnigetUI where the first install attempt triggered a UAC prompt which didn't happen because there was no active display session, which then causes the install to eventually time out and retry which triggers another UAC prompt... so when I eventually get round to RDPing into the box I get met with dozens of UAC prompts spawning that I have to click no to and can't do anything else on the machine until I've acknowledged every last one of them!
hrdubwd commentedon Oct 1, 2026
I am finding that more and more frequently 'server time out' is causing "could not be updated". Multiple tries fail to work. It used to be good - has something changed?
I suspect that the problem is that UniGetUI gives up too easily - a longer item has to be allowed for the handshakes etc.
However, even then it is possible that a retry is necessary, so the idea of that occurring automatically is highly desirable. I would prefer that the number of retries not be limited, although the time between them may also be settable, to allows for busy servers or slow connections somewhere.
As it stands it has become essentially unworkable for some items, which is a great pity.