[BUG] Prompted to update to version 2026.1.0.0 when I already have 2026.1.0 installed

[stevehoek]

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.1.0

Windows version, edition, and architecture

Win 10 Pro x64

Describe your issue

I'm getting prompted to install the same version

Steps to reproduce the issue

Install 2026.1.0 from this repo
Launch
See the erroneous update message

UniGetUI Log

n/a

Package Managers Logs

n/a

Relevant information

There is no 2026.1.0.0 version, it just installs the same 2026.1.0 and keeps nagging

Screenshots and videos

[ConiKost]

Same here.

[jbarcus81]

Same issue... It will not go away.

[jh30uk]

Same here.

[lastmetroid]

same issue, its in infinite loop, when you close it it will update then restart and so on

[Sixdd6]

Same, seems it is looking for literal 2026.1.0.0 and not counting 2026.1.0 as sufficient. At least it seems like that may be the case.

[bikram-agarwal]

Same thing is happening in portable installation too!
I downloaded the UniGetUI.x64.zip and extracted it to E:\SW\UniGetUI. When I run the exe, it says it has to update to 2026.1.0.0 and then that installs at C:\Program Files\UniGetUI. And keeps saying it has an update.

[jmwoods301]

I was able to kill the loop by disabling automatic UniGetUI updates, and then restarting.

After that, it worked as expected.

[mamoreau-devolutions]

Argh, sorry about that, we deployed the update file earlier today and 2026.1.0 started using it instead of fallbacking to GitHub Releases. I just hadn't foreseen the issue caused by the version comparison mismatch with 3 and 4 version elements. I'll see about handling it properly in code, and try to get the update file reverted over the weekend.

[llaville]

Too much annoying. I've reverted back to v3.3.7 that is more stable, until a fix/stable version is available.

[mamoreau-devolutions]

The issue has been resolved, we have temporarily removed UniGetUI from the new update file, which forces a fallback to the legacy update check method in 2026.1.0. I apologize for the trouble, we will re-enable the new update file once 2026.1.1 is released with a fix for the version comparison: