"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
1

After the Patch-Tuesday update on 13.01.2026, I am getting the following error from my jobs running in unattended mode from orchestrator:

“Cannot access application ‘credentialuibroker.exe’. Elevated privileges might be required. Try running the UiPath application as an administrator.”

The processes are all running from a server where the robot user is admin. The first step is to open a remote desktop session using a saved connection. When the robot needs to type the password, it cannot access the application ‘credentialuibroker.exe’.

I have identified that something in the Patch-update is causing the issue by restoring the server to a version before the update, and running the process again without errors. Microsoft documentation for the update can be found here: January 13, 2026—KB5073457 (OS Build 20348.4648) - Microsoft Support.

I am not sure exactly which part of the update is causing the issue or how to find a good solution. For now, I have taken out the server from the update cycle as a temporary solution. But I need to find a solution that will work with the update.

Event logs from the server when getting the error:
A fatal error occurred while creating a TLS client credential. The internal error state is 10013.
The SSPI client process is smartscreen (PID: 11144).

Running as an administrator is not an option. As stated in this issue https://forum.uipath.com/t/how-to-overcome-this-error-message-in-studio-cannot-access-application-elevated-privileges-might-be-required-try-running-the-uipath-application-as-an-administrator/540204: “From unattended we don’t and we’ll never support running processes with elevated rights. It’s too big of a security risk.”

Does anyone have an idea of how to overcome this issue?

Cannot access application 'credentialuibroker.exe'. Elevated privileges might be required. Try running the UiPath application as an administrator
2

Hi @msj

Run as Robot admin user on server (elevated CMD):

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart UiPath Service: net stop UiPathService && net start UiPathService

In Use Application Credentials activity: Enable “Use secure credentials”

This resolves post-KB5073457 Credential UIBroker access blocks without elevation.

3

Hi @msj

The January 13, 2026 Windows update tightened security, causing the robot to lose access to credentialuibroker.exe during unattended runs when typing passwords in remote desktop sessions. Running as admin is not an option due to security risks.

  • Update UiPath Robot and Studio to the latest versions.
  • Avoid UI-based password entry; use Credential Manager or Orchestrator Assets for secure credentials.
  • Use saved RDP credentials or alternative remote session methods like PowerShell remoting.
  • Check and adjust Group Policy settings related to credential delegation carefully if needed.
  • Consider contacting Microsoft since the error relates to TLS/SSPI changes in the update.

For now, avoiding UI interaction with credential dialogs and using stored credentials is the best approach.

4

Hi @msj

You can try this approach

1 Use Orchestrator Credential Assets
2 Use Secure Credentials enabled
3 Avoid Windows credential UI
4 Keep UiPath & Windows patches aligned

Hope it helps

5

After doing all the settings mention above still not working

6

Hello, I am facing the same issue but KB5073457 is not installed in my server. and having same issue.

7

I have tried running the elevated commands as suggested by @arjun.shiroya, but am unsure of what is meant with the point "In Use Application Credentials activity: Enable “Use secure credentials” - could you be more specific here?

To elaborate a bit on my current setup: I am using Orchestrator Assets to store the credentials and using the activity UiPath.Core.Activities.TypeSecureText with this selector

<wnd app='credentialuibroker.exe' cls='Credential Dialog Xaml Host' title='Windows Security' />
<ctrl automationid='PasswordField_2' />

to type the password.

I am not interested in using saved RDP credentials. In regards to PowerShell remoting, I have not been able to find a good solution that ensures, the password is not typed as plain text. @Monali_Vekariya do you have a specific method in mind here, and if so, could you elaborate on it?

@nishiijain2000 I am not sure about step 2, that you are suggesting. Where exactly can I enable “Use Secure Credentials”?

8

Hello,

I have the same error in some of my productive processes. I was able to implement a workaround so that the login screen is not displayed (automatic login for intranet sites (Edge Browser)).

I recommend opening a support ticket with UiPath. I assume that a large number of processes are affected.

Best Regards,
Dennis

1 Like
9

@msj In use Application credential activity there you need to enable use secure credential.

10

Update or Roll Back UAC Policy (High Success Rate)**

Many users fixed this exact popup by changing this group policy:

Disable:

User Account Control → Run all administrators in Admin Approval Mode
[forum.uipath.com]

Steps:

  1. Press Win + R
  2. Type: gpedit.msc
  3. Navigate:
