- About UiPath Assistant
- UiPath Assistant on Mac
- Field Descriptions
- Automation Configuration
- Task Capture Launcher
- Assistant Governance
- UiPath Assistant for Excel add-in
- About Backward and Forward Compatibility
- Hardware and Software Requirements
- Updating the Robot
- Setting Up Windows Server for High-Density Robots
- Services the Robot Connects to
- UiPath.Settings File Description
- 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
- 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
Increased Process Execution Duration
Process execution takes almost twice as long when Studio is installed from
UiPathStudioSetup.exe (Community Edition), compared to
UiPathStudio.msi (Enterprise Edition). The issue occurs on Studio v2018.4.6 and above.
Studio Community Edition is installed in
%localappdata%\UiPath, which is not a trusted location by Windows Defender. This means that every time a log file is created, Windows Defender
starts to scan it, which prolongs the process execution.
The scenario does not apply to Studio Enterprise Edition, because the installation folder (
%ProgramFiles%\UiPath) is trusted by Windows Defender, and thus not scanned every time a log file is created during the execution of a process.
Adding the Studio Community Edition installation folder (
%localappdata%\UiPath) on the Windows Defender exclusion list means log files created during the process execution are no longer scanned on the
spot. To add a folder on the Windows Defender exclusion list, you need to perform the following steps:
- Click the Windows Start button, then search for Virus & threat protection and open it.
- Access the Virus & threat protection settings page.
- Access the Add or remove exclusions page from the Exclusions section.
- Click the Add an exclusion button, then choose Folder from the drop-down menu.
- Navigate to the
%localappdata%\UiPathfolder, then click the Select Folder button. Please note that Administrator rights are required to add a folder on the exclusion list.
Log files created during the process execution are no longer scanned on the spot by Windows Defender.