- Getting started
- Understanding UiPath Robot
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for High-Density Robots
- Redirecting robots through a proxy server
- Implementing authentication with credential providers
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Using EntraID users with multifactor authentication (MFA) for unattended robots
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Governance
- Troubleshooting
Robot admin guide
Updating UiPath Robot
The update process ensures that both Studio and Robot are upgraded to the latest available version.
Before updating your Robot version, check the compatibility matrix.
When planning for an update, keep the following recommendations in mind:
- Preserve the Robot operational mode: Service Mode or User Mode.
- Match Robot and Studio versions. Refer to the compatibility matrix for guidance.
UiPathRobot.msicannot update an olderUiPathStudio.msiinstallation.Important:When you have Orchestrator installed on the same machine as the Robot, we recommend updating your Orchestrator version first, followed by the Robot version. To apply the new settings, reconnect the Robot to Orchestrator.
Manual update
Manual update is done via Command Line.
This option is available exclusively for Enterprise LTS versions of Robot. Community versions are automatically updated to the latest release. For instance, you can manually update your 2024.10.5 LTS version to the latest 2024.10.9 LTS version. Community installations, however, are always updated to the most recent version, and selecting a specific version is not possible
Updating Service Mode robots
To update a Robot that was initially installed in Service Mode, run UiPathStudio.msi or UiPathRobot.msi with default settings. This replaces old files without altering your settings.
Updating stores activity packages in the C:\Program Files\UiPath\Studio\Packages folder.
To update the Service Mode Robot from the command line using UiPathStudio.msi, write:
UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot,RegisterService
UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot,RegisterService
Updating User Mode robots
To update a Robot that was initially installed in User Mode, run UiPathStudio.msi or UiPathRobot.msi with default settings. This replaces old files without altering your settings.
To update the Service Mode Robot from the command line using UiPathStudio.msi, write:
UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot
UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot
Switching between modes
When switching from Service Mode to User Mode, the Robot might not be able to access the .xaml files from the original NuGet Packages folder.
Updating the configuration variables requires a Robot restart to take effect, but several changes in Orchestrator settings do not need a restart. These include:
RunDisconnectedHours- the number of hours the robot can run offline (disconnected from Orchestrator).- SignalR settings - parameters related to the SignalR technology used for real-time communication between Robots and Orchestrator.
HeartbeatPeriodSeconds- the frequency, in seconds, at which the Robot sends a heartbeat signal to Orchestrator to show it is online.- NuGet feeds - references to package sources for activities.
To switch from User Mode to Service Mode, make sure the RegisterService parameter is added to the ADDLOCAL command.
To switch from Service Mode to User Mode, make sure the RegisterService parameter is removed from the ADDLOCAL command.
Automatic update
Administrators can set up policies for automatically updating Studio, StudioX, Robot, and Assistant from Orchestrator. When a policy triggers the automatic update process, the UiPath Update Agent shows an Update Available notification, prompting you to start the update.
In unattended scenarios, the update service verifies that Robot, Studio, or Assistant are not executing any jobs or processes. Once this is confirmed, the update acknowledgment is sent back to the update server, triggering the update process.
Refer to Update Service for more details.
