{{ message }}
Repository navigation
[BUG] Lack of updatable scoop packages #5414
Description
Please confirm these before moving forward
- I have searched for my issue and have not found a work-in-progress/duplicate/resolved issue.
- I have tested that this issue has not been fixed in the latest (beta or stable) release.
- I have checked the FAQ section for solutions.
- This issue is about a bug (if it is not, please use the correct template).
UniGetUI Version
2026.3.0
Windows version, edition, and architecture
Windows 11 Pro 28120.3032
Describe your issue
Sometimes, even though scoop status -l returns multiple packages (both in the logs and when run manually), UnigetUI still shows fewer than the actual number present.
Steps to reproduce the issue
- Refresh update page
UniGetUI Log
too long
Package Managers Logs
too long
Relevant information
The skipped packages vary—they aren't always the same. In this specific case, SubtitleEdit (the only one today) always appears in Uniget; rpcs3 sometimes does and sometimes (like now) doesn't; others, such as JAMI, never appear (obviously excluding the ignored packages, but none of these—which I've already checked—are blocked).
Screenshots and videos
Activity
SiriosDev commentedon Oct 15, 2026
Gabriel Dufresne (@GabrielDuf) Unfortunately, I have to reopen this issue because the problem seems to persist. It's much better than before, but some are still “hidden.” For example, right now:
it's still “invisible” to unigetui
GabrielDuf commentedon Oct 19, 2026
Hi SiriosDev (@SiriosDev),
This turned out to be a different bug from the first one. The table output was read correctly this time. The problem was the versions themselves: nightly packages like
librehardwaremonitor-dotnet10-nightlyuse very large build numbers as versions (e.g.37149234619). Those were too big for UniGetUI's version comparison, so the installed and the new version both counted as 0. UniGetUI then decided the newest version was already installed and quietly hid the update.I reproduced it with that exact package, and #5547 fixes it: version numbers of any length are now compared correctly. With the fix, the update shows up as expected. It will be in the next release once merged.
SiriosDev commentedon Oct 19, 2026
Oh, that explains, thanks 🙏