<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Windows Security Popup (CredentialUIBroker.exe) in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124534#M54359</link>
    <description>&lt;P&gt;To add to RaimondvandeSteeg&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Fri, 23 Jan 2026 15:47:57 GMT</pubDate>
    <dc:creator>Carol.Ouellet</dc:creator>
    <dc:date>2026-01-23T15:47:57Z</dc:date>
    <item>
      <title>Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124490#M54342</link>
      <description>&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="DanLister_0-1768998014592.png" style="width: 400px;"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/41966iB9480D112149A644/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="DanLister_0-1768998014592.png" alt="DanLister_0-1768998014592.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;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:-&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Windows Security prompt is now fully non-automatable&lt;BR /&gt;As of January 13, 2026 Patch Tuesday, Microsoft hardened:&lt;/P&gt;&lt;P&gt;Winlogon&lt;BR /&gt;Credential UI&lt;BR /&gt;Secure Desktop rendering over RDP&lt;BR /&gt;These prompts now:&lt;/P&gt;&lt;P&gt;Run on Secure Desktop&lt;BR /&gt;Are isolated in Session 0&lt;BR /&gt;Block UI Automation, Win32 hooks, accessibility tools&lt;BR /&gt;Explicitly prevent programmatic interaction&lt;BR /&gt;This is intentional and security-driven, following exploitation of Desktop Window Manager (DWM) vulnerabilities patched in January 2026&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Has anyone found the same issue/found a workaround?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2026 12:24:09 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124490#M54342</guid>
      <dc:creator>Dan.Lister</dc:creator>
      <dc:date>2026-01-21T12:24:09Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124492#M54344</link>
      <description>&lt;P&gt;This has to handle and fix by your infrastructure/ RPA COE team by doing image or patch update via policy. We already done this&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2026 13:46:58 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124492#M54344</guid>
      <dc:creator>naveed_raza</dc:creator>
      <dc:date>2026-01-21T13:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124493#M54345</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you explain further what you mean?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2026 15:16:34 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124493#M54345</guid>
      <dc:creator>Dan.Lister</dc:creator>
      <dc:date>2026-01-21T15:16:34Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124518#M54346</link>
      <description>&lt;P&gt;Hi Dan,&lt;/P&gt;&lt;P&gt;We'd always recommend to apply O/S-level updates in a lower environment first to test their impact on existing automations before allowing the updates to be applied in Production environments.&lt;/P&gt;&lt;P&gt;Microsoft has released a few Windows updates recently that contain changes to comply with certain EU regulations, including credential pop-ups like the one you describe. It may be the case that with this Windows Update package, the credentials pop-up you were previously able to spy and interact with has been changed (i.e. from an application layer to the system layer), and may require a new Object to be created to interact with it. For example, if the window was previously able to be spied/interacted with from an Object that was interacting with the target application from which the pop-up originated, Windows may have moved that from the application to the system, and you'd need to account for this change in your Process design.&lt;/P&gt;&lt;P&gt;To restore functionality until this change can be accounted for, you could roll back the MSFT KB update&amp;nbsp;in Production after determining which one affected this change, but keep it applied in your Development/Testing environment to create a new Object to interact with the new/changed pop-up window.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jan 2026 14:59:20 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124518#M54346</guid>
      <dc:creator>steven.boggs</dc:creator>
      <dc:date>2026-01-22T14:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124519#M54347</link>
      <description>&lt;P&gt;Thanks Steven,&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've rolled back for now.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The window we attached to was always in its own object. We connected to CredentialUIBroker.exe and a window title of Windows Security, but it seems we can no longer attach to that process. I can see it is still running as that process and window title, but we now can't attach and get the message "Could not open target process". If we run the Blue Prism app as admin, it will then attach.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jan 2026 15:22:18 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124519#M54347</guid>
      <dc:creator>Dan.Lister</dc:creator>
      <dc:date>2026-01-22T15:22:18Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124520#M54348</link>
      <description>&lt;P&gt;i will check here with my RPA COE team what fix they have done and will share here&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jan 2026 20:29:06 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124520#M54348</guid>
      <dc:creator>naveed_raza</dc:creator>
      <dc:date>2026-01-22T20:29:06Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124521#M54349</link>
      <description>&lt;P&gt;We have noticed the same issue happening in ou non-prod environment this week.&lt;/P&gt;&lt;P&gt;I find it strange that we don't appear to be many groups with this issue.&lt;/P&gt;&lt;P&gt;Since the window cannot be automated, I'd like to hear from Blue Prism.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jan 2026 22:29:45 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124521#M54349</guid>
      <dc:creator>Carol.Ouellet</dc:creator>
      <dc:date>2026-01-22T22:29:45Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124522#M54350</link>
      <description>&lt;P&gt;Yes we've logged with Blue Prism and are still waiting to have a call with them, but so far we have no solution. I expected there to be a lot more people affected, but I can only see it mentioned on UiPath forums. It's the first time i've come across something that I can't seem to find a workaround for other than running as admin.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 09:23:26 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124522#M54350</guid>
      <dc:creator>Dan.Lister</dc:creator>
      <dc:date>2026-01-23T09:23:26Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124524#M54351</link>
      <description>&lt;P&gt;i checked with our RPA COE Team, what they said is , deleting credentials from machines clears it.&lt;/P&gt;&lt;P&gt;they ran this below line of code in command prompt, which will clear all credentials and post that will not get that popup,&amp;nbsp;&lt;/P&gt;&lt;P&gt;rundll32.exe keymgr.dll, KRShowKeyMgr&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;you can check with your IT team regarding this&lt;/STRONG&gt;&lt;/FONT&gt; and try the luck.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 10:37:55 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124524#M54351</guid>
      <dc:creator>naveed_raza</dc:creator>
      <dc:date>2026-01-23T10:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124526#M54353</link>
      <description>&lt;P&gt;Blue Prism have responded and are testing suggested workarounds from Microsoft.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 13:55:30 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124526#M54353</guid>
      <dc:creator>Dan.Lister</dc:creator>
      <dc:date>2026-01-23T13:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124527#M54354</link>
      <description>&lt;P&gt;okay , let us know , what fix they suggested&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 14:13:15 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124527#M54354</guid>
      <dc:creator>naveed_raza</dc:creator>
      <dc:date>2026-01-23T14:13:15Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124528#M54355</link>
      <description>&lt;P&gt;[Retracted Reply]&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 14:43:03 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124528#M54355</guid>
      <dc:creator>Carol.Ouellet</dc:creator>
      <dc:date>2026-01-23T14:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124530#M54357</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;Just dropping in to say:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;We're aware of the issue and our engineering team investigating&lt;/LI&gt;
