Update the app
Check for updates in Desktop, follow the action offered on your platform, and verify the running version and existing tasks. This page explains what to save, how to confirm completion, and what to do after failure.
Establish the running version and update source
Open Settings > Advanced for the version and update entry. Record platform, architecture, full version, and channel. Ordinary checks follow the corresponding channel. Use the official target-channel installer for a channel change; see Beta and Stable.
Managed updateChannel or updateFeedURL affects the source. If the control is administratively locked, inspect Settings sources and locks and contact its owner rather than clearing personal settings.
Interpret check results
| State | Meaning | Next step |
|---|---|---|
| Checking | No final result yet | Wait for the existing check |
| Up to date | Check completed; current source offers no update | Record source and time |
| Update available | An update item can be handled | Review target version and offered action |
| Unreachable or unable to check | No valid completed check | Diagnose source/network; do not record up to date |
| Downloading, ready to relaunch, applying | Update is unfinished | Complete the flow and verify after restart |
Follow the action offered for the platform and artifact. A download or file-location action does not establish installation. Verify successful check, download, and running version separately.
Complete an app update
- Note current and target versions. Save open files and necessary backups.
- Check active tasks and unconfirmed external actions. Update when you can interrupt your work.
- Complete the offered download or installation, reopen the app, and verify its version and service readiness.
- Complete a small task with your usual model and plugin, checking output and location.
- Reconcile unfinished tasks before continuing or retrying to avoid duplicate writes or messages.
If you use EvoX on multiple devices, check the version and behavior on each. Updating one does not update the others.
Failure and recovery
Retain original/target versions, failed stage, and error. Repair unreachable sources, investigate signature or digest failures under download verification, and use service maintenance for startup diagnosis. Do not disable validation to install.
Software rollback and data recovery are separate. Use a verified installer and suitable backups without assuming an older version supports every state written by a newer one. Verify version, service, original workflow, and unresolved tasks after recovery; installer exit alone is insufficient.