03-08-26 10:48 AM
When open application with edge's inprivate model, system will pop up Windows Security form. I want to click cancel to close it but cannot identify any elements on this screen. Also try to use a separate object to do that but failed to attach. Any advice can do that?
03-08-26 06:21 PM
I think this has to done from GSO policy side , here we have RPA COE team and we have seen this many times .. our COE team has done some image updates behind the scenes to block this. i am not sure what they have done
03-08-26 08:15 PM
Yeah I agree with Naveed try to add the site to the allow list in group policy.
The other optoin would be surface automation, if you can not attach to this window you can attach to explorer window:
Make sure font smoothing is turned off
Scale your display to match the Resource
Make sure your desktop is clear and everything is minimised
Spy the screen in region mode
Set the username password etc.
Definitely try Group policies first!
04-08-26 02:24 AM
If the popup window cannot be avoided, surface automation/region mode would be the right approach. If it still won't work, log a ticket so support team can check your specific usage.
04-08-26 01:49 PM
last option would be surface automation , however that windows security popup might show up again and again , if you open outlook it will come back again , sometimes if you open folder that time also .. if you reboot your machine again it will come back .
we faced alot this issue and later COE team applied group policy update
06-08-26 05:01 AM
Thank you all. I tried with surface automation but did not work. Neither bat nor vbs. I think group policy update should be the way, will check with tech team.
3 weeks ago
I'm just wondering. Are questions about pop ups launched by a browser the most asked questions in Blue Prism history??
Create a new object for common Win32 browser pop ups if it cannot be avoided in browser or windows or network settings.
17 hours ago
Hi Eric,
Thank you for contacting Blue Prism Community.
This is a classic Blue Prism pain point — the Windows Security credential prompt (used for NTLM/Basic proxy or site auth) is often rendered as a XAML-hosted dialog rather than plain Win32 controls, which is why neither Win32 nor AA spying picks up individual elements like the Cancel button, and why a separate "Attacher" object fails to bind to it.
A few approaches that reliably work in practice:
1. Switch spy mode to UI Automation (UIA), not Win32/Active Accessibility
In Application Modeller, when you go to identify the Cancel button, try changing the element type to UIA (sometimes labelled "Win32" vs "UIA" vs "AA" depending on your BP version). This dialog is built on the Credential UI framework, which exposes its buttons through UI Automation even when the Win32 hook sees only the parent host window. This is usually the fix — try it first.
2. If UIA also can't drill in, skip element identification entirely and use keystrokes
A plain Escape keypress or Alt+F4 closes this dialog exactly like clicking Cancel, since it's a modal foreground window.
Use a Navigate stage → Send Hotkey, or a Global Send Keys action, targeted at the window by title ("Windows Security") rather than trying to attach to an element inside it.
This avoids the attach problem completely since you're acting on the window handle, not a child control.
3. Last resort — region/image click
If none of the above work (rare, but possible if the dialog is on a secure/isolated desktop, which sometimes happens depending on GPO settings for credential prompts), define a Region relative to the dialog and use image-based click on the Cancel button. This is fragile across DPI/resolution changes, so treat it as a fallback rather than the primary method.
I'd start with #1, since it fixes the underlying identification problem rather than working around it — but #2 (Escape/Alt+F4 via hotkey targeting the window) is the pragmatic route most people end up using for this specific dialog since it's fast to implement and very reliable.
Regards
Hossein Azimi (APJ Team Member)