WireGuard for Windows failed to start after update to v0.2.1

Jason A. Donenfeld Jason at zx2c4.com
Tue Nov 17 23:03:00 CET 2020

On Tue, Nov 17, 2020 at 10:56 PM Jason A. Donenfeld <Jason at zx2c4.com> wrote:
> If so, my current best guess is that:
> - MSI stops manager, stops tunnel, installs new version, starts new
> manager (thereby initiating the config migration), starts new tunnel.
> - New tunnel fails to start [a]. We flipped on the MSI rollback switch
> in v0.2, so that tunnel bug now causes the installer to move in
> reverse [b].
> - New manager stopped, old version installed, old manager started, old
> tunnel started, but config has been migrated already [c], so the
> tunnel doesn't come up and you can't see it.
> - You press update again, stops manager, new version installed, starts manager.
> - You start the tunnel service manually.

Alternative interpretation would be that the MSI starts new tunnel,
which uninstalls old Wintun, then old MSI tries to uninstall old
Wintun and fails, and then new installer jumps into rollback mode.
Either way, it seems like the solution is to go back to disabling

More information about the WireGuard mailing list