Issue initiating Process from Orchestrator: "Elevated Privileges Required" & Remote Debugger Error

[user1231 (user123)]

Hi everyone,

I am facing an issue with a process I developed in UiPath Studio while running the application as an Administrator.

The Problem:

1. Orchestrator: I am unable to start the job from Orchestrator. It fails to initialize the application correctly.
2. Remote Debugging: When attempting to use the Remote Debugger, I receive the error: “Elevated privileges required. Run as administrator.”

It seems the process requires admin rights to interact with specific UI elements , but the Robot Agent isn’t invoking those rights when triggered remotely or via Orchestrator.

Has anyone found a workaround for this that doesn’t involve manually logging into the VM to ‘Run as Admin’ every time? How should I configure the Robot Service or the Project Settings to handle these elevated requirements?

Thanks in advance!

[prashant1603765 (Prashant Kumar)]

Hi @user1231

Pls check the below thread:

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 …

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