Local Computer Policy → Windows Settings → Security Settings 
→ Local Policies → Security Options
  1. Find: User Account Control: Run all administrators in Admin Approval Mode
  2. Set it to Disabled
  3. Restart the machine

This forces elevation to behave consistently, fixing CredentialUIBroker issues introduced by patches.

3 Likes
11

Currently facing the same problem. Updating to OS Build 20348.4650 (Windows update) did not fix the issue.

12

Thank you for the suggestion @Hassan_Raza! This solved the issue.

13

I have created a Ticket with support, since disabling the UAC is not an option, security-wise. Will post solution if post is still open, otherwise feel free to reach out.

3 Likes
Forum Engagement Daily Reports
14

We’ve been hit by the same issue. Currently asking IT to roll back the update for a breather to fix things.. Did anything come from your ticket?

15

Nothing yet. I’ve sent their support a sample project and a Diagnostic Tool log, as requested, waiting to hear back. I sent it earlier today.

16

We are having the same issue in a few environments.
So far none of the suggested solutions removed the issue.

We use two workarounds at the moment but both should not become permanent solutions

**1)**Where possible add the credentials to the Windows Credential Manager, this can be done programmatically and temporary.

For example for RDP this would work from PowerShell, you could also use Start Process from UiPath for each command:

# Setcredentials directly into Windows Vault - generic:TERMSRV is for RDP, if you need to set credentials for a different application this key looks deifferent

System.Diagnostics.Process.Start("cmdkey", "/generic:TERMSRV/YourServerAddress /user:YourDomain\YourUser /pass:YourPassword")

#Launch RDP (It will now auto-login without showing the broken prompt)

System.Diagnostics.Process.Start("mstsc", "/v:YourServerAddress")

#Wait a few seconds for connection, then clear credentials

System.Threading.Thread.Sleep(5000)

System.Diagnostics.Process.Start("cmdkey", "/delete:TERMSRV/YourServerAddress")

**2)**Let UiPath click on the on-screen keyboard :wink: I have attached a video.

image
image1573×725 113 KB

image
image1543×840 134 KB

3 Likes
17

I have gotten this response from support:
"Based on what we know, as of now, our customers have encountered this Windows security pop-up in the following situations:

While accessing a webpage (Example: CRM - MS Dynamics 365) in a browser
During RDP connection: Connect to a remote server using mstsc.exe

*The following is the collective list of Windows patches reported by the customers, which is causing the issue *
KB5074159 - Windows 11 version 25H2, all editions Windows 11 version 24H2, all editions
KB5073723 - Windows Server 2019 Win 10 Ent LTSC 2019
KB5073457 - Windows Server 2022
KB5073724 - Windows 10 ESU Windows 10 Enterprise LTSC 2021

Customers have not reported the following patches. However, found via Microsoft documentation for different OS editions, and it could be related to this issue:
KB5073379 - Windows Server 2025, all editions
KB5073450 - Windows Server, version 23H2
KB5073455 - Windows 11 version 23H2, all editions

We could replicate this behavior internally and could observe that the Integrity level for CredentialUIBroker.exe process is now Medium+. after installing the mentioned KB.

Before this security update it was Medium and could be automated without admin privileges.

In this situation the misbehavior of our UiPath products is a consequence.

We can suggest following workarounds
Approach #1:
Quicker, but the customers may disagree to follow these due to security concerns
A: Launch Studio/Robot as administrator
B: Uninstall the patch applied to the machine
C: Disabling User Account Control: Run all administrators in Admin Approval Mode group policy

Approach #2:
Should be a safer option as of now. Shared by one of the customers
A: Configure the credentials of the webpage/RDP connection (mstsc.exe) in the Windows Credential Manager. This will not display the pop-up
B: It’s important to note that this approach may not work for an RDP connection scenario if the Credential Guard is enabled on the server/machine"

They are working on a more permanent solution, but for now we only have workarounds.
I have reached out to my own IT department, regarding lowering the integrity level of ‘credentialuibroker.exe’ back to medium. Might be a better semi-permanent solution for now.

1 Like
18

Morning,
Thank you for keeping us updated.
We’re having the issue not from RDP but for logging onto a website that uses ‘Www-Authentication: Negotiate’ causing windows to pop-up the prompt. I’m trying to wrap my head around what possible mitigations we have.

@bbot, you mention lowering the integrity level of ‘credentialuibroker’ is that even an option? Does an admin have such control over windows?

19

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.