Skip to main content
Question

Community Edition – Bot Agent Connected but Bot Execution Fails with “User not logged into the machine”

  • Nov 3, 2026 12:54 AM UTC
  • 3 replies
  • 9 views

Hello,

I'm using Automation Anywhere Community Edition with Bot Agent version 23.20.31 on Windows 11.

The Bot Agent installation was successful, and my local device appears as Connected in the Control Room under Manage → Devices.

The browser extension is also installed and enabled.

However, when I try to run a simple Task Bot, the execution fails immediately with the following error:

“User not logged into the machine. This may be due to multiple reasons.”

The error suggests checking the device login credentials and ensuring that the user is logged into the machine.

I have verified that:

  • The Bot Agent service is running.

  • The device is registered and shows as Connected.

  • The device is configured as Single user.

  • The Windows user session is active.

  • The username configured under My Settings → Devices → Credentials matches the Windows username.

One issue I noticed:

When I open My Settings → Devices → Credentials and select Edit, only the Username field is displayed. There is no Password field available.

My questions:

  1. Is a Windows password required for local bot execution in Community Edition?

  2. Why is the Password field missing from the Credentials section?

  3. Is there an additional configuration required to allow the Bot Agent to start a Windows session and execute Task Bots?

Any guidance would be greatly appreciated.

Thank you!

3 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+6
  • Automation Anywhere Team
  • Nov 3, 2026 12:58 AM UTC

​@sergio.ortiz 

1. No.

2. See #1.

3. No.

What your issue very likely is that you're using your login credentials instead of your Windows domain\username.

Search "whoami" in this forum for further information. 


  • Author
  • Cadet | Tier 2
  • Nov 3, 2026 2:09 AM UTC

Thank you. I verified the Windows account using both whoami and whoami /user.

The results confirm:

  • Windows domain/computer name: SERG

  • Windows username: giga_it

  • whoami output: serg\giga_it

This exact username is already configured in Automation Anywhere under My Settings → Devices → Credentials.

My Windows session is active, and the device status is Connected. However, I still receive the ba.user.loggedin.error message when running the bot.

Since the username format is correct, could you please advise what else might prevent the Bot Agent from recognizing the active Windows session?


Shreya.Kumar
Pathfinder Community Team
Forum|alt.badge.img+4

​@Sergio 1245 , there may be some third party software (e.g., anti-virus, firewall, MDM) that is interfering with the communication between the browser extension and the Bot Agent. Can you try checking if that’s the case?