- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Restarting Robot Components
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Robot Citrix Apps Virtualization
- Troubleshooting
- Common Connection Errors
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET required during installation
- Assembly Cannot Be Loaded From Network Or Azure File Share
- Activities cannot find .NET Runtime
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.
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. |
Web Browsers (for browser automation) | Microsoft Edge 78 or greater with Internet Explorer (IE) mode |
Internet Explorer as a desktop application is out of support starting June 15 2022, Internet Explorer 11 being the last major version. We continue to provide the support for Microsoft Edge with Internet Explorer (IE) mode, which offers built-in legacy browser support for sites requiring Internet Explorer (see more details here). Automated with the extension for Microsoft Edge. |
Google Chrome version 64 or greater |
Automated with the extension for Chrome or the Webdriver protocol. | |
Mozilla Firefox version 52.0 or greater |
Automated with the extension for Firefox or the Webdriver protocol. | |
Microsoft Edge on Windows 10 version 1803 or greater |
Automated with the extension for Microsoft Edge. | |
Microsoft Office (for projects created in the StudioX profile) | Office 2013 | |
Office 2016 | ||
Office 2019 | ||
Office 2021 | ||
Office 365 | ||
IP |
IPv4 | |
IPv6 |
Assistant can be installed on IPv6-compatible operating systems. |
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.