Repository navigation
v2.22.5
Updates that cannot brick the install
The updater no longer stops Nex before proving it can finish the job, and every step is written to a log file that survives even if the launcher is gone.
What changed
- Helper shutdown via scheduler: The elevated helper is ended through its own scheduled task, which works across integrity levels where
taskkillsilently fails. A locked helper binary can no longer abort the update mid-flight. - Verify-before-touch: After stopping, the updater confirms zero
Nex*processes remain before moving anything. If anything survives, it aborts with the install untouched. - Safe rollback: Failures before the backup step restart the original install instead of leaving nothing running; failures after it restore the backup as before.
- File logging: All updater output mirrors to
updater.login the update workdir through a never-throwing logger, so a dead parent process can no longer take the diagnostics — or the rollback — down with it. - Move retries: The install-tree backup retries transient file locks before giving up.
Bug Fixes
- Silent death after "Updating...": Fixed the sequence where the updater quit Nex, then died on a locked helper binary, leaving no backup, no install, no restart, and no logs.
Commit Log
4aae79dfix(updater): survive parent death and stop helper via scheduler