studio
2023.4
false
- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- 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
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Last updated Nov 18, 2024
Automating Applications Running Under a Different Windows User
Automating an application that is running under a different Windows user fails by default.
The application running for the different user is trying to load files from
C:\Users\<UserA>\.nuget\packages\uipath, but it does not have access to that folder.
You need to grant Read & execute permissions to the different user for the UiPath .nuget folder of the current user.
To do so, follow these steps:
- In Windows Explorer, go to
C:\Users\<UserA>\.nuget\packages. - Right-click on the
uipathfolder. The folder properties window appears. - Go to the Security tab.
- Add
<UserB>and grant them Read & execute permissions. - Click Apply and close the properties window.
You can now automate applications running under a different Windows user.
