Updating Primo RPA Studio

Updating Studio to the latest version provides access to new features, performance improvements and enhanced data security.

Update Process

Updating requires a complete reinstallation of the program:

1. Close all related applications:

• Close Primo RPA Studio
• Close all browsers with the Primo RPA extension installed
• Ensure that the LTools.WebBrowser.Native.exe processes are terminated

2. Uninstall the previous version:

• Uninstall the old version of the application via “Control Panel” → “Add or Remove Programs”
• Or manually delete the folder where the previous version of Primo RPA Studio was installed

3. Saving extension files:

• If you installed browser extensions manually, save the \Extensions and \ExtensionsV3 subfolders
• You can save the .Dependencies folder to speed up dependency installation in new projects

4. Install the new version:

• Run the installer for the new version of Primo RPA Studio

For a standard installation, run setup.exe - it will automatically check and install all required components. The .msi file is intended for system administrators for automated installation via the command line.

Select the previous installation folder if the suggested path does not match the original one.

If necessary, restore the saved Extensions and ExtensionsV3 folders.

Configuration File Locations

Since version 1.25.9, configuration files are organized as follows:

Extension manifest files (manifest_**.json) are saved in different locations depending on the installation type:

• For all users: %ProgramData%\Primo\Manifest\ — this resolves the issues with permissions
• For the current user: %LOCALAPPDATA%\Primo\ — location remains unchanged

The dependencies folder (.Dependencies) operates on a priority basis:

• By default, it is created in %ProgramData%
• If you do not have write access to the installation directory, it is automatically created in %ProgramData%
• For backward compatibility: if the folder already exists in Studio, that is the one that will be used

Saving user settings

If you have extensions installed, make a backup copy of the Primo\Primo Studio\Extensions\manifest_ch.json file before updating to avoid potential issues with search patterns (selectors). After reinstalling Studio, replace the new manifest_ch.json file with the saved copy.

This recommendation applies to cases where the extension was installed manually, not via automation.

1. If you installed an unpacked extension, you don’t need to do anything extra when reinstalling Studio. The main thing is to install Studio to the same location on your drive.
2. If you installed the extension using the “Store (Current User)” or “Packed” methods, copy the manifest_ch.json file before reinstalling Studio and replace the new file with it after installation. Note: Copy the manifest_ch.json file from the appropriate folder:

• Primo\Primo Studio\Extensions — for extensions based on Manifest V2.
• Primo\Primo Studio\ExtensionsV3 — for extensions based on Manifest V3 (available starting from Studio version 1.24.6).