- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Properties
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-017 - Invalid parameter modifier
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Troubleshooting
- Trigger-based Attended Automation
- Object Repository
- The ScreenScrapeJavaSupport Tool
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Studio testing
- Troubleshooting
- About troubleshooting
- Assembly compilation errors
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Validation of large Windows-legacy projects takes longer than expected
Update Studio
Studio update management through the UiPath Platform Installer, including options to change the update channel, postpone updates, pin a version, or turn them off.
This page describes how Studio is updated on Windows. On macOS, refer to Updates in the UiPath Platform Installer guide.
Studio is updated by the UiPath Platform Installer, which keeps every desktop client it installed at aligned versions. You don't download or run a new installer for each release, and Orchestrator auto-update policies don't apply to Studio.
Versioning Scheme
UiPath uses calendar versioning, labeling its products with the year of the release (major) followed by the month (minor) and the patch (micro) version.
How updates work
On the Enterprise STS and Community channels, Studio receives new releases as they become available. On the Enterprise STS channel, automatic updates are on by default. For details about the channels, refer to Update channels.
When automatic updates are on:
- The Platform Installer checks for new versions and downloads only the changes from the installed version, in the background.
- On an attended machine, you can postpone an available update for the number of days set by your administrator. A notification is displayed every day, and a final notification is displayed 30 minutes before the update is applied. For details, refer to Postpone an update.
- On an unattended robot, the update is applied between job executions, so running jobs aren't interrupted.
- There is no automatic downgrade. If an update fails, the machine stays on the installed version.
If the Excel add-in is installed, close all Excel processes before an update is applied.
Changing the update channel
The channel decides which versions a machine receives. To move a machine to another channel, for example from Community to Enterprise STS, run the following command from the Updater installation folder (%ProgramFiles%\UiPathPlatform\Updater for a per-machine installation), from an elevated command prompt:
UiPath.Connected.Updater.App.exe set_channel -channel sts
UiPath.Connected.Updater.App.exe set_channel -channel sts
For a per-user installation, add the -perUser flag. For details, refer to Install the desktop clients.
Governing updates
Administrators control updates through Group Policy:
- Channel selection - Assigns machines to a channel.
- Version pinning - Caps the maximum version that machines can update to.
- Artifact mirroring - Serves update binaries from an internal location, for networks with restricted access.
- Update deferral - Sets the maximum number of days users can postpone an update.
- Auto-update - Turns automatic updates on or off.
For details, refer to the UiPath Platform Installer admin guide.
Updating from a classic MSI installation
To move a machine that runs Studio installed with UiPathStudio.msi to the Platform Installer, run the installer for the channel you want: UiPathPlatformSTS.msi for Enterprise STS, or UiPathPlatform.msi for Community. The Platform Installer migrates the existing installation and keeps its settings. After the migration, updates are managed by the Platform Installer and not from Orchestrator. For details, refer to Migrate from the classic MSI.