Halo v3.1.2 — autostart and Codex integration survive an upgrade

An installer-only release. Nothing in the pill itself changed since 3.1.1 — but if you have upgraded Halo at least once, two things you almost certainly ticked on your very first install had been quietly removed since.

"Start Halo when Windows starts" was on once, then never again

Setup remembers the previous run's choices and restores them over its own defaults. That sounds helpful and isn't: anyone who unticked autostart a single time had it stay unticked for every release afterwards, and the update that was supposed to keep Halo working is the thing that stopped it from coming back after a reboot. The defaults now win on every install.

"Integrate with Codex" was removed by upgrading

Worse, and for the opposite reason. That task carried a flag whose documented behaviour is "unchecked when Setup finds a previous version installed" — so it was on for a first install and off for every upgrade after it. If your Codex sessions stopped appearing in the pill at some point and you never worked out why, this was it. Re-run the installer and the integration comes back.

Also: the installer had been stamping 3.1.0 onto a 3.1.1 build.

---

Both checkboxes are on the first page of the installer and you can still untick either one — the change is only about which state you start from.

DynamicWinSetup.exe is the signed installer. DynamicWinPortable.zip needs no install — unzip and run Halo\Halo.App.exe. If you are already on 3.1.x, Halo picks this up on its own within a day; the installer part of it applies the moment it does.