- User guide
- Introduction
- Install the desktop clients
- Install from the command line
- Install on macOS (Preview)
- Migrate from the classic MSI
- Postpone an update
Migrate from the classic MSI
Move a machine from the classic MSI installation to the UiPath Platform Installer, keeping the installed products and settings, and revert to the classic MSI if needed.
The classic MSI installer (UiPathStudio.msi) and the UiPath Platform Installer can both be used to install the UiPath desktop clients. The classic MSI is available for 2025.10 and earlier releases. From 2026.10 on, the desktop clients ship only through the UiPath Platform Installer, which adds automatic, delta-only updates on top of the same clients. You can move a machine from the classic MSI to the UiPath Platform Installer, and back to a classic release if needed.
UiPath recommends moving to the UiPath Platform Installer for automatic, delta-only updates that do not interrupt unattended work, and to remove per-release installer redistribution. For the full list of benefits, refer to the introduction.
Installing the UiPath Platform Installer on a machine that already has a classic MSI installation upgrades that installation in place, with no separate migration step. It applies to every edition of the classic installer — UiPathStudio.msi, UiPathStudioCloud.msi, the trial variants, and UiPathRobot.msi — and to any installed version, because the installer recognizes the classic products by their Windows Installer upgrade codes, not by file name.
Before you begin
- Download the latest UiPath Platform Installer for the update channel you want the machine on. An older Platform Installer cannot migrate a classic installation.
- The Studio or Robot version published on that channel must be the same as or newer than the installed one. A channel that publishes an older version rejects the migration.
- Make sure the drive that holds the installation folder has at least 2.4 GB free. The space used by the classic installation is not counted, because it is removed only after the new clients are installed.
- Close Studio, Assistant, and any running automations. The installer closes any UiPath process that is still open, and it does not wait for unattended jobs to finish. For unattended robots, run the migration in a maintenance window.
- If both
UiPathStudio.msiandUiPathRobot.msiare installed on the machine, they must have the same installation scope (both per-user or both per-machine). Otherwise the migration fails. - Use an elevated command prompt, or a deployment tool that runs as
SYSTEM, to migrate a per-machine installation.
How the migration works
-
The installer detects the classic Studio and Robot products and reads their installation folder, installed features,
uipath.config, andnuget.config. -
The installation scope follows the existing installation: a per-user classic installation is migrated per-user, a per-machine one per-machine. The
MSIINSTALLPERUSERandFORCE_PERUSERparameters are ignored during a migration. This also applies to the offline installer (UiPathPlatformOffline.exe): the scope it requests is replaced by the scope of the existing installation. -
In interactive mode, the installer asks for confirmation before changing anything:
We're upgrading your UiPath Studio to use the new installer, enabling smaller updates and automatic upgrades. Before continuing, please close all UiPath applications (Studio, including running automations). If any UiPath apps remain open, the installer will close them before proceeding.
For a Robot-only installation, the message refers to Assistant instead of Studio. Select OK to continue, or Cancel to leave the classic installation untouched. A silent installation (
/qn) migrates without asking. -
The installer closes the remaining UiPath processes, removes the classic MSI products through Windows Installer, and installs the clients from the channel into the UiPath Platform Installer folder, with the settings listed in What is preserved.
-
The classic installation folder is deleted, and the installer reports The product was successfully upgraded.
End users do not need to take any action. The desktop clients continue to work as before, and from this point on the UiPath Platform Installer keeps them up to date. Updates are no longer managed from Orchestrator: update governance — the update channel and the allowed version — is configured through policy by IT (refer to the admin guide). For the earlier Orchestrator-based update model, refer to Auto-updating client components.
On an Enterprise Long-Term Support (LTS) channel, automatic updates are turned off by default after the migration, so the machine behaves like a classic MSI installation until an administrator enables them. Refer to Update channels.
What is preserved
Installed products
The installer requests the products that match the classic installation:
| Product | Installed when |
|---|---|
Studio | The classic Studio feature was installed. |
Robot | Always. |
Assistant | The channel publishes Assistant (it is bundled with Robot otherwise). |
Runtimes | The channel publishes Runtimes. |
BrowserExtensions | At least one browser or remote-desktop extension was installed. |
Settings
The settings below are read from the classic installation and applied to the new one. They correspond to the product parameters of a clean command-line installation.
| Setting | Read from | Applied as |
|---|---|---|
| Orchestrator URL | uipath.config | SERVICE_URL |
| Automatic sign-in to Orchestrator | uipath.config | ORCHESTRATOR_AUTO_SIGNIN |
| Enforced default Orchestrator URL | uipath.config | ENFORCE_DEFAULT_SERVICE_URL |
| Packages download folder | uipath.config | PACKAGES_FOLDER |
| Secure XAML disabled | uipath.config | DISABLE_SECURE_XAML |
| Online feeds disabled | uipath.config | NUGET_OPTIONS |
| Proxy settings | uipath.config | PROXY_* |
| Telemetry | uipath.config | TELEMETRY_ENABLED, unless passed on the command line |
Signed execution enforced (require mode only) | nuget.config | ENFORCE_SIGNED_EXECUTION |
| Custom activity feeds | nuget.config | CUSTOM_NUGET_FEEDS |
| Robot installed as a Windows service | Installed features (per-machine only) | REGISTER_ROBOT_SERVICE |
| Robot JavaScript add-on | Installed features | INSTALL_ROBOTJS |
| Live Streaming | Installed features | INSTALL_LIVE_STREAMING |
| Excel add-in | Installed features | INSTALL_EXCEL_ADDIN |
| SAP Solution Manager plugin and host | Installed features | INSTALL_SAP_SOLMAN, SAP_SOLMAN_HOST |
| Chrome, Edge, Firefox, Java, Silverlight, Citrix, Remote Desktop, VMware, and Amazon WorkSpaces extensions | Installed extensions | INSTALL_*_EXTENSION, plus CHROME_INSTALL_TYPE and EDGE_INSTALL_TYPE |
| Marketplace widget in Assistant | UIPATH_DISABLE_MARKETPLACE_WIDGET environment variable | ASSISTANT_OPTIONS |
| Installer language | Registry | INSTALLER_LANGUAGE |
| Installation ID | Classic update service | Kept, so the machine stays the same in telemetry |
Proxy
The PROXY_* parameters configure the Robot. The UiPath Platform Installer needs its own proxy settings to download updates, and the migration takes them from the first of these sources that has any:
- The file passed with
UPDATER_CONFIGURATION_FILE. When passed, it is used even if it contains no proxy settings. - The machine-level
%ProgramData%\UiPath\Shared\proxy.jsonthat Robot 2025.10 and later use. It is read only for per-machine migrations. - The proxy settings in
uipath.config, for classic versions 2024.10 and older.
For a per-user installation of 2025.10 or later behind a proxy, pass UPDATER_CONFIGURATION_FILE, because neither of the other sources applies.
The user and robot data folders are not touched by the migration: %ProgramData%\UiPath, %LocalAppData%\UiPath, %AppData%\UiPath, and the packages folder (by default %UserProfile%\.nuget\packages) stay in place.
What changes
| Aspect | Classic MSI | After the migration |
|---|---|---|
| Installation folder | %ProgramFiles%\UiPath\Studio or %LocalAppData%\Programs\UiPath\Studio (or a custom folder) | %ProgramFiles%\UiPathPlatform\ or %LocalAppData%\Programs\UiPathPlatform\, with each product in <product>\<version>\ |
| Apps and features entry | UiPath Studio, UiPath Robot | UiPath Platform |
| Windows Installer upgrade code | Studio: 63828A34-54AE-49FE-AEF7-9D81A499D6B8Robot: 95A0D093-AC57-4CF7-BEEF-8557EB93A6E0 | BF77B981-530C-4984-87AC-FBFDBBA4F8AB |
| Updates | Re-run the MSI, or Orchestrator auto-update | Delta updates from the update channel, governed by policy |
The following differ from a clean installation:
- A custom classic installation folder is not carried over. The clients are always installed under the UiPath Platform Installer folder.
- Product folders include the version and change with every update. Detection rules in deployment tools should use the new upgrade code, or the
UiPathPlatformfolder rather than a versioned path. For application control, prefer publisher rules over path rules: the per-user folder is writable by the user, so a path rule on it trusts anything placed there. - A
PLATFORM_CONFIGURATION_FILEpassed on the command line is ignored during a migration, because the configuration is rebuilt from the classic installation. One exception: when the classic installer predates the Live Streaming feature (for example, 2023.10), the file'sINSTALL_LIVE_STREAMINGvalue on theRobotpackage is applied; without it, Live Streaming is installed.
Migrate from the command line
Run the UiPath Platform Installer for the channel with msiexec, as described in Install from the command line. No parameters are required for the migration itself. For example, to migrate silently to the Enterprise LTS 26.10 line:
msiexec /i UiPathPlatformLTS.26.10.msi /qn /l*v "C:\Windows\Temp\UiPathPlatform-migration.log"
msiexec /i UiPathPlatformLTS.26.10.msi /qn /l*v "C:\Windows\Temp\UiPathPlatform-migration.log"
The offline installer (UiPathPlatformOffline.exe) migrates a classic installation the same way. It extracts its payload to a local mirror and runs the same installer package from there, passing its command line through to msiexec, so the same parameters, checks, and exit codes apply. Its own log, UiPath.Connected.Updater.OfflineStub.log, is written next to the installer logs (%TEMP% for per-user, %SystemRoot%\SystemTemp for per-machine). For example:
UiPathPlatformOffline.exe /qn /l*v "C:\Windows\Temp\UiPathPlatform-migration.log"
UiPathPlatformOffline.exe /qn /l*v "C:\Windows\Temp\UiPathPlatform-migration.log"
- The classic MSI command-line parameters —
ADDLOCAL,PACKAGES_FOLDER,ORCHESTRATOR_URL,REGISTER_ROBOT_SERVICE, and the others — are ignored by the UiPath Platform Installer. The matching settings are taken from the classic installation instead, as listed in Settings. TELEMETRY_ENABLEDandUPDATER_CONFIGURATION_FILEare honored. Refer to Proxy for how the configuration file relates to the migrated proxy settings.- Pass
CHANNELonly to place the machine on a channel other than the one the installer pre-selects.
Exit codes
| Exit code | Meaning |
|---|---|
0 | The migration succeeded. |
1602 | The user selected Cancel in the confirmation dialog. The classic installation is unchanged. |
1603 | A check failed before the migration started, or the installation failed. The reason is in the verbose log (/l*v), as one of the messages below, or in the installer log described in Troubleshooting. |
| Message in the log | Cause | Solution |
|---|---|---|
This UiPath Platform is an older version. In order to migrate from another product, please use the latest version of the installer. | The channel already has a newer UiPath Platform Installer than the one you ran. | Download the current installer for the channel. |
The installed version of UiPath Studio per-machine (...) is newer than or not compatible with the version you are trying to install (...). | The channel publishes an older Studio or Robot than the one installed, or the two classic products have different installation scopes. | Choose a channel whose version is the same or newer. If the scopes differ, uninstall one of the classic products first. |
Insufficient disk space on the drive: C:\. Required 2400 MB. | Less than 2.4 GB free on the drive of the installation folder. | Free up disk space and run the installer again. |
Revert to the classic MSI
To move a machine back to the classic MSI:
- Uninstall UiPath Platform from Apps and features, or run
msiexec /xwith the UiPath Platform Installer package. This removes the desktop clients and the UiPath Platform Installer data folder (%ProgramData%\UiPathConnectedor%LocalAppData%\UiPathConnected). - Install the desktop clients with the classic MSI of a 2025.10 or earlier release (
UiPathStudio.msi), using the same installation scope as before. On a machine migrated to 2026.10 or to the Enterprise STS channel, this is a downgrade.
The UiPath Platform Installer does not remove the %ProgramData%\UiPath, %LocalAppData%\UiPath, and %AppData%\UiPath folders or the packages folder, so the Studio, Robot, and Assistant settings stored there are available to the classic installation again.
Projects and settings saved by the newer Studio or Robot are not converted back. Their compatibility with the older release follows the downgrade rules of those products, not of the installer.
Coexistence
The two models are not mutually exclusive across an organization: some machines can stay on the classic MSI while others use the UiPath Platform Installer. A single machine, however, is managed by one model at a time — either the classic MSI or the UiPath Platform Installer.