robot
2022.10
false
- Getting Started
 - Installation and Upgrade
 - Robot Types
 - Robot Components
 - Licensing
 - Connecting Robots to Orchestrator
 - Processes and Activities
 - Logging
 - 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
 
 - Governance
 - Troubleshooting
- 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
 - CrowdStrike integration troubleshooting
 
 

Robot User Guide
Last updated Jun 4, 2025
Workflows using specific activity packages fail when run on 2023.4.0 and newer robots
               with one of the following errors: 
               
            
            
            "To run this application, you must install missing frameworks for .NET.""To run this application, you must install .NET."
The following activity packages are impacted:
- UiPath.Form.Activities version 2.0.x
 - UiPath.IntelligentOCR.Activities
 - UiPath.MobileAutomation.Activities
 - UiPath.Vision
 - UiPath.DocumentUnderstanding.Activities
 - OCR related activities in the UiPath.UIAutomation.Activities package
 - UiPath.OmniPage.Activities
 - UiPath.OCR.activities
 
Upgrade the activity packages of the affected workflows to the following versions:
- UiPath.Form.Activities 2.0.x -> 2.0.7
 - UiPath.IntelligentOCR.Activities -> 6.9.1
 - UiPath.MobileAutomation.Activities -> 23.4.0
 - UiPath.Vision -> 3.10.1
 - UiPath.DocumentUnderstanding.Activities ->2.2.2
 - OCR related usage from UiPath.UIAutomation.Activities fixed in ->23.4.5
 - UiPath.OmniPage.Activities -> 1.15.0
 - UiPath.OCR.activities -> 3.15.1
 
            Add an Invoke Code activity at the start of the affected
            workflow with the following statement:
            “
         
         
         
         
         
      System.Environment.SetEnvironmentVariable("DOTNET_ROOT",
               System.AppContext.BaseDirectory)”.