Hi Team,
I am working on an automation that requires taking an RDP session. During the process, a Windows Security password prompt appears, and the automation is unable to enter the password or proceed further.
I have already tried the following approaches:
Type Into
Type Secure Text / Type Secure Key
Send Hotkey
cmdkey command for credential management
However, none of these methods are working, and the automation is still unable to interact with the password prompt or establish the remote connection.
Could you please let me know if there is any alternative solution or recommended approach to handle the Windows Security password prompt during RDP automation?
@pragati.baghel This usually happens because the Windows Security popup is running at a higher privilege level, so normal UiPath activities such as Type Into or Send Hotkey cannot interact with it.
Try setting the below system environment variable on the robot machine:
UiPath_MEDIUMPLUS_EXECUTOR = 1
After adding it, restart the UiPath Robot Service or restart the machine and test again.
Also, if this is an unattended process, it would be better to configure the Windows credentials in Orchestrator and let UiPath create the RDP session instead of handling the Windows Security popup manually.
Please try the Medium+ Executor setting first and check if the password field becomes accessible.
For Unattended mode, fix the issue by setting the environment variable “UiPath_MEDIUMPLUS_EXECUTOR=true” and restart the Robot service.
For Studio/Attended mode, stop all UiPath processes like “UiPath.Service.UserHost.exe” & “UiPath.Executor.exe” from Task Manager. Start Studio as Administrator and automate the prompt then, stop processes again and then finally restart Studio without admin rights before continuing.
Enable Auto-login / Save Credentials for the RDP session so the password prompt does not appear.
Use UiPath Remote Runtime and automate the application inside the remote session instead of automating the login prompt.
If possible, launch RDP using an .rdp file with stored credentials or configure credentials through Windows Credential Manager beforehand.
Check whether the prompt is a UAC/Windows Security secure screen. Secure desktop windows cannot be automated by normal UI automation activities.
For unattended automations, the best practice is to avoid interactive password prompts entirely by pre-configuring authentication or using service accounts.
@pragati.baghel
I would avoid trying to automate the Windows Security popup itself if possible. Windows can protect these credential dialogs, so Type Into or Send Hotkey may not work reliably.
If the goal is to automate something inside the remote VM, the cleaner option would be to run the UiPath Robot directly on that VM and start the process through Orchestrator instead of opening an RDP session from another robot.
If RDP is mandatory, I’d also check with your IT team whether saved credentials are allowed and whether a group policy is forcing the password prompt. If that policy is enabled, UiPath activities won’t really be able to bypass it.
