Interrupted 2.0.178 → 2.0.179 install-on-quit leaves app unlaunchable (Multilo.exe and app.asar deleted)
What I was trying to do
Nothing unusual — I quit Multilo at the end of a session. The app had already silently downloaded 2.0.179 in the background and had it queued to install on quit.
What happened
The install-on-quit handler launched the NSIS installer, the installer confirmed the app had closed, started replacing the old version, and then stopped partway through. It had already removed the old files but never wrote the new ones.
The result:
...\AppData\Local\Programs\Multilo\still exists but **Multilo.exeandresources\app.asarare gone**. Only leftovers remain (resources.pak,vulkan-1.dll,vk_swiftshader.dll,snapshot_blob.bin,v8_context_snapshot.bin,Uninstall Multilo.exe, and a near-emptyresources\folder).So:
- Both the Desktop and Start Menu shortcuts still point at
Multilo.exe, which no longer exists — clicking them does nothing at all, with no error message. - Windows "Apps & features" still lists Multilo 2.0.178 as installed, because the uninstall registry entry was never cleaned up. From the user's side the app looks installed but is simply gone.
To a non-technical user this looks exactly like the application uninstalled itself overnight. It took digging through the logs to work out that it was a half-finished update.
Steps to reproduce
I can't reproduce it on demand — it happened once, on a normal quit. The sequence from the logs was:
- Running 2.0.178. The updater polls every 30 minutes, sees 2.0.179, and pre-downloads it ("already-prepared").
- Quit the app.
install-on-quitspawns the 2.0.179 installer and the old app exits.- The installer begins, logs that the app and lock-holders are closed, writes its
INSTDIRline — and then dies. - Nothing is ever written back. No new version, no rollback, no error shown anywhere.
Expected vs actual
Expected: either the update completes, or it fails and leaves the working 2.0.178 install in place — or at minimum, something tells me on next launch that an update failed.
Actual: the old version is deleted, the new version is never installed, and there is no surviving executable and no message of any kind. The app silently ceases to exist.
Relevant log output
updates\nsis-install.log— note the truncated first character of the second line, which suggests the write itself was cut off:customCheckAppRunning: done — app + lock-holders closed, clear to install ultilo-2.0.179-win-x64.exe INSTDIR=C:\Users\<user>\AppData\Local\Programs\Multiloupdates\update-debug.log— the last entries ever written:[install-on-quit] entry {"platform":"win32","installerProcessLaunched":false,"hasReadyInMemory":true} [install-on-quit] spawning {"version":"2.0.179"} [loop-breaker] attempt-recorded {"version":"2.0.179","failCount":1,"max":3} [spawn] spawn-attempt {"expectedVersion":"2.0.179","approach":"direct-nsis-no-powershell","attemptCount":1} [spawn] authenticode {"ok":true,"status":"Valid","subject":"CN=INTUTO4U LLC, ...","reason":"ok","enforced":false} [spawn] install-mode {"perMachine":false,"elevate":false} [spawn] nsis-installer-spawned {"expectedVersion":"2.0.179","parentPid":33580,"childPid":32348}updates\install-attempts.json:{ "version": "2.0.179", "failCount": 1, "max": 3 }install-state.jsonstill reads"version": "2.0.178"with"pendingUpdateTo": "2.0.179", so the app's own record of itself is now wrong in both directions — it believes 2.0.178 is installed when no executable exists.Environment
- Multilo 2.0.178, updating to 2.0.179 (windows x64, per-user install, no elevation)
- Windows 11 Home, 26300
- Does it happen every time? No — once, on an ordinary quit.
Two things worth noting
1. The downloaded installer was fine. I checked the queued
Multilo-2.0.179-win-x64.exeafterwards: its SHA-256 matches the hash in the app's ownready.jsonexactly, and it is Authenticode-valid and signed by INTUTO4U LLC. So this wasn't a corrupt or tampered download — the installer was good and the install simply got interrupted, most likely by the machine sleeping or shutting down right after the app quit, or possibly by antivirus.**2.
ready.jsonhas a size field that doesn't match the file.** It records"size": 35243535while the actual downloaded file is 188,584,520 bytes — about 5× larger. The 2.0.178 installer sitting in the same folder is also ~188 MB, so ~180 MB looks like the correct size and the ~35 MB figure looks wrong. Since the SHA-256 matched, whatever uses this field clearly isn't gating the install on it, but if it's meant to be a pre-flight integrity check then it isn't working, and it may be worth checking where that number comes from.Suggestions
- Install to a new directory and swap it in once the write succeeds, rather than deleting the old install before the new one is on disk. An interrupted install should never be able to leave zero working versions.
- On launch of the updater/shortcut, if the install directory has no executable but the registry still lists a version, offer to repair instead of failing silently.
- Treat a non-zero
failCountininstall-attempts.jsonas something to surface to the user, not just a loop-breaker counter. - The
sizemismatch inready.jsonabove.
Happy to supply fuller logs if useful. Fortunately nothing in
AppData\Roaming\Multilowas touched — all documents, chat sessions, checkpoints and research collections survived intact, and re-running the downloaded 2.0.179 installer should put things right.Solved by saliha — jump to the solution
2 views
- created
- last reply
- reply
- 1
- views
- 2
- likes
- 0
- people
- 2
- M
- S
- Both the Desktop and Start Menu shortcuts still point at
Thanks for such a thorough report. The logs and the hash check made this quick to track down.
What happened: the installer removed the old version before copying the new one in, so a shutdown or antivirus stopping it partway through left nothing to start.
Fixed in the next release: updates now work the way VS Code and Chrome-style updaters do. The new version is written to a separate folder next to the installed one. Only once it's complete does a quick rename switch it in. If the install is interrupted, your current version stays as it is and keeps working.
Two smaller fixes from your notes are also in:
- The install log was writing each new line over the start of the file, which is why it looked cut off. It now keeps the full sequence.
- The
sizeinready.jsonwas the amount downloaded for a partial update (~35 MB), not the installer's size. It now records the real size. As you noticed, this was never a safety problem, because the SHA-256 is what's checked.
If you hit this before the release: run the downloaded installer from
%APPDATA%\Multilo\updates(e.g.Multilo-2.0.179-win-x64.exe), or download Multilo again from multilo.com/download. Your documents, chats and settings aren't affected.