Setting up package folders and network paths

Setting up a fallback package folder

To set up a fallback package folder:

Add the NUGET_FALLBACK_PACKAGES variable to your system environment.
For the variable, add the list of the absolute paths for the folder, separated by semicolons.
Important:
- If the environment variable does not exist, the robot tries to read the NuGet packages fallback folders from the Nuget.config file.
- Processes deployed in fallback folders are not supported, only dependencies.

Changing the download path for packages

The default download path for packages is %userProfile%\.nuget\packages.

To change the package download location, you can either edit the UiPath.config file, or use the PACKAGES_FOLDER="new/download/path" parameter via the command line when installing Studio or Robot.

To edit the UiPath.config file, follow these steps:

Open the configuration file. You can find it in the C:\Program Files\UiPath\Studio folder.
In the packageSettings section, add a new entry called packagesInstallationFolder. Then, set its value as the path of the new download folder.
Save the changes and, if the Robot is installed as a service, restart the service.

Note:
When changing the download folder, make sure that all users that need to run automations can access it.

For example:

<packageSettings>
  <add key="packagesInstallationFolder" value="C:\Nuget" />
</packageSettings><packageSettings>
  <add key="packagesInstallationFolder" value="C:\Nuget" />
</packageSettings>

Setting up local and network paths

You can set a local or network path to enable several robots to use the same path. The setup depends on the robot operational mode: Service Mode or User Mode.

On Windows Server machines that allow concurrent executions on High Density Robots, you need to set up unique paths for each user. Using the same shared folder for all users in High Density environments is supported with some limitations:

Robot mode	Path type	Considerations for multiple robots using the same path
Service mode	Local path	No restrictions
Service mode	Network path	Not supported when Secure XAML is used. Service mode robot installed on separate machines must have its own folder on the network. Mapped network paths, such as `Z:\Packages`, are not supported. Use non-mapped path, such as `\\server\Packages`.
User Mode	Local path	You must add the `NUGET_SCRATCH` environment variable on the robot machine, and provide it with a value other than the NuGet installation one. This sets a different path for storing temporary NuGet files, to prevent potential conflicts when multiple robots attempt to use NuGet simultaneously. The new temporary folder should be exclusive for the `NUGET_SCRATCH` variable. The user accounts under which robots run must have read and write access to both NuGet folders on the machine.
User Mode	Network path	The path must include the machine name and username. `<packageSettings> <add key="packagesInstallationFolder" value="\\NetworkServer\SharedFolder\UiPath\Packages\" /> </packageSettings>`<packageSettings> <add key="packagesInstallationFolder" value="\\NetworkServer\SharedFolder\UiPath\Packages\" /> </packageSettings>

On this page

Setting up a fallback package folder
Changing the download path for packages
Setting up local and network paths

Was this page helpful?

PREVIOUSConfiguring preloaded execution

NEXTCrowdStrike integration

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy