UiPath Documentation
robot
2026.10
false
Robot admin guide

Upgrading from 2025.10

What changes when you upgrade UiPath Robot from 2025.10 to 2026.10, from the new installer and update model to .NET 10 and the new install folder.

2026.10 includes every change shipped on the short-term support train since 2025.10, starting with 2026.0.179, and the changes that were made after the last short-term support release. Most of them arrive automatically, but the ones in the following table change how you install, update, connect, and script the Robot. Review them before you move machines from 2025.10.

Changes that need action​

ChangeWhat it affectsWhat to do
The UiPath Platform Installer replaces UiPathRobot.msi and UiPathStudio.msiInstallation scripts, deployment packages, golden imagesMove installation to the Platform Installer. Refer to Moving from the MSI to the Platform Installer.
The Update Service doesn't ship in 2026.10Update policies in Orchestrator, update schedulesOrchestrator update policies don't reach 2026.10 robots, because the Update Service applied them. Set the channel, version cap, and postponement through the Platform Installer governance policies, in Group Policy. Refer to Updating the Robot.
Machine key connections are deprecated, and robots connected with a machine key don't run agents, functions, or API workflows by defaultRobots connected with a machine keyReconnect the robots with client credentials. Refer to Moving from a machine key to client credentials.
The Robot installs in its own folder, separate from Studio: %ProgramFiles%\UiPathPlatform\Robot\<version> per-machine, or %LocalAppData%\Programs\UiPathPlatform\Robot\<version> per-user. 2025.10 used C:\Program Files\UiPath\Studio per-machine, or a folder under %LocalAppData%\Programs\UiPath per-user.Scripts and tools that call Robot executables by full path, such as UiRobot.exe and UiPath.LicenseTool.exeUpdate the paths to the new install folder. The folder name changes with every update, so read it from the RobotDir registry value at run time, as described in Install folder.
Live streaming and remote control (RealVNC) isn't installed by default by the Platform InstallerRobots that use live streaming or remote controlSelect Live streaming and remote control in the installer, or set INSTALL_LIVE_STREAMING=true for a silent installation. Otherwise, live streaming and remote control stop working after the move. Refer to Silent installation.
The Platform Installer doesn't downgradeMachines you might need to move back to 2025.10To go back, uninstall the Platform Installer and reinstall the 2025.10 MSI. Refer to Migrate from the classic MSI.
The Robot runs on .NET 10Automations and activities that depend on the .NET runtimeTest critical processes on 2026.10 before you upgrade production machines. For known issues, refer to .NET troubleshooting.

Moving from the MSI to the Platform Installer​

The Platform Installer isn't available for 2025.10, so a 2025.10 machine moves to it as part of the upgrade. When the Platform Installer installs on a machine that has a classic MSI installation, it migrates that installation and keeps its settings.

  1. Download UiPathPlatformLTS.26.10.msi, the installer for the Enterprise LTS (26.10 line) channel. For the download location, refer to Installing the Robot.
  2. Run it on the 2025.10 machine.
  3. Check that the Robot is connected to Orchestrator and, for an unattended robot, that the UiPath Robot Windows service is registered.

The migration keeps the following:

  • The Robot service and the Orchestrator connection
  • The Robot settings
  • The NuGet feeds
  • The installed features
  • The browser extensions

The machine runs Robot 2026.10, on the Enterprise LTS (26.10 line) channel. On this channel, automatic updates are off by default until an administrator turns them on. Refer to Update channels. For what the migration keeps, refer to Migrate from the classic MSI.

New in 2026.10​

These changes need no action, but are worth knowing before you upgrade:

  • Agents, functions, and API workflows run on unattended Windows robots through Unified Runtime.
  • Machine-level proxy. Robot processes can take their proxy from the machine-level proxy.json file, with the UIPATH_APPLY_SERVICE_PROXY machine environment variable. Refer to Redirecting robots through a proxy server.
  • Verbose log cap. By default, the Robot keeps at most 10,000 verbose logs per executor process, then logs a warning and drops further verbose logs from that process. To change the limit, set the UIPATH_VERBOSE_LOG_LIMIT environment variable. Refer to Environment variables.
  • Licensed job time. The Robot reports how long each job ran, and Orchestrator uses that duration, so time spent disconnected no longer counts as execution time.

For every change since 2025.10, refer to the 2026.10 release notes.

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated