Changes to Installation Folder Structure in UiPath Studio/Robot v26.0.198

Japan Knowledge Base
,
1

■Overview

In UiPath Studio/Robot v26.0.198, the structure of the default installation folder has been changed.

This change does not affect the screen operations of Studio and Robot, licensing, connection to Orchestrator, or running processes, and you can continue to develop in Studio and run automation in Robot as usual.

However, please note that if the locations of UiPath executables or configuration files are specified as absolute paths in your scripts, monitoring tools, management tools, and security products, review of the references will be necessary after the upgrade.

■Changes

  1. Studio and Robot will not be structured together in the same folder, but instead, will be organized into separate folders for Studio and Robot under one product root.

Example:

  • Before Change: C:\Program Files\UiPath\Studio (Studio and Robot are placed in the same folder)

  • After Change: C:\Program Files\UiPathPlatform (Studio and Robot are placed in separate subfolders)

  1. The main executable for Studio, UiPath.Studio.exe, and the Studio application will be placed under the Studio\ folder.

  2. The main executable for Robot, UiRobot.exe, the Robot/Assistant services, command line tools, Diagnostic Tool, License Tool, and shared configuration files will be placed under the Robot\ folder.

  3. Configuration files: UiPath.config and nuget.config will be placed under the Robot\ subfolder. If these configuration files are referenced with absolute paths, updates to the references will be necessary.

  4. The placement of the package folder will not change. When Studio is installed, it will be located under Studio<version>, and when Robot is installed, it will be located under Robot<version>. The entries for the local feed in NuGet.config will be updated to match the path of the package folder at installation.

  5. The registry configuration will be updated. The key itself will remain HKEY_LOCAL_MACHINE\SOFTWARE\UiPath\UiPath Studio, but StudioDir for Studio components and RobotDir for Robot components will be written separately. The process of locating executables using InstallDir should be changed to use StudioDir or RobotDir. RobotAgent will be an absolute path.

  6. Standard upgrades from older versions will automatically transition to the new folder structure. For normal upgrade operations, no manual actions for folder migration are required.

  7. If you are using the Connected Installer (the installer version for STS), Studio will depend on the Robot product, and the Robot product will be placed under Robot<version> instead of Studio<version>. Configurations that reference UiRobot.exe, UiPath.config, NuGet.config, UiPath.DiagnosticTool.exe, and UiPath.LicenseTool.exe from under Studio<version> will be affected.

■Settings that Need Confirmation

  1. Custom scripts or automation that reference UiRobot.exe, UiPath.Studio.exe, various service executables, UiPath.config, or nuget.config with absolute paths.

  2. Application allowlists such as antivirus software, EDR, AppLocker, and WDAC that are based on absolute paths for executable files.

  3. Deployment and management tools, such as SCCM, Intune, GPO, and custom scripts, that reference executable paths after installation.

  4. Monitoring, inventory, and asset management tools that are based on absolute paths.

  5. Shortcuts pinned to the desktop/start menu created with custom provisioning. Note: Shortcuts created by the installer will continue to function.

■Points That Remain Unchanged

  1. The functionality and UI of Studio and Robot will not change.

  2. Licensing, connection to Orchestrator, and running processes will remain unchanged.

  3. Command line parameters at installation, shortcuts, and protocol handlers like UiPath-assistant:// will not change.

  4. Studio and Robot will continue to include the necessary runtime in the product. Therefore, there is no need to install additional runtimes with the upgrade.

■Measures

  1. Before upgrading, please check for any locations where paths to UiPath executables or configuration files are specified as absolute paths.

  2. In processes that reference the installation locations of Studio or Robot, change to a method that uses StudioDir and RobotDir instead of relying on the old InstallDir or fixed absolute paths.

Note: If you are obtaining the installation path with custom scripts or batch files, please revise the references to use StudioDir or RobotDir.

Also, the environment variable UiPath_USER_SERVICE_PATH will have the full path of UiPath.Service.UserHost.exe set (e.g., C:\Program Files\UiPathPlatform\Robot\26.0.199-cloud.24445\UiPath.Service.UserHost.exe). Since this value is a path to the executable, if you are only using the folder, it will require processing on the script side to obtain the directory portion.

  1. If your antivirus software, EDR, AppLocker, or WDAC use absolute paths for allowlisting, please update the rules before the upgrade to reflect the new executable paths under the new Studio\ and Robot\ structure.

  2. If you are referencing old absolute paths in SCCM, Intune, GPO, custom provisioning, or pinned shortcuts on the desktop/start menu, please update to match the new folder structure.

  3. If your implementation manuals, operational procedures, monitoring configurations, or asset management rules document the installation paths for Studio/Robot as absolute paths, please update them.

Reference:
Robot Release Notes - August 2026
Robot - August 2026