Installation and Updates

Install new versions safely and understand version-specific app data.

Use this page before installing a new app version or when you need to understand what an update changes.

Installing a new version

You do not need to uninstall an older version before installing a newer version.

It is safe to have multiple app versions installed at the same time. Keeping the previous version installed is often safer because you can close the new version and return to the previous installed version if you need to keep working.

Version-specific app data

Installing a new version does not automatically copy user data from an older version.

Each app version normally has its own AppData folders for:

  1. App-wide settings, including Settings.json.
  2. Saved profile files, including .prf files.
  3. Generated image cache data.
  4. Logs.

This separation is intentional. It lets a new version start with its own data while the previous version keeps the data it already used.

Settings and profiles

You may be able to copy settings and profile files from an older version folder to a newer version folder, but this is an advanced or support-directed step.

Only copy settings or profile files while the app is not running.

Before copying:

  1. Back up the destination files.
  2. Copy only between app versions you trust.
  3. Start the app and check the related settings before relying on the copied data for important work.

Newer versions should normally tolerate missing settings or profile fields by using defaults. The app development practice is to avoid removing setting and profile fields after they have shipped. Even so, copied files are not guaranteed to be a fully tested migration path.

If copied settings or profiles cause startup problems, close the app and use the Troubleshooting Reset page.

Image cache

Do not copy the image cache as a normal update step.

The image cache is generated data. Let each app version build its own cache. Separate versions should have separate cache locations, and that is the default.

If you use a custom image cache location, you can point a newer version at the same folder. This may work, but it can also create compatibility problems if the cache structure changes between app versions. Using a separate cache folder per app version is safer.

Runtime dependencies

The installer includes required Microsoft runtime installers when the app needs them.

These may include:

  1. The Windows App Runtime.
  2. Microsoft Visual C++ redistributables needed by native SDK components.

If a runtime dependency is missing or damaged, the installer normally repairs or installs it. The redistributable installers are also located in the app installation folder. If support asks you to repair them manually, close the app, find those installers in the app installation folder, and run them as administrator.

Falling back to an older version

If a new version does not work correctly:

  1. Close the new version.
  2. Start the previous installed version.
  3. Continue working from the previous version if it still behaves correctly.

Because app data is version-specific by default, the previous version should still have its own settings, profiles, and cache data.

Uninstall and reinstall

If all else fails, uninstall the affected version and reinstall it.

Uninstalling and reinstalling can repair missing or damaged app files. It may not remove version-specific user data. If reinstalling does not fix the problem, use Troubleshooting Reset because the problem may be in settings, profiles, or cache data that survived the reinstall.