Windows Security Popup (CredentialUIBroker.exe)

[Dan.Lister]

We have recently been impacted by the latest Windows Update (KB5074109). We run processes for clients and internally that launch RemoteApps through various means, Remote Desktop Connection Center / Saved .RDP files which causes the Windows Security popup to appear (CredentialUIBroker.exe).

We've always attached to this process and entered creds and then built the system that launches using Surface Automation. This has run perfectly for years. After this update we can no longer interact with CredentialUIBroker.exe or the Windows Security window. Copilot is now telling us the following:- 

The Windows Security prompt is now fully non-automatable
As of January 13, 2026 Patch Tuesday, Microsoft hardened:

Winlogon
Credential UI
Secure Desktop rendering over RDP
These prompts now:

Run on Secure Desktop
Are isolated in Session 0
Block UI Automation, Win32 hooks, accessibility tools
Explicitly prevent programmatic interaction
This is intentional and security-driven, following exploitation of Desktop Window Manager (DWM) vulnerabilities patched in January 2026

We've tried pre-saving credentials using cmdkey, but aren't having any luck with this as yet. For one of our apps we download a digitally signed .rdp and within that file it is set to always prompt from credentials so we can't stop it doing it.

Has anyone found the same issue/found a workaround?

[naveed_raza]

okay , let us know , what fix they suggested

[Carol.Ouellet]

[Retracted Reply]

[Michael_S]

Hi all,

Just dropping in to say:

1. We're aware of the issue and our engineering team investigating
2. As soon as we have practical advice to share, I'll add it in here for all to use

Please continue to let us know if you have attempted workarounds or fixes that may help the community.

Thank you to @Dan.Lister @Carol.Ouellet @naveed_raza @steven.boggs for raising the issue, highlighting the specific problems with examples and suggesting workarounds. 

[RaimondvandeSteeg]

Thanks for the explanation.

Within our organisation, we are required to roll out all Windows updates within two weeks, including on VM’s, due to security vulnerabilities. Because of that, keeping updates limited to Test/ACC only isn’t an option for us — Production will automatically be updated as part of the rollout.

What we mainly expect here is for Blue Prism to proactively identify and communicate the impact of these kinds of changes (e.g. Windows updates that modify UI/system dialogs). Ideally, we’d have early visibility on what changes, how it affects spying/interactions, and a clear workaround or fix pattern so we can prepare before it hits Production.

[Carol.Ouellet]

To add to RaimondvandeSteeg

I think Blue Prism probably has some sort of automated testing suites to check if Patch Mondays break things. If not then this is quite probably buildable. Even having some AI read all the patch notes and try to compare and build recommendations on what to test and what are the possible risks.

[Michael_S · Accepted solution]

Hi all, 

We have some suggested workarounds for you provided in this article:

https://support.blueprism.com/en/support/solutions/articles/7000096893 

We'll continue to update that link with any new information that comes to light, and please feel free to continue to discuss, feedback and share tips here.

[Michael_S]

On a side note - @Carol.Ouellet @RaimondvandeSteeg - really appreciate the feedback and expectations. I'll have a chat with our team internally and see what the process is on our end.

Our best practice advice mirrors @steven.boggs post - we always recommend deploying OS updates in a lower environment before production rollout. 

[Dan.Lister]

Thank you for this.