Hi @Chanderpal singh​ ,

Checkout below KB for resolution,

https://apeople.automationanywhere.com/s/article/Your-Chrome-Plugin-is-either-not-installed-or-disabled/p>

https://apeople.automationanywhere.com/s/article/A360-Recorder-is-not-working-in-Mozilla-firefox/p>

Thanks for replying @ChanduMohammad S​  but link u provided are invalid please help me to solve this issue its really frustrating to get plug in error after trying all stuff

Perform the following steps to resolve the issue:

1. Remove the NativeMessagingHosts setting for the 11.x Chrome plugin registry setting. Computer\HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\automation.chrome.agent (Solution mentioned under Point#5 of the below article) https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/deployment-planning/cloud-chrome-changing-extension.html
2. Restart the Chrome browser and try recording again.

Note: Verify if "automation.bot.browseragent" has been created in the registry under (for versions A2019.15 and above) Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Chrome\NativeMessagingHosts

1. Make sure the user has access to the C:\ProgramFiles\Automation Anywhere path where the  AAChromeManifest.json file is located. 

Default Path:- C:\Program Files\Automation Anywhere\Bot Agent\AABrowserAgent\AAChromeAgentManifest.json

1. If the above steps do not help resolve the issue, please try the following:
   1. Stop the Automation Anywhere Bot agent service.
   2. Navigate to C:\ProgramData\AutomationAnywhere\GlobalCache.
   3. Delete the content of the Global cache folder.
   4. Start the Automation Anywhere Bot agent service.
   5. Try re-running the Bot and see if that helps.

Solution 2:

The bot creator/user will need to add additional delays in the bot to allow the webpage/UI Objects to be first fully loaded before executing the recorder options.

Solution 3:

These steps are only applicable to A360 v.21 and below since v.22 has addressed the package missing from the GlobalCache issue. However,  a one-time cleanup can be required to clear out any previous files needing cleanup. This cleanup can also be required if upgrading from A360.20 or A360.21 directly to A360.23 or A360.21 directly to A360.24. The steps to be followed are as follows: 

If Automation.Bot.BrowserAgent is running and still, the same error is being received then change the recorder package. If the latest recorder package is not present in the GlobalCache folder then perform the below steps

1. Stop the Bot agent service.
2. Delete the GlobalCache folder. The folder would be present in  C:\ProgramData\AutomationAnywhere
3. Start the Bot agent service.
4. Now try to use the latest package. The folder of the latest package should be created in C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources.
5. If it is not created, then uninstall the bot agent and delete the GlobalCache folder.
6. Install and register the device.
7. Now run the bot with the latest recorder package.

Solution 4: 

Applicable for the Bot Agent versions greater than 18.19

1. On the Bot Agent machine, navigate to the location C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources.

2. Locate the Package for the Recorder command and take the backup of the folder. ( The name of the package would start with the version of the Recorder Package being used in the bot).

For instance, if Recorder package used is of version 2.2.0-20210507-195346, then the folder name will be in the form of 2.2.0-20210507-195346-d49ca70a-a160-4b95-b53a-d242654184c0.

Note: The Hexadecimal part in the folder name will be dynamic.

3. Open the Installation path of Bot Agent, C:\Program Files\Automation Anywhere\Bot Agent\AABrowserAgent.

4. Copy the below files:

   i. AAChromeAgentManifest.json

   ii. Automation.Bot.BrowserAgent.exe

5. Paste it under the folder located in Step 2. 

6. Restart the Bot Agent service.

7. Capture the object using the Recorder. 

It should capture the objects now. 

After following the above-mentioned steps if the issue persists then perform the below steps:

1. Delete the ComSpec environment variable.
2. Restart the machine
3. Add the ComSpec environment variable.

Solution 5:

Make sure that the Recorder is selected as the Default version on the Package page.

Solution 6:

Remove the entry 'automation.bot.browseragent' in the registry path: "Computer\HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts".

After removing the registry entry, 'Automation.Bot.BrowserAgent.exe' should be running in the Task Manager-> Details tab.

Note: After making registry changes, restart the machine.

It sounds frustrating that the capture function isn't working despite your efforts in Chrome and Firefox. There are a few possibilities to explore:

1. Misunderstood Plugin: Modern browsers like Chrome and Firefox generally don't rely on individual plugins for screen capture anymore. They have built-in capture features. Can you clarify what kind of capture functionality you're looking for (screenshot, screen recording, etc.)?
2. Extension Confusion: You mentioned "capture plugin" and "extensions." Extensions are more for adding functionalities within the browser, not necessarily capturing the screen.

Here are some solutions depending on your capture needs:

For Screenshots:

• Chrome: Use the built-in screenshot tool by pressing Shift + PrtSc. You can also access it from the three-dot menu (top right) -> More tools -> Capture screenshot.
• Firefox: Press PrtSc for a full-screen screenshot or Alt + PrtSc for the active window.

For Screen Recordings:

• Chrome: Use a browser extension like "Loom" or "Screencastify."
• Firefox: Use a browser extension like "Nimbus Capture" or "FireShot."

For Advanced Capture Needs:

If you require more advanced capture features, consider dedicated screen recording software like OBS Studio (free and open-source) or Snagit (paid).

Additional Tips:

• Check for browser updates. Outdated browsers might have bugs with capture functionality.
• Temporarily disable any extensions you recently installed, just to see if they're interfering.
• Restart your browser completely.

If you can provide more details about the specific capture plugin or error message you're encountering, I might be able to offer more tailored advice.