Why does UiPath Studio or Robot keep auto-updating to a different version even when Orchestrator update policies are set correctly and auto-update settings are disabled?
Issue Description:
UiPath Studio or Robot automatically updates to an unintended version (e.g., from LTS to STS) even after:
- Orchestrator's Auto Updating Client Components / Client Binaries policies are configured to a pinned version or set to None
- The user has disabled auto-update within Studio's settings
- The correct version has been reinstalled and hardcoded at the machine level
This issue may affect individual machines or a wider group of users, and persists across reinstalls.
Resolution:
When Orchestrator policies and UiPath-native settings have been ruled out, the update is likely being triggered by a third-party endpoint management or patch deployment tool such as ManageEngine Endpoint Central (UEMS), Microsoft SCCM, Ivanti, or similar platforms.
How to Identify the Root Cause:
- Open Event Viewer on the affected machine and filter for entries around the timestamp when the update occurred.
- Look for a Windows Installer transaction log entry referencing a path outside of UiPath's standard directories, for example:
Beginning a Windows Installer transaction: C:\Program Files (x86)\ManageEngine\UEMS_Agent\patches\<UiPathStudio>.msi - If the MSI path points to a third-party agent's patch directory (e.g., ManageEngine\UEMS_Agent\patches\, SCCM\, Ivanti\), the update is being pushed externally not by UiPath services.
Key Indicators That a Third-Party Tool Is Responsible:
- The update runs under NT AUTHORITY\SYSTEM
- The MSI is sourced from a non-UiPath directory
- The UiPath Update Service, Orchestrator, Assistant, and Studio are all confirmed not to have initiated the update
- The issue recurs even after reinstalling the correct version and configuring UiPath policies
Recommended Action:
Coordinate with your IT / Endpoint Management team to:
- Identify whether UiPath Studio is included in any active patch deployment policies within your endpoint management platform
- Remove or exclude the UiPath Studio MSI from automated patch deployments
- Ensure only the approved LTS version is distributed if managed deployment is still required
Once the third-party deployment is disabled and the correct version is reinstalled, monitor for 24–48 hours to confirm the version is holding stable.
Related Areas to Check (Ruling Out UiPath-Native Causes)
| Area | What to Check |
|---|---|
| Orchestrator Policies | Client Binaries / Auto Updating Client Components → confirm set to pinned version or None |
| UiPath Update Service | services.msc → confirm service is running and not misconfigured |
| Install Mode | Confirm whether Studio was installed in Service Mode vs. User/Quick Mode |
| Registry Scope | Confirm hardcoded settings are applied to HKLM / ProgramData, not just HKCU |