Update Version

The setup of a newer version installs next to the current version and updates the instances you select.

Updated 1 min read

Updating Version

Your configuration database and historian database are preserved and automatically updated. As a backup, always take a project export before updating.

Start the setup of the new version. It lists the instances on the server and updates the selected ones; the other instances keep running their version. See Multiple Instances.

On a server installed with a version before 2026/11/02, setup takes over the existing installation as the instance EnvisionSCADA. The project, databases, IIS site and bindings stay, and the program moves to C:\Program Files\EnvisionSCADA. 

Restart Windows when setup asks for it.

The installed version is shown next to the EnvisionSCADA logo at the top of the menu, for example V20260808. Its first six digits are the Current Version on the License page.

Some upgrades change the structure of the historian database. When that is the case, the first start after the upgrade converts the historian before the engine is started, and every screen shows a Database migration in progress page until it completes.

On a small historian this takes seconds. On a historian that has been logging for years it can take considerably longer, and it needs free disk space on the drive that holds the database. Plan the upgrade in a maintenance window, and read the Database Migration After an Upgrade article first when the historian is large.

An earlier version cannot open a historian that an upgrade has converted. Take a copy of the historian database before updating when returning to the earlier version must remain possible.

Something missing or wrong in this article? Contact us