- About this guide
- Getting started
- Installing
- Upgrading
- Upgrading from 2025.10
- Updating the Robot
- Connecting and licensing
- Configuring
- Running workloads
- RPA processes and tests
- Agents, functions, and API workflows
- Limits
- Securing and governing
- Monitoring
- Troubleshooting
- Reference
Updating the Robot
How UiPath Robot 2026.10 stays current through UiPath Platform Installer update channels, and how updates reach attended and unattended robots.
In 2026.10, the UiPath Platform Installer updates the Robot. The Update Service, which updated earlier versions, doesn't ship in 2026.10. Each machine follows an update channel, and the Platform Installer downloads updates for that channel in the background and applies them. On the Enterprise LTS (26.10 line) channel, automatic updates are off by default, until an administrator turns them on. Refer to Update channels.
Before you update, check the compatibility matrix. Update Orchestrator first, then the Robots.
Update channels
| Channel | Version format | What the machine receives |
|---|---|---|
| Enterprise LTS 26.10 | The 26.10 line | Patch updates within the 26.10 line only |
| Enterprise STS | YYYY.0.N | Each new short-term support release |
| Community | — | Community releases |
The Platform Installer reports a platform version, such as 26.205.<build>, in the Version registry value. Each desktop client has its own product version, such as 26.10.0-<suffix>.<build> for the Robot. A 2026.10 patch is a new platform version with new product builds.
The STS channel works only with Automation Cloud Orchestrator connections.
A machine installed from the 26.10 LTS installer stays on the 26.10 line. You can change the channel later without reinstalling. For how, refer to Change the update channel.
For support dates, refer to Product lifecycle.
How updates reach the Robot
- Unattended robots install the update between jobs. A running job is never interrupted, and no one needs to act.
- Attended robots show a notification. The user can update right away or postpone, up to the postpone period your update policy sets. When that period ends, the update installs on its own.
For the attended experience and the postpone policy, refer to Postpone an update.
Control updates across machines
Administrators control updates through Group Policy, or through registry values under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\UiPath\Platform:
| Policy | Registry value | Effect |
|---|---|---|
| Channel selection | Channel | Assigns machines to an update channel, such as the 26.10 LTS line |
| Version pinning | MaxAllowedVersion | Caps the version a machine can update to. Machines don't take updates above it. |
| Update deferral | MaxPostponeDays | Sets how many days users can postpone an update. 0 turns postponing off. The default is one day. |
| Auto-update | AutoUpdateDisabled | 1 turns automatic updates off |
| Artifact mirroring | DownloadRootLocation | Serves update files from an internal URL or network share |
To roll out a version in stages, apply the policies to groups of machines, such as a pilot group before production. No policy sets a maintenance window. To control when unattended robots update, combine version pinning with your rollout groups, and raise MaxAllowedVersion when a group is ready. For the procedure, refer to Deploy governance policies.
Linux robots
Linux robots don't update through the Platform Installer. To update one, deploy the Docker image of the newer version. Refer to Installing on Linux.