studio
2025.10
false
- 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-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
 - Troubleshooting
 
 - Trigger-based Attended Automation
 - Object Repository
 - The ScreenScrapeJavaSupport Tool
 - Extensions
- About extensions
 - SetupExtensions tool
 - Configure a multi-hop connection
 
- 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
 
 - Studio testing
 - 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
Last updated Oct 30, 2025
To reach a destination remote computer via multiple connections, you must install Remote Runtime on each intermediary remote computer, not only on the final target computer.
Consider the following scenario:
                  
               
               - Machine A (with Studio and/or Robot) connects via RDP (Microsoft Remote Desktop Protocol) to Machine B, and
 - Machine B connects via RDP to Machine C, where the target application is running, and the automation must be performed.
 
In this example, the following configuration is required:
                  
               
               - Machine A – install Studio/Robot and the Extension for Microsoft Remote Desktop and Apps (UiPath RDP extension).
 - Machine B – install the Extension for Microsoft Remote Desktop and Apps and 
UiPathRemoteRuntime.msi. - Machine C – install 
UiPathRemoteRuntime.msi. 
If other types of connections are used between two machines, you must configure a connection at each hop, with the appropriate
                  extension:
                  
               
            - Extension for Citrix for the case of Citrix connection
 - Extension for Microsoft Remote Desktop and Apps (UiPath RDP extension) for the case of RDP connection
 - Extension for VMWare Horizon for the case of VMWare connection
 - Extension for Amazon WorkSpaces for the case of connections to Amazon WorkSpaces
 
Let's consider another scenario in which:
                  
               
               - Machine A (with Studio and/or Robot) connects via RDP to Machine B, and
 - Machine B connects via Citrix to Machine C, where the target application is running, and the automation must be performed.
 
On Machine B (or other intermediary machines), you can install the extension with one of these methods:
                  
               
            - Run the 
UiPathRemoteRuntime.msiinstaller and select from the Product Features list the required extension. Refer to Installing the UiPath Remote Runtime - From the Installer. - From Command Prompt run 
SetupExtensions.exe(located in the folderC:\Program Files (x86)\UiPath\RemoteRuntime) with the parameter corresponding to the required extension: 
               A more difficult to detect scenario is for example the one where Windows Remote Desktop is published as a RemoteApp, and this
               Remote Desktop is used to access the target application through a RDP connection:
               
This may initially seem like a direct connection from the Machine A to the Machine C via RDP, but it is actually a multi-hop scenario.
               
               
               
               
            
            - Machine A (with Studio and/or Robot) uses Windows Remote Desktop published as a RemoteApp on Machine B, and
 - Machine B accesses through an RDP connection the Machine C where is running the target application.
 
This may initially seem like a direct connection from the Machine A to the Machine C via RDP, but it is actually a multi-hop scenario.
Such a configuration can be identified:
- by trying to indicate a target UI element in the target application. In this case you can observe in the selector a window
                     having the class 
'RAIL_WINDOW'. Example:<wnd app='mstsc.exe' cls='RAIL_WINDOW' title='...' /> 
- by opening the 
.rdpfile with a text editor, where the following line can be found:remoteapplicationmode:i:1 
UiPathRemoteRuntime.msi needs to be installed on the 2 remote machines from this double-hop setup:
               - The remote machine from where the Remote Desktop is published as a RemoteApp (Machine B).
 - The remote machine to which we RDP to access the target application (Machine C).
 
- Run the 
UiPathRemoteRuntime.msiinstaller and select from the Product Features list the UiPath extension for Microsoft Remote Desktop. Refer to Installing the UiPath Remote Runtime - From the Installer. - From Command Prompt run 
SetupExtensions.exe(located in the folderC:\Program Files (x86)\UiPath\RemoteRuntime) with the parameter corresponding to the UiPath extension for Microsoft Remote Desktop. 
Regardless of your multi-hop connection scenario, if you are automating a Java application or a web application, you must
                  also install the corresponding extension (the extension for Java, Chrome, Microsoft Edge, Firefox) on the remote machine.
                  This can be done by running:
                  
               
            - the 
UiPathRemoteRuntime.msiinstaller, as described in Installing the UiPath Remote Runtime, or - the 
SetupExtensions.exetool located in the installation folder of UiPath Remote Runtime (default%ProgramFiles(x86)\UiPath\RemoteRuntime), as described in About the SetupExtensions tool.