# Silent installation

> Install UiPath Robot 2026.10 without prompts, using the UiPath Platform Installer from the command line and a platformConfig.json file.

A silent installation runs the UiPath Platform Installer from the command line with no prompts. Use it to script an installation, or to deploy the Robot to many machines. A configuration file, `platformConfig.json`, selects the Robot and sets its parameters. The UiPath Platform Installer, distributed as an MSI package named `UiPathPlatformLTS.26.10.msi`, replaces the `UiPathRobot.msi` and `UiPathStudio.msi` installers, which don't ship for 2026.10.

For more details about the Platform Installer, refer to [Install the desktop clients](https://docs.uipath.com/uipath-platform-installer/standalone/latest/user-guide/install) and [Update channels](https://docs.uipath.com/uipath-platform-installer/standalone/latest/admin-guide/update-channels).

## Install the Robot silently

1. Create a `platformConfig.json` file that requests the Robot package and sets its parameters. For an example, refer to [Robot parameters](#robot-parameters).
2. Open an elevated command prompt. A silent installation runs per-machine only when the command prompt is elevated, and service mode needs a per-machine installation.
3. Run the installer with the configuration file:

   ```
   msiexec /i UiPathPlatformLTS.26.10.msi PLATFORM_CONFIGURATION_FILE="C:\Config\platformConfig.json" /qn
   ```

   The LTS installer sets the channel itself, so you don't pass a channel.

To install silently with the offline installer, refer to [Offline installer](https://docs.uipath.com/uipath-platform-installer/standalone/latest/user-guide/install-from-the-command-line#offline-installer). To deploy the Robot with Configuration Manager (SCCM) or Intune, refer to [Deploy with Configuration Manager or Intune](https://docs.uipath.com/uipath-platform-installer/standalone/latest/admin-guide/deploy-with-configuration-manager-or-intune).

The Robot is installed without prompts. Connecting at install time with a client ID and secret works only for a per-machine installation with the Unattended robot type (`REGISTER_ROBOT_SERVICE` set to `"true"`). `SERVICE_URL`, `ORCHESTRATOR_CLIENT_ID`, and `ORCHESTRATOR_CLIENT_SECRET` are all required, and the installer skips the connection if any is missing. The connection is best effort: after installing, check that the robot is connected in Assistant or on the **Machines** page in Orchestrator. If it isn't, [connect the Robot to Orchestrator](https://docs.uipath.com/robot/standalone/2026.10/admin-guide/connecting-robots-to-orchestrator-unattended) after the installation.

For every installer parameter and the format of both configuration files, refer to [Install from the command line](https://docs.uipath.com/uipath-platform-installer/standalone/latest/user-guide/install-from-the-command-line).

The `PROXY_*` installer parameters of earlier versions don't exist for the Platform Installer. To install behind a proxy, put the proxy settings in an updater configuration file and add `UPDATER_CONFIGURATION_FILE="C:\Config\updaterConfig.json"` to the `msiexec` command line. For the file format, refer to [Install from the command line](https://docs.uipath.com/uipath-platform-installer/standalone/latest/user-guide/install-from-the-command-line#updaterconfigjson-updater_configuration_file). For the proxy the Robot itself uses, refer to [Redirecting robots through a proxy server](https://docs.uipath.com/robot/standalone/2026.10/admin-guide/redirecting-unattended-robots-through-a-proxy-server).

## Robot parameters

The Robot's parameters are set in the `Robot` entry of `platformConfig.json`. Parameter values are strings, and on/off parameters take `"true"` or `"false"`.

The following example installs an unattended robot in service mode, connects it to Orchestrator with client credentials, and installs the browser extensions, which are a separate package:

```json
{
  "Packages": [
    {
      "PackageName": "Robot",
      "InstallRequested": true,
      "Parameters": {
        "REGISTER_ROBOT_SERVICE": "true",
        "SERVICE_URL": "https://cloud.uipath.com/<Organization_Name>/<Tenant_Name>/orchestrator_",
        "ORCHESTRATOR_CLIENT_ID": "<Client_ID>",
        "ORCHESTRATOR_CLIENT_SECRET": "<your-client-secret>",
        "INSTALL_LIVE_STREAMING": "true"
      }
    },
    {
      "PackageName": "BrowserExtensions",
      "InstallRequested": true,
      "Parameters": {
        "INSTALL_CHROME_EXTENSION": "true",
        "INSTALL_EDGE_EXTENSION": "true"
      }
    }
  ]
}
```

Assistant is a separate package that depends on the Robot, and the Robot installs without it. For attended use, request the `Assistant` package next to the `Robot` package, as in the following example of an attended robot in user mode:

```json
{
  "Packages": [
    {
      "PackageName": "Robot",
      "InstallRequested": true,
      "Parameters": {
        "REGISTER_ROBOT_SERVICE": "false"
      }
    },
    {
      "PackageName": "Assistant",
      "InstallRequested": true,
      "Parameters": {}
    }
  ]
}
```

The Robot package accepts the following parameters:

| Parameter | Description |
| --- | --- |
| `REGISTER_ROBOT_SERVICE` | `"true"` registers the Robot Windows service, so the Robot runs in service mode. Per-machine installations only. A per-user installation ignores it. |
| `SERVICE_URL` | The Orchestrator URL. Required with `ORCHESTRATOR_CLIENT_ID` and `ORCHESTRATOR_CLIENT_SECRET`, with `ORCHESTRATOR_AUTO_SIGNIN`, and with `ENFORCE_DEFAULT_SERVICE_URL`. |
| `ORCHESTRATOR_CLIENT_ID` | The client ID of the machine template or standard machine. Set it together with `ORCHESTRATOR_CLIENT_SECRET`. Only with `REGISTER_ROBOT_SERVICE` set to `"true"`: the installer rejects client credentials otherwise, including in a per-user installation. A per-user robot never runs in service mode, so use `ORCHESTRATOR_AUTO_SIGNIN` or sign in from Assistant instead. Can't be used with `ORCHESTRATOR_AUTO_SIGNIN`. |
| `ORCHESTRATOR_CLIENT_SECRET` | The client secret that goes with `ORCHESTRATOR_CLIENT_ID`. |
| `ORCHESTRATOR_AUTO_SIGNIN` | `"true"` signs attended users in to `SERVICE_URL` automatically. Can't be used with `REGISTER_ROBOT_SERVICE` set to `"true"`. |
| `ENFORCE_DEFAULT_SERVICE_URL` | `"true"` enforces `SERVICE_URL` as the Orchestrator URL for all users of a user mode robot. |
| `LICENSE_KEY` | A Robot license code to activate on the machine without Orchestrator. |
| `PACKAGES_FOLDER` | The folder the Robot downloads process packages to. |
| `NUGET_OPTIONS` | `DisableOnlineFeeds` stops the Robot from using the online activity feeds. The default is `EnableOnlineFeeds`. |
| `CUSTOM_NUGET_FEEDS` | Additional package feeds, in the form `Name1,Source1;Name2,Source2`. |
| `INSTALL_ROBOTJS` | `"true"` installs RobotJS. On a first silent installation, a per-user installation or a per-machine installation without the Robot service installs it even if you leave it out. |
| `INSTALL_LIVE_STREAMING` | `"true"` installs the RealVNC components used for live streaming and remote control. Off unless you set it. |
| `ASSISTANT_STARTUP` | `"true"` starts UiPath Assistant when the user signs in to Windows. |
| `DISABLE_SECURE_XAML` | `"true"` turns off XAML protection for Windows - Legacy projects. |
| `ENFORCE_SIGNED_EXECUTION` | `"true"` runs only signed packages. |

Telemetry isn't a Robot parameter. To turn it off, add the Platform Installer property `TELEMETRY_ENABLED=0` to the `msiexec` command line.