How To Disable The Interactive Logon Screen For The Unattended Robot?

News Knowledge Base
1

How to disable the pop up that might appear when the Unattended Robot tries to create the RDP session and prevent the error "Could not start executor. The wait operation timed out. (0x80070102)" ?

Issue Description

This article addresses issues around a legal banner potentially causing a Robot to fail at login time.

Example of the pop-up message:


Background

When the Unattended Robot tries to create a session via RDP to start an Unattended job, the Robot should login automatically without the need of human intervention. If there is a legal banner, it is expected that the Robot is able to bypass it. This has always been the functionality but in version prior to 21.10.6 and 22.4.3 there was a condition in which the bypass would not work.

Additionally, there was a race condition found and fixed in 23.10.4 that would sometimes occur.

The error occur: "Could not start executor. The wait operation timed out. (0x80070102)" is not specific to this problem. It simply means something the login process did not complete. The login is done through windows and we are not always technically possible to give more specific details of the underlying problem.

Diagnosing

If there's a suspicion that a legal banner is causing an issue, the legal banner settings can be disabled.

  1. Before going through the following steps, its recommended that if the error: "Could not start executor. The wait operation timed out. (0x80070102)" is encountered, try immediately logging in to the machine that threw the error. Any unhandled pop up during login could cause this issue, and more often its a general login issue unrelated to UiPath. See: Specified Login Does not exist for other possible causes.
  2. Determine how the banner is being set:
    1. Check the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
    2. Check to see if there is a string value called LegalNoticeCaption and LegalNoticeText
    3. If this exists, the banner is coming from a group policy. Contact your admin to see if it can be temporarily disabled for testing.
    4. Alternatively, this can be set in a local group policy (The registry key should always exist whether the policy is locally set or set by domain policies). The local polices for this is
      1. Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Interactive logon: Message text for users attempting to log on
      2. Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Interactive logon: Message title for users attempting to log on
      3. If set locally, just disable the settings.
  1. If the registry is not set, check the legacy setting.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
    • Look for the String Value LegalNoticeText and LegalNoticeCaption.
    • Remove the data from these settings.
  2. After disabling the setting, see if the issue still reproduces. If it does, the issue is not related to the legal banner (which is what we would expect). If the issue stops occuring, then please raise a ticket with UiPath. Most likely we will have to check the environment and use a tool like procmon to find the issue. (The login sequence involves windows subsystems for which we usually need to use debug tools to find issues with).