After the installation of UiPath Remote Runtime in the target server and Microsoft Remote App Extension in the UiPath Studio. There is no more error message when identifying the element on it (Previous, there is error of missing both extension or version diff between Remote Runtime and UI Automation.).
Nevertheless, I can now only to identify the whole window instead of the button in it. Does anyone know how to solve this issue ?
hi, @Hugo_Pang this usually happens when the Remote Runtime version on the server doesn’t match the UIAutomation package version in Studio. Even a small mismatch can mess it up and UiPath will only see the whole window.
Here’s what you can do:
Make sure both versions are exactly the same (Remote Runtime = UIAutomation).
After installing, restart the server and UiPath Studio once.
Double-check that the Remote App extension is enabled properly.
If it still acts up, try using a stable UIAutomation version like 23.x — that usually fixes it.
Once the versions line up, you’ll be able to select buttons and fields individually again.
hi @arjun.shiroya Thank you for your answer. I have checked that when the version of UiPath.UIAUtomation.Activities package is incompatible with the UiPath Remote Runtime, there will be an error message pop-up. Please find the below screen capture for your reference. And currently there is no error message when trying to identify element with Ui Explorer.
Hello @Hugo_Pang,
Ensure Remote Runtime runs in each user session, all versions match, try AA/UIA in UiExplorer, enable UIA redirection in Group Policy, and restart both the remote app and Studio.
Confirmed that Remote Runtime run in each user session. The Remote Runtime version is 19.10.7312.25504 and UI Automation version is 19.11.1
One more information is that it works fine with Citrix but it is not work after we changing to access method to Microsoft RemoteApp
@Hugo_Pang our Remote Runtime version and UI Automation versions are close but not exactly the same (19.10 vs 19.11). That small difference can cause issues, especially with Microsoft RemoteApp which is more sensitive than Citrix.
Citrix is more flexible with element detection, but RemoteApp often needs perfect version match.
try to Fix: Upgrade Remote Runtime to 19.11.1 to match UI Automation version exactly.
After upgrade, restart the server and Studio.
Update one of them so both versions match exactly — either:
Once both are the same version, restart the remote app and Studio — you should then be able to identify individual elements (like buttons) again
@sagar.singh1 After downgrading the UIAutomation package to 19.10.1 and restart the studio, the issue still persist. May I know if there is any steps I missed ?
Even if versions match, element-level detection fails if:
@sagar.singh1 I have checked that the Remote Runtime is already running in my user session. For point 2 and 3, may I know how could I check it ?
Point 2:-
Open gpedit.msc → Navigate to:
Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection
gpupdate /force to apply.Point 3:-
Check in Device and Resource Redirection, there is no Setting “Allow UI Automation redirection”. May I also know if it is possible blocked by some default setting of Microsoft RemoteApp ?