The process of updating an older Studio release to this release differs depending on the Studio edition currently installed on your machine - Enterprise or Community.
The installation artifacts can be downloaded from the Resource Center in UiPath Automation Cloud, provided to you when you purchase Studio, or provided by your customer success manager or the support team.
UiPath uses calendar versioning, labeling its products with the year of the release (major) followed by the month (minor) and the patch (micro) version.
Updating the Enterprise Edition
In releases prior to 2021.4, Studio and Robot were available as 32-bit applications. Starting with version 2021.4, a 64-bit installer is available by default. A 32-bit version is also available and can only be installed on 32-bit operating systems.
UiPathPlatformInstaller.exe is no longer available starting with version 2021.4.
UiPathPlatformInstaller.exe Enterprise installations as follows:
- Use the 64-bit version of the installer (
UiPathStudio.msi) to update existing 32-bit installations on 64-bit operating systems.
- Use the 32-bit version of the installer (
UiPathStudio-x86.msi) to update existing installations on 32-bit operating systems.
Existing installations on 64-bit operating systems that are using the default installation path (
C:\Program Files (x86)\UiPath\Studio) are migrated to
C:\Program Files\UiPath\Studio after updating with the 64-bit installer. If the older version is installed in a custom location, the update does not change the installation path.
- Double-click the installer to launch the installation wizard.
- A page is displayed with installation options. To continue using your previous setup, do not change any settings. If you want to make changes to the setup, you can configure the following options:
- Install Choice - Select if you want to install UiPath Studio, StudioX and Assistant for creating and testing automations. or only the UiPath Assistant for running automations.
- Robot Installation Type - Select the Robot installation type: Service Mode (the recommended option for running unattended automations) or User Mode (the recommended option for creating and testing automations, and running attended automations). For more details, see Robot types in the Robot guide.
Note: If you convert the Robot from service mode to user mode, the Robot might not be able to access the
.xamlfiles from the original NuGet Packages folder. For details on how to resolve this, see the NuGet packages not accessible after migration troubleshooting article.
- Automatically Start Assistant with Windows - Launch the Assistant at Windows startup.
- Packages Configuration - Select whether to Install Local Activities.
- Click Upgrade, wait for the installation to complete, and then click Finish.
For information on performing the update from the command line, see Command Line Parameters.
Considerations for Updating from Versions Prior to 2018.4
If the entire UiPath suite is installed on a single machine, and you want to update from v2018.2 or older versions, you are required to first do so on Orchestrator and then Studio and Robot. If you first update your Studio, your Orchestrator instance is removed. This is due to a change in the installers' Upgrade Code.
If you are updating from v2017.1, v2018.1, or v2018.2, note that all old local activities packages are lost. Please back up before updating.
Please keep in mind that, upon upgrade from v2018.2, the activities packages are cumulated in the
If you have projects created with a Studio version prior to v2018.3, and they have dependencies in the
%localappdata%/UiPath/Activitiesfolder, add the path as a feed in the Package Manager, so that the projects can reference them.
After updating from a version prior to v2018.3, Studio performs an automatic migration of dependencies when the project is opened. Read more about Dependency Migration as part of the Core Activities Split.
It is not recommended to perform manual changes to
NuGet.configor any configuration files, and instead, UI or command-line arguments should be used. However, if manual changes were indeed made to configuration files, it is recommended to back up these files before upgrading to a later Studio version.
The location of the activity packs has changed from
%programdata%\UiPath\Activitiesin 2016.2 to
%localappdata%\UiPath\Activitiesin 2018.1 and above.
This means that, when updating from 2016.2 to 2018.1, 2018.2, or 2018.3, the activity packs must be reinstalled to work properly. More info can be found in the Managing Activities Packages chapter.
Updating the Community Edition
If you are using the Community Edition installed using
UiPathStudioSetup.exe and activated with a Community license, Studio is automatically updated as soon as a new version is available, be it Stable or Preview. If the automatic update takes place while you have a project open in Studio, a Studio is updating message and a progress bar are displayed in the Studio status bar. You must restart Studio to complete the update process.
If you installed Studio using with the Community Edition installer and activated it with an Enterprise license, Studio is automatically updated to the latest Stable release, regardless of the update channel you selected.
Starting with v2021.2,
UiPathStudioSetup.exeis a 64-bit installer. Automatic updates are no longer available for Community Edition installations on 32-bit operating systems.
If you manually update your Community Edition Studio, your user settings are not lost, but the existing UiPath extension for Chrome is removed from your browser. The content of the current UiPath folder from
%localappdata%\UiPath installation folder is removed and the setup fails if you previously performed selections with UI Explorer in a Java application. Please note that these issues do not occur when Studio automatically updates to the latest version.
Selecting the Update Channel
You can choose an update channel by going to Home (Studio Backstage View) > Help and selecting either Stable or Preview. Please note that once you change your selection, you have to restart the application for the change to take effect.
Updated about a year ago