"Cannot access application 'credentialuibroker.exe'. Elevated privileges might be required. Try running the UiPath application as an administrator." error after Patch-Tuesday update 13.01.2026

Help Robot
21

Unfortunately this solution does not seem to work. Disabling secure desktop still won’t allow UiPath interacting with the window.

My team ended up with disabling secure desktop: User Account Control Switch to the secure desktop when prompting for elevation - Windows 10 | Microsoft Learn

We find the listed vulnerabilities that it mitigates:

Elevation prompt dialog boxes can be spoofed, causing users to disclose their passwords to malicious software. Mouse cursors can be spoofed by hiding the real cursor and replacing it with an offset so the cursor is actually pointing to the Allow button.

don’t do much for RPA, as it usually checks the running process when interacting with a dialog.

The approved " Run all administrators in Admin Approval Mode" is much more risky since it makes running all processes with admin priviledges by default (assuming the robot account has admin priviledges).

22

Hi all,

We have/had this issue when trying to connect a remote desktop via .rdp file.

We were able to uninstall the Security update KB5073457 for Windows Server 2022. That did the trick. (At least on the development machine. Haven’t tried it on the productive VM, but should still work.)

On the Microsoft info page (Windows Server 2022 known issues and notifications | Microsoft Learn) it’s mentioned as known issue, and as resolve there is another patch K5077800 (January 17, 2026—KB5077800 (OS Build 20348.4650) Out-of-band - Microsoft Support)

image
image781×210 13.1 KB

We did not install this patch K5077800 yet. Just informed our IT about it, then let’s see if they can make it available to us.

23

Hi,

we tried both OOB updates from Microsoft KB5077800 and KB5078136 for Windows Server 2022.
None resolved the issue, and I also think no future patches will.
In the end Microsoft made the decision to make the credential broker more secure, I do not think they will revert that.

1 Like
25

Hi there. I would love to try using the OSK BUT right now when I try it, UiPath won’t let me indicate the osk window as an app. I tried to manually enter the path to the exe file but UiPath says that the c:\windows\system32\osk.exe file doesn’t exist, even though I can clearly see the file in explorer. Did you need to do anything special to get UiPath to interact with the OSK?

26

Can you try these steps and let us know if those helped with not setting the above GPO "Cannot access application 'credentialuibroker.exe'. Elevated privileges might be required. Try running the UiPath application as an administrator." error after Patch-Tuesday update 13.01.2026 - #10 by Hassan_Raza and still using the latest Windows OS patches?

  • Install/upgrade the impacted robot using this installer https://download.uipath.com/versions/25.10.6/UiPathStudio.msi or https://download.uipath.com/versions/24.10.19/UiPathStudio.msi

  • Add this system environment variable, UIPATH_MEDIUMPLUS_EXECUTOR = true and restart the UiPath Robot service (UiRobotsvc).

    In a PowerShell console as Administrator, this command execution should set the needed system environment variable:

    [Environment]::SetEnvironmentVariable("UIPATH_MEDIUMPLUS_EXECUTOR", "true", "Machine")

  • Sign out from the robot user session

  • Retry to run the old broken automation from Orchestrator (unattended mode) where it has the issue with CredentialUIBroker popup.

References:

1 Like
27

Hello Marian
we have installed Studio 24.10.19, added System environment, restarted the server, but still we are not able to use CredentialBroker, it says elevated privileges required once you try to select pop up window.
Is there any additional steps we could try ?
Besides we are using Edge extension 24.10.3. Edge version: 144.0.3719.115
Could you post version you used and it all worked?
Thank you.

28

Hello Marian
we have installed Studio 24.10.19, added System environment, restarted the server, but still we are not able to use CredentialBroker, it says elevated privileges required once you try to select pop up window.
Is there any additional steps we could try ?
Besides we are using Edge extension 24.10.3. Edge version: 144.0.3719.115
Could you post version you used and it all worked?
Thank you.

29

Hi Marian,

the Studio version 2024.10.19, will it still support legacy projects?
The linked release note refers to Robot version 2024.10.19.

30

Unfortunately, the same situation with version 25.10.6, it still does not resolve the issue.
We installed Studio version 25.10.6 and set the environment variable UiPath_MEDIUMPLUS_EXECUTOR=TRUE for machine and user variables (just to be sure). We also restarted our machine twice and created a fresh project with updated library versions.

31

Does the UiPath Service require the Medium+ integrity level as well? We checked the integrity level using Microsoft Sysinternals Process Explorer. The CredentialUIBroker has medium+ but the UiPath processes have only medium.

32

The update works for our processes. Studio version 2024.10.19.
Key note: it does not work in the studio, only on the unattended processes.

