Auto update strange behaviour

[Vlad_ek]

As per chat - didn't work in auto in #8 and #9. Manual installation works fine. Now when trying to recreate the problem it automatically goes into manual installation.

Aslains_WoT_Logs.zip

[Aslain]

I checked your log file and the auto-update is actually working correctly on your end.

 

Here is what happened according to the log:

The installer detected that you had version 2.2.1.3.08 installed and the new installer is version 2.2.1.3.09, so it showed you the auto-update dialog asking if you want to update using your previous settings.

 

At that point you clicked "No", which tells the installer to skip auto-update and go into manual installation mode instead. That is exactly what it did.

 

So there is no bug here - the auto-update dialog appeared as it should, but choosing "No" is what sent you into manual mode. Most likely this happened in both #8 and #9 without you noticing, or maybe you clicked "No" by mistake.

 

Next time the dialog pops up, click "Yes" and it should auto-update just fine.

[Vlad_ek]

Made me do manual.

Aslains_WoT_Logs.zip

[Aslain]

verified it again in the source and in the log you just sent. The Yes/No mapping is not inverted, and the log proves what was clicked.

 

Your newest log, at 13:08:39, records:

User chose No.

 

2026-05-29 13:08:37.694   [GetInstalledVersion] InstalledVersion=2.2.1.3.09
2026-05-29 13:08:37.694   [CheckLocalVsInstalled] Installed version (2.2.1.3.09) is older than this installer (2.2.1.3.10), offering auto-update
2026-05-29 13:08:37.695   Message box (Yes/No):
                          Ten instalator zawiera nowszą wersję (2.2.1.3.10) modpacka niż obecnie zainstalowana (2.2.1.3.09).
                          
                          Kliknij Tak dla auto-aktualizacji używając poprzednich ustawień, lub Nie aby kontynuować z ręczną instalacją.
2026-05-29 13:08:39.005   User chose No.

 

If you had clicked Yes, the log would instead show User chose Yes. and User chose auto-update from local installer, and a second installer would launch silently. None of that is present,  so in this run No was registered, not Yes.

Note: that User chose No. line is written by the Inno Setup engine itself from the actual dialog return value, not by my code, so it can't be a logic bug on my side. One thing to watch:

 

if you close that dialog with Esc or the X in the corner, Windows counts it as No. To auto-update, click the Yes button itself.

 

If you're certain you clicked Yes, please attach the log from that exact run, the one you sent shows No.

[Vlad_ek]

I'm absolutely 100% sure "user chosen Yes". I will check again with next update and track the whole process. It may have happen that I created logs after auto update didn't work and I updated mods in manual regime. 

Edited May 30 by Vlad_ek

[Aslain]

Sorry logs says the otherwise. Next time record a video, and attach logs right away.

[Vlad_ek]

I will. To defend my point here is the screenshot of "refusal" taken at 13:05 

[Aslain]

There is no such thing in logs, only this timeframe there: 2026-05-28 12:14:46.512  - 2026-05-28 12:16:22.537. There is a chance that it wasn't logged. 

 

Next time when it happens, navigate to AppData\Local\Temp and attach the latest file like that: Setup Log 2026-05-30 #002.txt (numbers and date will be different)

 

 

[Aslain]

You can fool it that you have old WoT modpack installed by running regedit, and changing that number to older, i.e. to 10, then launch the latest installer.

 

Komputer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Aslains_WoT_Modpack_Installer_is1

 

 

[Vlad_ek]

Haven't tried fooling but tried again - autoupdate didn't work - screens and logs attached.

 

BUT I have Win LTSC installed on another drive and tried the same there and it works fine with autoupdate.

Aslains_WoT_Logs.zip

[Vlad_ek]

Setup Log 2026-06-04 #002.txt

2026-06-04 15:24:58.760   User chose Yes.
2026-06-04 15:24:58.760   [CheckLocalVsInstalled] User chose auto-update from local installer
2026-06-04 15:24:58.761   [CheckLocalVsInstalled] Saved log snapshot for post-update merge
2026-06-04 15:24:58.837   [CheckLocalVsInstalled] Staged self via cmd to C:\Users\W\AppData\Local\Temp\Aslains_WoT_Modpack_Installer_update.exe
2026-06-04 15:24:59.582   [CheckLocalVsInstalled] ShellExec failed with ErrorCode=1223
2026-06-04 15:24:59.582   Message box (OK):
                          Aktualizacja automatyczna nie powiodła się. Spróbuj uruchomić instalator ponownie lub kontynuuj z ręczną instalacją.
2026-06-04 15:25:32.218   User chose OK.
2026-06-04 15:25:32.219   InitializeWizard raised an exception (fatal).
2026-06-04 15:25:32.219   Caught EAbort exception.
2026-06-04 15:25:32.219   Deinitializing Setup.
2026-06-04 15:25:32.219   [DeinitializeSetup] DeinitializeSetup -- OK
2026-06-04 15:25:32.321   Log closed.
 

[Aslain]

Thanks for the logs,  it's not a download problem. The new installer started fine, but Windows blocked it from relaunching itself for the auto-update (log shows ErrorCode=1223 = ERROR_CANCELLED).

Just do this: when it asks about auto-update, click No and run a normal manual install. It installs 2.3.0.0.03 the same way and keeps your settings,  auto-update is only a shortcut.

It fails here (but works on your LTSC) most likely because UAC is turned off or you're using the built-in Administrator account. There's no hidden prompt to find and "Run as administrator" won't help. The manual install gets you updated right now

 

I will try to make small patch for your case, but cannot promise it will work.

[Vlad_ek]

Don't bother for me if I am the only one affected, I am fine using manual as I did quite often before. As for UAC see screen.

 

[Aslain]

Either way I added one fallback, try it today. Let me know with logs too.

[Vlad_ek]

Will do with next update, ok?

 

[Aslain]

Try the one I just released.

[Vlad_ek]

Same result.

Setup Log 2026-06-04 #005.txt

[Aslain]

Thanks, the new log made it clear. The error (1223) isn't a download or permission problem, Windows SmartScreen is blocking the updater from launching because the installer was downloaded with a browser, so Windows tags it as "from the internet."

That's why it works on your LTSC drive (SmartScreen likely off) but not here.

Quick fix on your side: right-click the downloaded .exe -> Properties -> tick Unblock at the bottom -> OK -> run it again and choose auto-update. That should work.

(Or just click No and do a normal manual install, it installs the same version with your settings.)

I'll also update the installer so it removes that "from the internet" tag automatically, so this won't happen again.

[Vlad_ek]

I will stick to manual, not a problem at all. I just thought that me sharing this will help you in development. 

[Vlad_ek]

Unblocking in properties works fine and auto updated from #3 to #4. Yet another problem solved 😉 Thanks  🙂

 

[Vlad_ek]

Update: to my surprise update from #4 to #5 went smoothly without intervention, i.e. no need to unblock in properties ... 😁

[Aslain]

42 minutes ago, Vlad_ek said:

Update: to my surprise update from #4 to #5 went smoothly without intervention, i.e. no need to unblock in properties ... 😁

The installer is now removing this property on its own.