- 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
NuGet Packages Not Accessible After Migration
"Access to path
C:\Users\john.doe\.nuget\packages\HelloWorld\1.0.0\lib\net45\Main.xaml is denied".
When the Robot is deployed in Service Mode, packages are downloaded and installed in a folder (e.g.
.nuget\packages) by the Local System user that the robot is running service under.
When converted to User Mode, NuGet packages from that folder are no longer accessible as the current user that runs the Robot does not have permissions to view or edit those files.
1. Deleting all packages from the original folder:
If you choose to delete packages from the original folder, the Robot reinstalls the processes in the configured folder under the user's permission. This way, the Robot has access to the files whenever it needs to run them.
2. Changing the packages folder:
When converting the Robot from Service-Mode to User-Mode, you can change the packages installation folder from
%userprofile%\.nuget\packages to a different path, like
This causes the Robot to re-create the
.nuget\packages folder and download the processes in it so they can later be used.
By default, activities packages are downloaded and installed in the
%userprofile%\.nuget\packages folder. You can set a different folder in one of the following ways:
- During installation, by installing from the
with the option
After installation, by manually editing the
- Open the
uipath.configfile in a text editor. By default, the file is located in
- In the
packageSettingsnode, add the
packagesInstallationFolderkey with the path to the new folder as its value.
Save the changes and restart the robot.
For example, add the following to
uipath.configto change the download location to
<packageSettings> <add key="packagesInstallationFolder" value="C:\nuget" /> </packageSettings><packageSettings> <add key="packagesInstallationFolder" value="C:\nuget" /> </packageSettings>
- Open the
For more details around the differences between Service-Mode and User-Mode Robots, read the according to deployment document which provides a more detailed description of each type of Robot.