Skip to main content
Question

Persistent Error: "An unexpected problem occurred while activating the window" during recording

  • November 3, 2025
  • 5 replies
  • 71 views

Forum|alt.badge.img+1

 

I am using the Automation 360 Community Edition and repeatedly encountering the error message shown in the screenshot when trying to record a desktop application (Automation Anywhere - Order Fulfillment Manager). The error message specifically states: "An unexpected problem occurred while activating the window 'Automation Anywhere Order Fulfillment Manager'. Please refresh the window list and try again."

The Problem Behavior:

  • I can see the window listed correctly after refreshing the browser/window list, but when I click the Capture button, the same error pops up immediately.
  • The critical issue: Reinstalling the Bot Agent or specific packages allows me to successfully capture only one action instance.
  • When I try to Run the entire bot, it fails immediately at the first step that uses a capture action; it doesn't enter any details or interact with the application window at all

Steps Already Taken (Troubleshooting Done):

  1. Restarted the local Bot Agent service
  2. Performed standard uninstall/reinstall of the Bot Agent.
  3. Checked antivirus/firewall (temporarily disabled, issue remained).
  4. Confirmed browser extension is installed and enabled.

I need a permanent solution as these steps have not resolved the recurring nature of the error, which prevents the bot from running consistently.

5 replies

Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • November 3, 2025

Hi ​@tmohamedyaser,

 

I hope you’re trying the Capture action on a new browser window rather than the same browser where you are accessing the CR.

As you have performed most of the known fixes for this issue, I don’t have much to say on this. However, try checking the below two points as well.

 

  1. Check the Recorder package version. - Try after upgrading or downgrading the same.
  2. Clear the Bot Agent Cache from the location below and restart the Bot Agent service. This often resolves stale Recorder state issues.

          C:\ProgramData\AutomationAnywhere\BotAgent\Cache


Forum|alt.badge.img+1
  • Author
  • Cadet | Tier 2
  • November 3, 2025

Hi ​@Padmakumar ,
I tried looking for the BotAgent folder, but I only have BotRunner in C:\ProgramData\AutomationAnywhere\BotRunner, and there’s no Cache folder inside it. I also restarted the Automation Anywhere Bot Agent service from services.msc, but the issue still persists. Do you have any other suggestions I can try?

Thanks!


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • November 4, 2025

Hi ​@Padmakumar ,
I tried looking for the BotAgent folder, but I only have BotRunner in C:\ProgramData\AutomationAnywhere\BotRunner, and there’s no Cache folder inside it. I also restarted the Automation Anywhere Bot Agent service from services.msc, but the issue still persists. Do you have any other suggestions I can try?

Thanks!

Have you tried changing the package version?


Forum|alt.badge.img+1
  • Author
  • Cadet | Tier 2
  • November 10, 2025

Hi ​@Padmakumar ,
I tried looking for the BotAgent folder, but I only have BotRunner in C:\ProgramData\AutomationAnywhere\BotRunner, and there’s no Cache folder inside it. I also restarted the Automation Anywhere Bot Agent service from services.msc, but the issue still persists. Do you have any other suggestions I can try?

Thanks!

Have you tried changing the package version?

Yeah i did still the issue is persistant


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • November 11, 2025

Hi ​@Padmakumar ,
I tried looking for the BotAgent folder, but I only have BotRunner in C:\ProgramData\AutomationAnywhere\BotRunner, and there’s no Cache folder inside it. I also restarted the Automation Anywhere Bot Agent service from services.msc, but the issue still persists. Do you have any other suggestions I can try?

Thanks!

Have you tried changing the package version?

Yeah i did still the issue is persistant

Well, I would recommend raising a support ticket on this then as the above-mentioned are the only checkups possible to do on this issue.