- Getting started
- Understanding UiPath Robot
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for High-Density Robots
- Redirecting robots through a proxy server
- Implementing authentication with credential providers
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Governance
- Troubleshooting

Robot admin guide
Description
Occasionally, robots cannot find a mapped network drive when running unattended automation, especially when running background processes.
Potential issue
This can happen due to the non-interactive nature of the Windows logon session.
Solution
Map the network drive in the headless mode for every job the robot starts by running the following command:net use Z: \\unc\path
net use Z: \\unc\path
Description
Trying to run a package from a network path or an Azure File Share fails with the "System.Xaml.XamlObjectWriterException: Cannot create unknown type [....]" error.The robot logs the following error message: "System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework."
Potential issue
The Robot machine might not trust the web address for the Azure File Share, where the package is located. Alternatively, the account the robot uses might lack permissions for that specific location.
Solution
Make sure that the account under which the robot runs has the necessary permissions. Then, add the Azure File Share web address as a trusted network on the robot machine.
Description
The Robot machine becomes unresponsive and shows high CPU usage at some point after starting the automation. It occurs on Windows 10 v1903 machines.
Potential issue
DWM.exe
file, leading to high CPU usage upon completion of a Remote Desktop session.
Solution
Apply the KB4522355 update on the faulty Windows machine.