Bot does not start on locked machine

Hello, we are using Automation 360 Build 37528 and trying to start an unattended bot on a fixed schedule. However if the machine is locked, the bot always fails to start, returning the error message:

java.lang.RuntimeException: User - xxx has attested the device credentials, but Console session is locked

The user has the correct credentials to unlock the machine and we also tried to uncheck Attest Device Credentials checkbox in user settings, as described in

https://apeople.automationanywhere.com/s/article/A360-Java-lang-RuntimeException-User-vdi-has-attested-the-device-credentials-but-not-chosen-to-reuse-an-existing-session

but nothing seems to work. Is there anything else we can try?

Thank you

Page 1 / 1

Hi @Broman,

Since unchecking the Attest Device Credentials checkbox in user settings is the suggested fix to this issue and it didn't actually work in your case, could you please try to restart the Bot Agent service on that particular runner device also once?

Hi @Padmakumar, thank you for your answer.

Restarting and reinstalling the Bot Agent unfortunately did not help.

Hi @Padmakumar, thank you for your answer.

Restarting and reinstalling the Bot Agent unfortunately did not help.

Here are some additional points to check:

1. Disable Legal/Login Banners

Any message or banner that appears before the login screen will block the bot.

Policy Location: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
Policies to Configure:
- Interactive logon: Message text for users attempting to log on: This must be blank.
- Interactive logon: Message title for users attempting to log on: This must be blank.

2. Disable "Require Ctrl+Alt+Del"

The Bot Agent cannot simulate this key combination.

Policy Location: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
Policy to Configure:
- Interactive logon: Do not require CTRL+ALT+DEL: This must be set to Enabled.

3. Allow Remote Desktop Login

The bot user needs permission to log in via a remote session, which is how the Bot Agent creates its session.

Policy Location: Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment
Policy to Configure:
- Allow log on through Remote Desktop Services: Ensure the bot runner's user account (or a group it belongs to, like 'Remote Desktop Users') is added to this policy.

As a standard operational procedure, you should always sign out of the bot runner machine rather than just locking the session (e.g., with Windows Key + L).

Why? Locking the machine leaves your user session active but inaccessible. Signing out completely terminates the session. This provides a clean slate for the Bot Agent, allowing it to create a fresh, isolated session for the bot run without any conflicts, which is the ideal state for an unattended execution.

Finally, quickly verify that the Bot Agent service is configured correctly.

Open Services (services.msc).
Find the Automation Anywhere Bot Agent service and open its Properties.
Go to the Log On tab.
Ensure it is set to log on as Local System account. If not, change it to this and restart the service.

Hi @Padmakumar, thank you for your answer.

Restarting and reinstalling the Bot Agent unfortunately did not help.

Here are some additional points to check.

1. Disable Legal/Login Banners

Any message or banner that appears before the login screen will block the bot.

Policy Location: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
Policies to Configure:
- Interactive logon: Message text for users attempting to log on: This must be blank.
- Interactive logon: Message title for users attempting to log on: This must be blank.

2. Disable "Require Ctrl+Alt+Del"

The Bot Agent cannot simulate this key combination.

Policy Location: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
Policy to Configure:
- Interactive logon: Do not require CTRL+ALT+DEL: This must be set to Enabled.

3. Allow Remote Desktop Login

The bot user needs permission to log in via a remote session, which is how the Bot Agent creates its session.

Policy Location: Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment
Policy to Configure:
- Allow log on through Remote Desktop Services: Ensure the bot runner's user account (or a group it belongs to, like 'Remote Desktop Users') is added to this policy.

As a standard operational procedure, you should always sign out of the bot runner machine rather than just locking the session (e.g., with Windows Key + L). Locking the machine leaves your user session active but inaccessible. Signing out completely terminates the session. This provides a clean slate for the Bot Agent, allowing it to create a fresh, isolated session for the bot run without any conflicts, which is the ideal state for an unattended execution.

Finally, quickly verify that the Bot Agent service is configured correctly.

Open Services (services.msc).
Find the Automation Anywhere Bot Agent service and open its Properties.
Go to the Log On tab.
Ensure it is set to log on as Local System account. If not, change it to this and restart the service.

Hello @Padmakumar

Thank you for your answer. We have tried all of your points, but unfortunately the bot still cannot unlock a locked machine and start automatically on a schedule.

There are no logs for these failed runs in the Bot_Launcher file, and only the following exception in the Node_Manager logs:

