- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-017 - Invalid parameter modifier
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Troubleshooting
- About troubleshooting
- Assembly compilation errors
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Hardware and Software Requirements
Minimum | Recommended | |
---|---|---|
CPU Cores (*) | 2 x 1.8 GHz 64-bit (x64) |
4 x 2.4 GHz 64-bit (x64) |
RAM | 8 GB of available system memory |
12 GB |
Disk Space |
|
N/A |
(*) UiPath does not support the ARM architecture on Windows.
Supported Versions | Particularities | |
---|---|---|
Operating System |
Windows 10 Windows 10 N |
Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version (required for GIT source control) |
Windows 11 |
Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022, x64 version (required for GIT source control) | |
Microsoft Azure Windows 10 Enterprise Multi-Session | Works in conjunction with Azure Virtual Desktop
(AVD) as well.1 Supports Windows 365 machines. | |
Windows Server 2016 |
Microsoft Visual C++ Redistributable for Visual Studio 2015,
2017, 2019, and 2022, x64 version (required for GIT source
control)
2 | |
Windows Server 2019 |
Microsoft Visual C++ Redistributable for Visual Studio 2015,
2017, 2019, and 2022, x64 version (required for GIT source
control)
2 | |
Windows Server 2022 |
Microsoft Visual C++ Redistributable for Visual Studio 2015,
2017, 2019, and 2022, x64 version (required for GIT source
control)
2 | |
XenApp v6.5 or greater | ||
XenDesktop v7.0 or greater | ||
.NET Framework |
Version 4.6.1 or greater |
.NET Framework is required for running Windows - Legacy projects and must be installed on machines. 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. .NET (formerly .NET Core) is a newer framework required for running Windows and cross-platform projects. The appropriate .NET version (Desktop Runtime) is automatically added in the installation folder when installing or upgrading Studio. |
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 Edge or the Webdriver protocol. | |
Microsoft Edge in IE mode (Internet Explorer v8.0 or greater) 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 | ||
File System | NTFS | |
IP | IPv4, IPv6 | Studio can be installed on IPv6-compatible operating systems. |
- Various display issues may occur in Studio if the Nahimic Service
software in installed on your machine. This component is also included in
other third-party applications such as Asus ROG Xonar Phoebus Sonic Studio
and Asus Sonic Studio. We recommend disabling the Nahimic service in Windows
or renaming the file
NahimicOSD.dll
. 1
- When using unattended robots on Virtual Machines, do not leave the Azure Virtual Desktop sessions indisconnected
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 indisconnected
state. When this scenario happens, the job eventually fails due to a time out.
2
- This component is installed by default with the operating
system and should be reinstalled if removed.