33

Microsoft now has this listed as a Known Issue for all OS’s, but doesn’t have any plans to change it as its part of new security requirements.

Remote sharing apps and automation apps become unable to autofill credentials

WI1230201, Windows Server 2022

Last updated: Feb 10, 2026, 4:06 AM EST

Originating time: Jan 13, 2026, 1:00 PM EST

Resolved time: Feb 10, 2026, 4:05 AM EST

Status

Resolved

User impact

This behavior is part of new security requirements. Temporary workarounds are available.

Is this post helpful?

Latest message View history

After installing Windows updates released January 13, 2026 (KB5073457) or later, certain applications might fail to autofill credentials during remote support sessions or automated authentication workflows. Users and IT administrators might observe the following symptoms while trying to connect to another device using screen sharing or a third‑party remote or automation tool: - Applications attempting to autofill credentials into the Windows authentication dialog and sign-in interfaces might fail to do so - Credential dialogs do not respond to virtual keyboard input from remote desktop or screen sharing tools or apps, such as Microsoft Teams or similar third-party apps. - Automatic or scripted authentication workflows cannot proceed because the credentials interface no longer accepts input Please note: This intentional behavior results from new security hardening, designed to protect users against untrusted input injection (see CVE‑2026‑20824 for details). Following installation of the January security update, Windows authentication dialogs will only accept input from trusted local sources, such as physical keyboard input, trusted accessibility applications with UIAccess privilege, or applications running with elevated (administrator) integrity. Resolution: Please note that Windows credential interfaces will continue to be protected against input from remote or automated tools for security reasons. Remote keystroke injections, remote virtual keyboards, and automated credential submission from remote tools will continue to be restricted, and authentication dialog will ignore input (including virtual keyboard inputs) if credentials are entered from non-trusted contexts. Applications should be updated to avoid keyboard entry into credential interfaces and instead authenticate through supported Windows authentication interfaces. Workaround: This change in behavior may be temporarily mitigated using the following workaround. Applications performing remote credential submission can be configured to run in an elevated (administrator) privilege. This should allow the previous behavior until applications can be updated to account for the hardening changes driven by CVE‑2026‑20824 [link]. Note: This workaround should only be used in tightly controlled environments where the application handles trusted inputs, trusted data, and trusted endpoints. Workarounds should remain temporary until the application is updated to avoid keyboard entry into credential interfaces and instead authenticate through supported Windows authentication interfaces. If your screen sharing app is failing to input passwords, you can use an accessibility app like Quick Assist as a temporary workaround until your screen sharing app is updated. If your organization needs immediate help to mitigate this issue, please contact Microsoft Support for business. Microsoft continues to work with application development partners to assist compliance with evolving security hardening requirements. Affected platforms: - Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016 - Server: Windows Server 2025; Windows Server 23H2; Windows Server 2022; Windows Server 2019; Windows Server 2016 to manage email notifications for Windows known issues

34

Did you run the job from Orchestrator, or from Assistant?

35

Did you run the job from Orchestrator or from Assistant?

36

From the studio. Is it working only for unattended robot ?
Are you planning to fix it for studio as well as it not comfortable to debug process and develop if it’s not working.

37

Yes, we tried to run the job in both Orchestrator and Studio according to the instructions in your post, but we are still receving the error message.

Use Application: Windows-Sicherheit: Cannot access application ‘credentialuibroker.exe’. Elevated privileges might be required. Try running the UiPath application as an administrator.

Could you please share if there are any other requirements or system settings that need to be configured?

38

The Product team shared this information for 2025.10.6:

“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+.“

39

Hi @lukasf, can you share what is the integrity level of UiPath.Service.Host.exe from Process Explorer? You might need to start Process Explorer as an administrator.

image
image1728×132 58 KB

40

Hi, and for version 2024 it also works? Thanks

41

Hi @marian.platonov and @george.neamtu,

I ran the automation again based on your suggestion and it is now working in Unattended Mode.

Unfortunately, we are facing another issue. In our setup, we require two RDP hops to reach the target server. The RDP connection from the Bot-Machine → Jumpserver is working now, but the the RDP connection from Jumpserver → Target-Server fails with the same error message:

Use Application: Windows-Sicherheit: Cannot access application ‘credentialuibroker.exe’. Elevated privileges might be required. Try running the UiPath application as an administrator.

We have installed UiPath Remote Runtime version 25.10.19 on the Jumpserver. Could you please confirm if this fix is already included in the latest Remote Runtime version 25.10.26?

Additionally, could you please clarify if the environment variable UIPATH_MEDIUMPLUS_EXECUTOR = true needs to be set at the machine level or if user level is sufficient?

Thank you in advance!