An Update Fails or Won't Verify

"Update could not be verified: not installed"

A downloaded update failed its own signature or integrity check, so it was never installed; your current version keeps running unchanged. Try checking for the update again; if this repeats, download and reinstall the current version manually from the official release page instead of waiting for an in-place update.

"Could not start the update"

The update never got underway, most often because another update or a database migration was already running. Wait for that to finish and try again.

An update that fails partway through, on a self-hosted instance

A failed self-hosted update rolls back automatically to the version you were running before, with services restarted and healthy again on that previous version. You aren't left on a broken in-between state; check the update log (Settings → System → View log) for what actually failed before retrying.

Services don't come back healthy after an update

If a restarted service doesn't report healthy within a reasonable window, that's surfaced directly in Settings → System, alongside which service it is and a link to its logs. Restart that specific service from the same screen before assuming the whole update needs redoing.

Related

• Updating HeartBeatAgents: how the normal update flow works on desktop and self-hosted instances
• Installation: verifying a release's signature directly, independent of the in-app updater