&lt;LI&gt;As soon as we have practical advice to share, I'll add it in here for all to use&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;STRONG&gt;Please continue to let us know if you have attempted workarounds or fixes that may help the community.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Thank you to&amp;nbsp;&lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/29551"&gt;@Dan.Lister&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/2428"&gt;@Carol.Ouellet&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/2425"&gt;@naveed_raza&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/2091"&gt;@steven.boggs&lt;/a&gt;&amp;nbsp;for raising the issue, highlighting the specific problems with examples and suggesting workarounds.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 14:55:26 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124530#M54357</guid>
      <dc:creator>Michael_S</dc:creator>
      <dc:date>2026-01-23T14:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124532#M54358</link>
      <description>&lt;P&gt;Thanks for the explanation.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 15:21:19 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124532#M54358</guid>
      <dc:creator>RaimondvandeSteeg</dc:creator>
      <dc:date>2026-01-23T15:21:19Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124534#M54359</link>
      <description>&lt;P&gt;To add to RaimondvandeSteeg&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 15:47:57 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124534#M54359</guid>
      <dc:creator>Carol.Ouellet</dc:creator>
      <dc:date>2026-01-23T15:47:57Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124544#M54360</link>
      <description>&lt;P&gt;Hi all,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have some suggested workarounds for you provided in this article:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.blueprism.com/en/support/solutions/articles/7000096893" target="_blank"&gt;https://support.blueprism.com/en/support/solutions/articles/7000096893&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 16:44:35 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124544#M54360</guid>
      <dc:creator>Michael_S</dc:creator>
      <dc:date>2026-01-23T16:44:35Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124545#M54361</link>
      <description>&lt;P&gt;On a side note -&amp;nbsp;&lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/2428"&gt;@Carol.Ouellet&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/2577"&gt;@RaimondvandeSteeg&lt;/a&gt;&amp;nbsp;- really appreciate the feedback and expectations. I'll have a chat with our team internally and see what the process is on our end. &lt;BR /&gt;&lt;BR /&gt;Our best practice advice mirrors&amp;nbsp;&lt;a href="https://community.blueprism.com/t5/user/viewprofilepage/user-id/2091"&gt;@steven.boggs&lt;/a&gt;&amp;nbsp;post - we always recommend deploying OS updates in a lower environment before production rollout.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 16:47:25 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124545#M54361</guid>
      <dc:creator>Michael_S</dc:creator>
      <dc:date>2026-01-23T16:47:25Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Security Popup (CredentialUIBroker.exe)</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124546#M54362</link>
      <description>&lt;P&gt;Thank you for this.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 16:58:34 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Windows-Security-Popup-CredentialUIBroker-exe/m-p/124546#M54362</guid>
      <dc:creator>Dan.Lister</dc:creator>
      <dc:date>2026-01-23T16:58:34Z</dc:date>
    </item>
  </channel>
</rss>

