Axiom V1.8.6
Updater orphaned-instance fix -- the actual root cause.
Fixed
- Found the real cause behind every update failure this cycle, including the ones the
V1.8.4/V1.8.5 hotfixes narrowed but didn't fully close: a failed update automatically
relaunches the installed copy (TryRestartInstalledCopy), and that relaunch always goes
through the normal single-instance check. If another copy from an earlier failed
attempt was still silently running -- its own "Axiom is already running" dialog never
seen or dismissed -- the new relaunch hit that same dialog and became one more orphan
itself, invisible and still holding the installed DLLs open. Each subsequent failed
update compounded this; eleven separate Axiom processes had accumulated behind the
scenes, several matching PIDs already logged as "did not exit" hours earlier - The updater's post-update relaunch is now tagged as a silent restart; if it finds Axiom
already running, it exits quietly instead of showing a dialog nobody may ever see or
dismiss - Before every update, the updater now sweeps for and terminates any process actually
running the installed executable, not only the one process ID it was launched to wait
for -- so a backlog of orphans from before this fix can't keep blocking future updates
either
Updating
Existing Axiom V1.7.2+ installations can install this release from the in-app update notification. V1.7.0 and V1.7.1 users must manually install V1.7.2 once because those builds contain a download-verification lock defect. New users can download the Windows ZIP, extract the complete folder, and run Malx_AI.exe.