- UiPath Assistant
- Installing UiPath Assistant
- Hardware and Software Requirements
- Installing UiPath Assistant
- Configuring UiPath Assistant
- Assistant on MacOS
- Picture in picture
- Configuring attended automations
- Governance
- Widgets in Assistant

Assistant user guide
Hardware and Software Requirements
Minimum | Recommended | |
---|---|---|
CPU (*) |
2 x 1.8GHz 64-bit (x64) |
4 x 2.4GHz 64-bit (x64) |
RAM (**) |
4 GB |
8 GB |
Disk Space (***) |
UiPathStudio.msi:
N/A |
(*) UiPath does not support the ARM architecture on Windows.
(**) Automations that use Document Understanding frameworks might need additional RAM.
(***) The disk space requirements do not include the space for the automation dependencies, such as packages and libraries.
You can also check out hardware requirements for Studio and Orchestrator.
Supported Versions | Particularities | |
---|---|---|
Operating System |
Windows 10 Windows 10 N | |
Windows 11 | ||
Microsoft Azure Windows 10 Enterprise Multi-Session |
Works in conjunction with Azure Virtual Desktop (AVD)
as well.
1 Supports Windows 365 machines. | |
Microsoft Azure Windows 11 Enterprise Multi-Session | Supports Windows 365 machines. | |
Windows Server 2016 Windows Server 2019 Windows Server 2022 | ||
Windows Server Core 2016 Windows Server Core 2019 Windows Server Core 2022 |
Can only run background unattended jobs. The
jobs run under the local system account by default. To use a
specific user (credentials specified in Orchestrator), you need to
configure the
UIPATH_HEADLESS_WITH_USER environment
variable on the robot machine and set the value to
True .
| |
MacOS version 10.15 (Catalina) or greater. | Required by the UiPath Assistant for Mac. | |
XenApp v6.5 or greater | ||
XenDesktop v7.0 or greater | ||
.NET Framework |
Version 4.6.1 or greater |
If your machine runs Windows OS in a language other than English, install the corresponding language pack for the .Net framework version you are using. This is required for running Studio in any of the available languages. The .Net framework and related language pack version must correspond, and any conflicting .Net framework versions installed on the machine should be removed. |
1
When using unattended robots on Virtual Machines, do not leave
the Azure Virtual Desktop sessions in disconnected
state (user
is connected to a host pool in an AVD environment, but they are still connected
to the session hosts). The robot is not able to use the disconnected session
as it was created via AVD and does not have access to it. Because of this, it
attempts to create a new session to run the unattended job, but fails because the
AVD session is already created and in disconnected
state. When this
scenario happens, the job eventually fails due to a time out.