Robot release notes

Bug fixes​

• Fixed an issue where the Robot could not interact with the Windows Security prompt (CredentialUIBroker.exe) after certain Windows updates changed its integrity level. The fix allows the Robot executor to run at medium+ integrity level so it can interact with the prompt.

  Unattended (Service Mode): To enable the fix, set the system environment variable UIPATH_MEDIUMPLUS_EXECUTOR=true (this enables the executor to run at medium+ integrity level) and restart the Robot service. This does not apply to Attended/Assistant (User Mode).

  Design time (Studio): To automate this prompt while building the automation, Studio must run with administrator privileges. All UiPath processes must match the elevated permission (all elevated); mixed elevation causes execution to fail. Before starting Studio elevated, close all UiPath processes (for example UiPath.Service.UserHost.exe, UiPath.Executor.exe). If any UiPath process is already running non-elevated and you then start Studio elevated, execution will fail. When you have finished automating the high-integrity window (the Windows Security prompt), close all UiPath processes, restart Studio without administrator privileges, and continue the rest of the automation. To check whether a process is elevated, open Task Manager, go to the Details tab, right-click the column headers, select Select columns, enable Elevated, and check the Yes/No value for each UiPath process. In Task Manager, Elevated = Yes means the process runs at High (or higher) integrity level (administrator); Elevated = No means Medium, Medium+, or lower — Task Manager does not distinguish between Medium and Medium+.

  Limitations:

  • The environment variable applies only to Unattended Robot in Service Mode; it has no effect in User Mode (Assistant, Attended).
  • At design time, the only supported way to automate the prompt is to run Studio elevated after ensuring no UiPath processes are running non-elevated.