Not able to detect the window

[Snehamayi_Senapati]

Hi Team,

I am getting this error not able to detect the window

So when i run this as administrator i can able to detect the window but cannot run the process as Robot is showing error so how to fix it

[prashant1603765 (Prashant Kumar)]

Hi @Snehamayi_Senapati

Yes i think this is expected behavior- so pls run into admin mode.
For More:

Error "Cannot Access Target Process Elevated Privileges Might Be Required. Try Running The UiPath Application As An Administrator"

Fix for the error received while inspecting the application element "Cannot access target process elevated privileges might be required. Try running the UiPath application as an administrator." Error Messages: [image] [Image of Elevated Privilege issue.] Root Cause: The target application where an automating needs a higher privilege to interact with it. Resolution: The issue appears due to lack of privileges. Note that it is an expected behavior to not allow the Robot to run as an admi…

Happy Automation

[Anil_G (Anil Gorthi)]

@Snehamayi_Senapati

please check this on what to do on robot side

How to overcome this error message in Studio: "Cannot access application '.'. Elevated privileges might be required. Try running the UiPath application as an administrator."?

How to overcome this error message in Studio: "Cannot access application '.'. Elevated privileges might be required. Try running the UiPath application as an administrator."? Let’s assume that you are trying to automate via UiAutomation an elevated application, but the Studio application it’s displaying a warning "Cannot access application '.'. Elevated privileges might be required. Try running the UiPath application as an administrator.". [image] What may be the cause? The issue is due to …

cheers

[Snehamayi_Senapati]

@Snehamayi_Senapati

I am getting this error not able to detect the window

So when i run this as administrator i can able to detect the window but cannot run the process as Robot is showing error so how to fix it

let me perform..and update you

[Snehamayi_Senapati]

Hi Anil,

I have done the same steps but still same issue.. Actually i have a VM server where bot needs to open Remote desktop and the popup comes to enter the password which we are unable to detect. so we followed the same steps and added reg file in the vm and Run without privilege elevation but still same error.

Step 3: Right-Click mstsc.exe

1. Right click on mstsc.exe
2. You should now see:

Run without privilege elevation

3. Click it
   
   

[Anil_G (Anil Gorthi)]

@Snehamayi_Senapati

oh I just realized this is the windows password manager screen

generally that is not detected…

even the application starts in non elevated this might not be automatable

for now can you try with image or CV activities(generally thats what works on these screens…as it is only password screen that should work)

cheers

[Snehamayi_Senapati]

Hi Anil,
Gm
Still no chance we are getting issue we tried all the possible activities

So do we need to reach out to our admin team to bypass this windows security?

[yedukondaluaregala]

This issue due to to you didn’t enable the api key for this,

Open the Orchestrator, go to Admin> click on Licenses >Click on Robot&Services> there you can comuputer vision api key copy that key and Open your process in studio Click on Project Settings> Click on Computer Vision >scroll down till last there you can see API key text box there paste your copied key.

if this post helpful, please mark it as solution.
Happy automation!

[Luiza_Surdu-Bob (Luiza Bob)]

Hi @Snehamayi_Senapati ,

This issue may be caused by the installation of Windows updates on January 13 (such as KB5074159 for Windows 11). There were several users reporting this on forum.

These updates changed the integrity level for the Windows Security prompt, and it was no longer possible to interact with the UI elements in that window.

Robot/Studio patches have been released for versions 25.10.6 and 24.10.19, you can check the release notes.

Regards,
Luiza

[Snehamayi_Senapati]

The issue still persists. I have added the required environment variable and set Studio and Assistant to run as Administrator by default (via Properties → Compatibility → Run as Administrator).

I am able to run the process successfully from Assistant, and the credential window is detected. However, when I trigger the process from Orchestrator, it is still unable to detect the Windows Security credential window.

I am not sure how to resolve this issue further.