v1.3.2 — upgrading no longer leaves the service stopped

A fix for upgrades. If you installed 1.1.0 or later, take this one.

Upgrading no longer leaves the service switched off

Installing over an existing version left the machine unprotected, and everything about it looked like it had worked. The setup stops the service before replacing files, then registers it — and sc create fails outright when the service already exists, so the registration reported failure, nothing started it again, and the only sign was a status page nobody had open.

An already-registered service is now reconfigured rather than recreated, which also handles the case that makes the situation arise: an install path that has changed. The service's registry ImagePath stays quoted through the upgrade, so the unquoted-service-path hazard the first install avoids is not quietly reintroduced.

Verified on a real install: service Stopped before, Running after, still set to start with Windows, path still quoted.

Downloads

File	Use it if
MinecraftFirewall-1.3.2-setup.exe	You want it installed properly. Start here.
MinecraftFirewall-v1.3.2-win-x64.zip	You would rather unzip it somewhere and run it yourself.

Everything from v1.3.1 and v1.3.0 is included: escalating bans for repeat offenders, the player-initiated /premium name lock, automatic blocking of server-indexing crawlers, and the repair for configurations written by older versions.

476 automated tests pass.