You added licensing, activation works, everyone is happy — and then you ship your first auto-update and the support tickets start: "it's asking me to activate again." The cause is almost always the same, and it has nothing to do with your licensing logic. It is where you cached the activation. Modern .NET desktop updaters install each version into its own directory, and anything you wrote next to the executable goes with the old version. This post is the per-updater map of where to put the signed lease so activation survives.
The root cause: versioned install directories
A cached activation is a signed lease — a small, node-locked, RSA-signed blob the SDK writes after a successful activation so the app can validate offline on later launches without phoning home. The question is which directory it lands in.
Velopack and Squirrel do not update in place. They install version 1.0.0 to …\YourApp\app-1.0.0\ , then install 1.1.0 to …\YourApp\app-1.1.0\ and point a stub launcher at the new folder.…