2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler - {deploymentId=9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5, traceId=11c5877578a64af5} - process(DeploymentHandler.java:348) - Create deploy bot session...
2025-Okt.-13 Mo. 15:05:03.207 ERROR [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl - {deploymentId=9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5, traceId=11c5877578a64af5} - useExistingSession(WindowsAutoLoginServiceImpl.java:231) - User - sazkerobby has attested the device credentials, but Console session is locked
2025-Okt.-13 Mo. 15:05:03.207 ERROR [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl - {deploymentId=9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5, traceId=11c5877578a64af5} - login(WindowsAutoLoginServiceImpl.java:140) - WindowsAutoLoginServiceImpl - Login - Exception java.lang.RuntimeException: User - sazkerobby has attested the device credentials, but Console session is locked
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.useExistingSession(WindowsAutoLoginServiceImpl.java:232) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.login(WindowsAutoLoginServiceImpl.java:108) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.UserBotSessionServiceImpl.createBotSession(UserBotSessionServiceImpl.java:147) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.createUserBotSession(DeploymentHandler.java:1049) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.getBotSession(DeploymentHandler.java:1029) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.process(DeploymentHandler.java:349) ~[node-manager.jar:?]
	at com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl$ListenerExecutor.lambda$process$0(InMemoryAsyncImpl.java:58) ~[node-manager.jar:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?]
	at java.util.concurrent.FutureTask.run(Unknown Source) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
	at java.lang.Thread.run(Unknown Source) [?:?]

2025-Okt.-13 Mo. 15:05:03.207 ERROR [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler - {} - process(DeploymentHandler.java:644) - Unable to process bot command successfully for executionId: (9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5) java.lang.RuntimeException: java.lang.RuntimeException: User - sazkerobby has attested the device credentials, but Console session is locked
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.login(WindowsAutoLoginServiceImpl.java:146) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.UserBotSessionServiceImpl.createBotSession(UserBotSessionServiceImpl.java:147) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.createUserBotSession(DeploymentHandler.java:1049) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.getBotSession(DeploymentHandler.java:1029) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.process(DeploymentHandler.java:349) ~[node-manager.jar:?]
	at com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl$ListenerExecutor.lambda$process$0(InMemoryAsyncImpl.java:58) ~[node-manager.jar:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?]
	at java.util.concurrent.FutureTask.run(Unknown Source) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
	at java.lang.Thread.run(Unknown Source) [?:?]
Caused by: java.lang.RuntimeException: User - sazkerobby has attested the device credentials, but Console session is locked
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.useExistingSession(WindowsAutoLoginServiceImpl.java:232) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.login(WindowsAutoLoginServiceImpl.java:108) ~[node-manager.jar:?]
	... 10 more

2025-Okt.-13 Mo. 15:05:03.207 WARN  [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.BotProgressEventProcessorImpl - {} - setEvent(BotProgressEventProcessorImpl.java:68) - Empty user name. Skipping event addition
2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-17-thread-1] - com.automationanywhere.nodemanager.service.impl.NodeMessagingServiceImpl - {} - writeSuccess(NodeMessagingServiceImpl.java:430) - Message sent to CR successfully.
2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.message.handlers.ResiliencyHandler - {} - sendErrorMessage(ResiliencyHandler.java:415) - Sent failure message: eventData {  id: "9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5"  bot_execution {    start_date_time {      seconds: 1760360703      nanos: 207208500    }    end_date_time {      seconds: 1760360703      nanos: 207208500    }    message: "java.lang.RuntimeException: User - sazkerobby has attested the device credentials, but Console session is locked"    status_type: DEPLOY_FAILED  }} to CR for deployment: (9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5)
2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-7-thread-1] - com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl - {} - lambda$process$0(InMemoryAsyncImpl.java:59) - Message successfully processed for topic DEPLOYMENT
2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-17-thread-1] - com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl - {} - lambda$process$0(InMemoryAsyncImpl.java:59) - Message successfully processed for topic NodeResponse
2025-Okt.-13 Mo. 15:05:03.272 INFO  [pool-12-thread-1] - com.automationanywhere.nodemanager.service.impl.message.handlers.ReconcileCompletedCommandHandler - {} - process(ReconcileCompletedCommandHandler.java:39) - Device: 217 received reconciled completed message: topic: DELETE_RECONCILED_EVENTSreconcile_completed_command {  device_id: 217  terminated_execution_ids: "9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5"}
2025-Okt.-13 Mo. 15:05:03.272 INFO  [pool-12-thread-1] - com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl - {} - lambda$process$0(InMemoryAsyncImpl.java:59) - Message successfully processed for topic DELETE_RECONCILED_EVENTS

Is there anything else we can try to resolve this problem?

Thank you

Hello @Padmakumar

Thank you for your answer. We have tried all of your points, but unfortunately the bot still cannot unlock a locked machine and start automatically on a schedule.

There are no logs for these failed runs in the Bot_Launcher file, and only the following exception in the Node_Manager logs:

2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler - {deploymentId=9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5, traceId=11c5877578a64af5} - process(DeploymentHandler.java:348) - Create deploy bot session...
2025-Okt.-13 Mo. 15:05:03.207 ERROR [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl - {deploymentId=9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5, traceId=11c5877578a64af5} - useExistingSession(WindowsAutoLoginServiceImpl.java:231) - User - sazkerobby has attested the device credentials, but Console session is locked
2025-Okt.-13 Mo. 15:05:03.207 ERROR [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl - {deploymentId=9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5, traceId=11c5877578a64af5} - login(WindowsAutoLoginServiceImpl.java:140) - WindowsAutoLoginServiceImpl - Login - Exception java.lang.RuntimeException: User - sazkerobby has attested the device credentials, but Console session is locked
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.useExistingSession(WindowsAutoLoginServiceImpl.java:232) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.login(WindowsAutoLoginServiceImpl.java:108) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.UserBotSessionServiceImpl.createBotSession(UserBotSessionServiceImpl.java:147) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.createUserBotSession(DeploymentHandler.java:1049) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.getBotSession(DeploymentHandler.java:1029) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.process(DeploymentHandler.java:349) ~[node-manager.jar:?]
	at com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl$ListenerExecutor.lambda$process$0(InMemoryAsyncImpl.java:58) ~[node-manager.jar:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?]
	at java.util.concurrent.FutureTask.run(Unknown Source) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
	at java.lang.Thread.run(Unknown Source) [?:?]

2025-Okt.-13 Mo. 15:05:03.207 ERROR [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler - {} - process(DeploymentHandler.java:644) - Unable to process bot command successfully for executionId: (9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5) java.lang.RuntimeException: java.lang.RuntimeException: User - sazkerobby has attested the device credentials, but Console session is locked
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.login(WindowsAutoLoginServiceImpl.java:146) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.UserBotSessionServiceImpl.createBotSession(UserBotSessionServiceImpl.java:147) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.createUserBotSession(DeploymentHandler.java:1049) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.getBotSession(DeploymentHandler.java:1029) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.message.handlers.DeploymentHandler.process(DeploymentHandler.java:349) ~[node-manager.jar:?]
	at com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl$ListenerExecutor.lambda$process$0(InMemoryAsyncImpl.java:58) ~[node-manager.jar:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?]
	at java.util.concurrent.FutureTask.run(Unknown Source) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
	at java.lang.Thread.run(Unknown Source) [?:?]
Caused by: java.lang.RuntimeException: User - sazkerobby has attested the device credentials, but Console session is locked
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.useExistingSession(WindowsAutoLoginServiceImpl.java:232) ~[node-manager.jar:?]
	at com.automationanywhere.nodemanager.service.impl.WindowsAutoLoginServiceImpl.login(WindowsAutoLoginServiceImpl.java:108) ~[node-manager.jar:?]
	... 10 more

2025-Okt.-13 Mo. 15:05:03.207 WARN  [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.BotProgressEventProcessorImpl - {} - setEvent(BotProgressEventProcessorImpl.java:68) - Empty user name. Skipping event addition
2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-17-thread-1] - com.automationanywhere.nodemanager.service.impl.NodeMessagingServiceImpl - {} - writeSuccess(NodeMessagingServiceImpl.java:430) - Message sent to CR successfully.
2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-7-thread-1] - com.automationanywhere.nodemanager.service.impl.message.handlers.ResiliencyHandler - {} - sendErrorMessage(ResiliencyHandler.java:415) - Sent failure message: eventData {  id: "9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5"  bot_execution {    start_date_time {      seconds: 1760360703      nanos: 207208500    }    end_date_time {      seconds: 1760360703      nanos: 207208500    }    message: "java.lang.RuntimeException: User - sazkerobby has attested the device credentials, but Console session is locked"    status_type: DEPLOY_FAILED  }} to CR for deployment: (9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5)
2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-7-thread-1] - com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl - {} - lambda$process$0(InMemoryAsyncImpl.java:59) - Message successfully processed for topic DEPLOYMENT
2025-Okt.-13 Mo. 15:05:03.207 INFO  [pool-17-thread-1] - com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl - {} - lambda$process$0(InMemoryAsyncImpl.java:59) - Message successfully processed for topic NodeResponse
2025-Okt.-13 Mo. 15:05:03.272 INFO  [pool-12-thread-1] - com.automationanywhere.nodemanager.service.impl.message.handlers.ReconcileCompletedCommandHandler - {} - process(ReconcileCompletedCommandHandler.java:39) - Device: 217 received reconciled completed message: topic: DELETE_RECONCILED_EVENTSreconcile_completed_command {  device_id: 217  terminated_execution_ids: "9fd7135b-7352-405a-a482-c9758aa145aa_11c5877578a64af5"}
2025-Okt.-13 Mo. 15:05:03.272 INFO  [pool-12-thread-1] - com.automationanywhere.asynchronous.messaging.InMemoryAsyncImpl - {} - lambda$process$0(InMemoryAsyncImpl.java:59) - Message successfully processed for topic DELETE_RECONCILED_EVENTS

Is there anything else we can try to resolve this problem?

Thank you

I would recommend raising a support ticket on this.

1. Disable Legal/Login Banners

2. Disable "Require Ctrl+Alt+Del"

3. Allow Remote Desktop Login

1. Disable Legal/Login Banners

2. Disable "Require Ctrl+Alt+Del"

3. Allow Remote Desktop Login

Sign up

Login to the Pathfinder Community

Scanning file for viruses.

This file cannot be downloaded