Update, back up, or uninstall Arizmic

What this guide is for

Arizmic keeps the installed application separate from your application-data folder. This guide explains how to protect retained work, apply a supported desktop update, and remove the application without accidentally deleting local projects or outputs.

Release-specific steps become effective only after the corresponding package has passed platform and lifecycle certification.

Know what you are managing

There are two separate things:

• the application installation, which contains the signed Arizmic program and launcher; and
• application data, which can contain settings, catalog records, imported data, Prepared Data, Strategies, Studies, Results, Notebook projects, logs, and other retained local work.

Updating or uninstalling the program must not silently decide the fate of the application-data folder.

Find the active data location

Before maintenance, open System & Jobs -> Information and System & Jobs -> System Settings. Record the active application-data location and confirm that it is reachable.

Do not assume the data is inside the installation folder. If more than one location has been used, identify which one the current launcher and workstation actually report.

Create a cold backup

For a consistent backup:

1. Allow active Jobs to finish or cancel them through System & Jobs -> Jobs.
2. Confirm there is no unresolved import, Study, export, Notebook, or Live operation.
3. Stop active Notebook sessions and supervised Live deployments safely.
4. Close the workstation and let the launcher stop managed services.
5. Copy the complete application-data folder to the backup destination.
6. Record the Arizmic version, operating system, time, and source path.
7. Verify that the backup can be read and contains the expected top-level content.

A filesystem copy taken while services are writing can contain mismatched catalog and file state. Use a cold backup unless a later release explicitly provides and certifies an online backup feature.

Protect the backup according to its contents. It can include proprietary data, Strategy code, local settings, and operational history. Credentials should use protected storage, but a backup still deserves restricted access.

Apply an update

Use only the update path named by the official release instructions.

1. Read the release notes and supported-platform statement.
2. Create a current cold backup.
3. Close Arizmic and confirm its managed processes have stopped.
4. Verify the new signed or notarized package.
5. Install it through the supported platform workflow.
6. Start the launcher and wait for Ready.
7. Open System & Jobs -> Information and confirm the new build identity.
8. Use Check Workstation and apply any offered workstation update.
9. Open Jobs, Activity Log, and one retained object before starting large work.

An application update does not silently recompute old Prepared Data, Studies, or Results. If a format or capability requires migration or rebuilding, the release notes and owning page must state that explicitly.

If an update is blocked

Stop and retain the current installation and backup when:

• the package signature or notarization is invalid;
• the release does not support the current operating system or architecture;
• the application-data folder is unavailable;
• the new launcher and visible workstation report incompatible identities;
• a required migration cannot be previewed or completed safely; or
• retained objects disappear unexpectedly.

Do not delete the data folder, overwrite it with a blank folder, or repeatedly reinstall while the cause is unknown. Record the build identities and collect a privacy-reviewed diagnostic bundle.

Uninstall the application

Before uninstalling:

1. cancel or finish Jobs;
2. stop Notebook and Live activity safely;
3. create and verify a cold backup;
4. record the active application-data location; and
5. close the launcher.

Use the operating system's supported uninstall path. If the verified uninstaller offers separate Keep local data and Remove local data choices, treat them as independent decisions.

Choose Keep local data when you may reinstall, need to inspect or migrate work, or have not independently verified a backup. Choose removal only after the exact path and scope are shown and you are certain the retained content is no longer needed.

Removing the application is recoverable by reinstalling a compatible package. Removing local data may not be recoverable without a separate backup.

Verify the intended end state

After an update:

• the launcher reaches Ready;
• Information shows the expected build;
• the workstation and API check succeeds;
• the intended data location remains selected; and
• retained objects open correctly.

After uninstalling while keeping data:

• the application no longer launches; and
• the recorded application-data folder remains intact.

After choosing data removal:

• verify only the exact approved application-data location was removed; and
• retain the backup until you have confirmed no further recovery is needed.

Return to Install and First Launch when installing a new certified package.