UiPathRemoteRuntime.exe stops working after working Almost 2 months

Hi everyone,

I’m facing a critical and recurring issue with UiPath Remote Runtime that starts every 1 or 2 months after re-installing RemoteRuntime to RDP Server, and I’m looking for a root-cause solution, not a workaround.

Environment

  • UiPath Remote Runtime Version: 24.10.99.27114
    UiPath Version: Studio 2024.10.14 LTS

When trying to indicate or validate selectors on an application running inside an RDP session, UiPath throws the following error:

“Cannot automate remote app: UiPathRemoteRuntime.exe is not running in the remote session.”

At this point:

  • The RDP session is active
  • The target application is open
  • UiPath Studio / Robot is connected
  • But UiPathRemoteRuntime.exe is not detected as running

Event Viewer Findings

When I checked Event Viewer, I found the following warning around the same timeframe:

Windows Installer reconfigured the product.
Product Name: UiPath Remote Runtime
Product Version: 24.10.99.27114
Product Language: 1033
Manufacturer: UiPath
Reconfiguration success or error status: 0

There was no manual update, repair, or reinstall triggered by us.

This looks like a silent Windows Installer reconfiguration, but it results in Remote Runtime effectively not working afterward.


In Task Scheduler, the Remote Runtime-related task looks completely normal:

  • Status: Ready
  • Triggers: Enabled
  • No recent changes
  • No failed runs

(Couldn’t add more image new-member srry)

And also we tried to close all antivirus protection to this RDP server as well.

The only way we can temporarily fix the issue is:

  1. Log in to the server via RDP
  2. Uninstall UiPath Remote Runtime
  3. Reinstall UiPath Remote Runtime
  4. Automation works again… for some time

This is not scalable or acceptable:

  • Manual RDP intervention breaks the whole RPA thing
  • This issue keeps recurring after weeks

Any guidance, similar experiences, or official recommendations would be highly appreciated.

Hi @sythep

The issue happens because Windows Installer silently repairs or reconfigures UiPath Remote Runtime, stopping it from running in the RDP session. This causes UiPath to lose automation control until you reinstall Remote Runtime. To fix, check for Windows updates or policies causing this, whitelist Remote Runtime in antivirus, and consider automating reinstall or contacting UiPath Support for a permanent solution.

Hi @sythep

Uninstall UiPath Remote Runtime completely from the RDP server and then reinstall it using the official UiPath Remote Runtime MSI in a machine-wide installation by logging in as a local administrator and installing it once for all users with administrative rights, then after the installation log in using a new RDP user account and confirm that UiPathRemoteRuntime.exe starts automatically in Task Manager, and next disable MSI self-repair triggers on the server by checking Group Policy for Windows Installer repair or resiliency settings as well as any application auto-repair or cleanup policies and ensure that no scheduled maintenance or optimization tools are automatically repairing MSI applications, and finally make sure not to mix installation methods by avoiding per-user reinstalls and not using the Control Panel repair option.

Cheers