- About this guide
- Getting started
- Installing
- Upgrading
- Connecting and licensing
- Configuring
- Running workloads
- RPA processes and tests
- Agents, functions, and API workflows
- Limits
- Securing and governing
- Monitoring
- Troubleshooting
- Reference
Prerequisites
Requirements to check before installing UiPath Robot 2026.10, for every machine and for machines that run unattended automations.
Before you install the Robot, check that the machine and the accounts that run automations are ready.
For every machine
- The Robot version is compatible with your Orchestrator. For the supported combinations, refer to the compatibility matrix.
- The machine meets the hardware and software requirements.
- You have the
UiPathPlatformLTS.26.10.msiinstaller for the Enterprise LTS (26.10 line) channel, available athttps://download.uipath.com/connected-installer/latest/lts-26-10/UiPathPlatformLTS.26.10.msi. For the other channels and their installers, refer to Update channels. - The machine reaches the services the Robot connects to. For the list, refer to Configuring networking settings.
- You have administrator rights, if you install the Robot for all users on the machine (per-machine). A per-user installation doesn't need them. A silent per-machine installation runs from an elevated command prompt. For details, refer to Install the desktop clients.
For unattended automations
An unattended robot signs in to Windows on its own to run each job, so the account set to run the automation needs the rights to open that session.
-
Add the account to the Remote Desktop Users group, in Computer Management > System Tools > Local Users and Groups > Groups > Remote Desktop Users.
-
Open Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.
-
Grant the account, or a group it belongs to, these rights:
- Allow log on locally
- Access this computer from the network, for High-Density Robots only
- Allow log on through Remote Desktop Services, for High-Density Robots only
The account can now open the Windows session the Robot needs. For how the Robot uses that session, refer to Windows sessions.
For agents, functions, and API workflows
Agents, functions, and API workflows run on unattended robots on Windows. In addition to the unattended requirements:
- The robot connects to Orchestrator with client credentials. Robots connected with a machine key don't run these workloads.
- The machine template in Orchestrator has Agent slots or Function slots set above 0. Functions and API workflows use Production (Unattended) runtimes instead when Use Production (Unattended) is selected on the machine template.
- The tenant has units available for agents. Functions and API workflows need units or an unattended runtime.
The executor packages ship with the Robot. The language runtimes they need, such as Python, are not part of the installation: the executors download them the first time they run a job, so the machine needs outbound internet access for that first job. For machines without internet access, refer to Executor packages.
For setup, refer to Enabling agents, functions, and API workflows.