UiPath Platform Installer user guide

The classic MSI installer (UiPathStudio.msi) and the UiPath Platform Installer can both be used to install the UiPath desktop clients. The classic MSI remains supported; the UiPath Platform Installer 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 again 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, see the introduction.

When the UiPath Platform Installer is installed on a machine that already has a classic MSI installation, it migrates the existing installation and preserves its settings. The preserved settings are the same as those configurable in a clean Platform Installer installation: Studio and Robot settings, browser extension settings, and proxy settings. End users do not need to take any action, and the desktop clients continue to work as before — they are now kept up to date automatically.

Once migration completes, the UiPath Platform Installer manages updates for the desktop clients, and updates are no longer managed from Orchestrator. Update governance — the update channel and the allowed version — is configured through policy by IT (see the admin guide). For the earlier Orchestrator-based update model, see Auto-updating client components.

To move a machine back to the classic MSI, uninstall the UiPath Platform Installer and reinstall the desktop clients with the classic MSI (UiPathStudio.msi). The settings after reverting are the same as they were before the Platform Installer was installed.

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.