- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- 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
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Update Service
The Update Service in UiPath Robot is part of a system responsible for managing UiPath updates for the Robot software and components.
The service detects when a new version of the software has been released and manages the update process while ensuring minimal disruption to the ongoing tasks. As an administrator, you can select the specific version to be installed on a your machine.
Operates through two executables:
-
UiPath.UpdateService.Agent.exe- This is the client-side component of the Update Service. It runs under the user context that launched the UiPath Robot and communicates with Update Service Worker.Important:Only present in the User Mode and attended robot installation.
-
UiPath.UpdateService.Worker.exe- This is the actual update component that performs the software updates. It runs as a system service, managing update downloads and installations.
|
Robot installation type |
| UiPath.UpdateService.Agent.exe |
|---|---|---|
|
Unattended |
Installed as a Windows service. |
Not installed. |
|
Attended Important:
To allow the Update Service to connect to the update server, add the Orchestrator URL during the installation. Without it, you need admin permissions to connect the Robot to Orchestrator. | Installed as a Windows service. | Installed as LogOn Task in Task Scheduler. |
|
Quick | Installed as LogOn Task in Task Scheduler. | Installed as LogOn Task in Task Scheduler. |
Automatic updates are standard for UiPath Robot Community Edition users. To prevent task disruptions, these updates are applied only when the Robot is idle.
Enterprise users need to manually control updates to align with their internal IT policies.
Automatic updates do not apply to Linux Robots.
|
Service Mode robots |
User Mode robots |
|---|---|
|
Both Robot and Update services run in the local system session. |
The Robot and Update services run in the user and local system sessions, respectively. |
You can configure update policies for users, user groups, or machines, based on the robot installation type.
|
Attended installations |
Unattended installations |
|---|---|
|
Per machine (for example, LAPTOP-AG1LD). Note:
Robot accounts use update policies set at machine level. |
-
Latest version - Installs the latest available version found on the update server.
-
Latest patch - Installs the latest patch available for each of the supported versions.
-
Specific version - Installs a specific patch from the ones available on the update server.
User-group policies take precedence over user policies set to None. To stop updates for a user, remove them from the policy-enforced group or match their policy to their installed version.
User-level policies set to Specific version value take precedence over the user-group policy.
User-level policies take precedence when a user-level policy, a group-level policy, and a machine-level policy all apply to the same robot.
During an update, you are prompted to stop or save running processes. In case of no response, Studio auto-saves work and closes, while the Robot waits for processes to end before updating. You can resume your work post-update.
|
User-Mode installations |
Service-Mode installations |
|---|---|
|
The update prompt offers two options:
Important:
If you do not respond to the prompt within 24 hours, the system automatically installs the update, which may lead to job failures. | 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.
Important:
If you do not respond to the prompt within 10 minutes, the system automatically installs the update, which may lead to job failures. |
The update process unfolds through the following steps:
-
Downloading: The update service checks for update requests from the update server every three hours and starts downloading if received.
-
Downloaded: Marks successful file download and initializes post-processing.
-
Processing: Involves post-processing of the downloaded file, checks for errors, and commences the installation process if clear.
-
Ready to Install: Alerts the user or checks that Robot, Studio, and Assistant are ready for for update.
-
Install Approved: Once the update service receives approval, actual installation begins.
-
Installing: The newer version is installed, preserving the same settings.
-
Success/Error: Reports the update status to the update server.
After the update process is complete, you must manually restart Robot and Studio.
With a pre-installed Chrome extension, the process auto-updates it. Without it, post-update manual installation is necessary.
In User Mode, an update command to one Robot impacts all users on that machine.
You can configure the auto-update process for robots operating behind a proxy, depending on the on the Robot installation type:
UiPath.config file. Both the Robot Service and the Update Service run using a Windows Service, independent of a user.
UiPath.config file. However, the user starts both the Robot Service and the Update Agent. The Update Service runs using a Windows Service.
For quick installations, configurations for the proxy are inherited from the existing user settings. The user initiates all services: Robot Service, Update Agent, and Update Service.
-
First retry applies one hour after the initial update attempt.
-
Second retry applies two hours after the first one.
-
Third retry applies four hours after the second one.
%localappdata%/Uipath/UpdateService/logs.
If the update is not completed within 72 hours of its start, an error is logged, and the update is retried upon the next request.
To manually retry the update, click the update icon .
You can access the logs for both failed and successful updates:
-
From the Orchestrator interface : Tenant > Machines > select a machine > More actions > Installed Versions & Logs
-
On the machine, in the logs file:
%localappdata%/Uipath/UpdateService/logs
You can check the status of your Robot version for your machines.
On the Orchestrator > Tenant > Machine page, the Version status column displays the update policy status for the corresponding machine. The following values are available:
|
Version status |
Description |
|---|---|
|
No policy |
No update policy is defined for the machine. |
|
Update in progress |
An update process is in progress on the machine. |
|
Compliant |
The robot version on the machine matches the update policy. |
|
Non-compliant |
The robot version on the machine differs from the one set in the policy. |
|
Update failed |
The update process failed. For details, check the update logs. |
|
N/A |
This status appears when the feature to exclude idle machines is active and the robot has not connected for some time, or the machine type does not support the auto-update process. |
When a machine is inactive, the machine template, using the same machine key with the update server, becomes Non-compliant.
To exclude inactive machines, select the Client Binaries box in Orchestrator > Tenant > Settings and adjust the inactivity interval.
For robots deployed on virtual environments involving cloned machine, all attributes, such as machine name, GUID, or drive ID, are the same.
This causes Orchestrator to receive different update statuses from multiple machines sharing identical attributes, leading to duplicate log entries.
In this case, Orchestrator displays the update status of the most recent connected machine.
