Skip to main content
Solved

Automation Anywhere 360 Browser Extension Access Issue in Windows 11 Machine.


Vatsy
Pathfinder Advocate | Tier 6
Forum|alt.badge.img+14
  • Pathfinder Advocate | Tier 6
  • 100 replies

Hi ​@Aaron.Gleason ​@Shreya.Kumar ​@Oli.Morris ​@madhu subbegowda ​@Marc Mueller,

We are facing an issue with the AA360 Browser Extensions (Both MS Edge and Google Chrome) in our new Windows 11 servers where it is enabled but we are NOT able to enable/disable it, or edit its settings, unlike in our old Windows 10 servers.

Our infrastructure team already checked at the group policies of the servers but didn't find any issue at their end, so I am reaching out to you guys if there is something that we are missing or is there anything specific to be done for the Windows 11 servers?

Looking forward to your response!

Best answer by Vatsy

Hello Everyone!

Thanks a lot for all your replies! I really appreciate it!

We were able to fix this issue by following below steps:

  1. We first referred to the below AA360 documentation where it talks about a setting to be done within the AA360 Control Room using the Admin account to Disable the Automatic Installation of the Extensions (both MS Edge and Google Chrome) during the installation of the Bot Agent. - Documentation Link
  2. We had observed that whenever we installed the Bot Agent first with automatic install of the Extensions, it automatically locked the Extensions after installation. We then tried to install the extensions first (with no Bot Agent present in the system) and that worked, but as soon as we installed the Bot Agent it again locked the extensions.
  3. We then followed the below steps:
    a. Logged into the Control Room using our Admin account.
    b. Navigated to Administration > Settings > Devices.
    c. In the Browser extensions settings, select Edit and then selected the Disabled option to disable the automatic update of browser extensions. This option is applicable only when a Bot Agent is updated or a new Bot Agent is installed.
  4. After completing the above step, we then installed the Bot Agent with no additional steps and Voila!, this time the Bot Agent didn’t lock the Browser Extensions.
  5. We manually enabled the extensions in both MS Edge and Google Chrome and applied the appropriate settings after which our Bots ran successfully.

I wanted to share this information here so that we all are aware that whenever you will migrate to the Windows 11 servers from the Windows 10 servers, please ensure that you DO NOT MISS this checkpoint to ensure a smooth transition. I hope this post helps you all in the future! 😀

Once again a big thank you to all my fellow Pathfinders for all your help and support!

Cheers!

View original
Did this topic help answer your question?

8 replies

Marc Mueller
Pathfinder Advocate | Tier 6
Forum|alt.badge.img+14
  • Pathfinder Advocate | Tier 6
  • 167 replies
  • March 18, 2025

Hi ​@Vatsy,

we are still on Windows 10 on VM’s.

No idea for now Sorry.🤔🤷

 

Cheers

Marc


Vatsy
Pathfinder Advocate | Tier 6
Forum|alt.badge.img+14
  • Author
  • Pathfinder Advocate | Tier 6
  • 100 replies
  • March 18, 2025
Marc Mueller wrote:

Hi ​@Vatsy,

we are still on Windows 10 on VM’s.

No idea for now Sorry.🤔🤷

 

Cheers

Marc

No problem ​@Marc Mueller!

Thanks for your response.


madhu subbegowda
Most Valuable Pathfinder
Forum|alt.badge.img+8

Hi ​@Vatsy ,

Can you try this?

1. Extension Management Restrictions in Windows 11

Windows 11 has stricter security policies for managing browser extensions. Check if the extensions are forced via a policy by running the following command in Command Prompt (cmd):

For Microsoft Edge:

  • reg query HKLM\Software\Policies\Microsoft\Edge\ExtensionInstallForcelist

For Google Chrome:

  • reg query HKLM\Software\Policies\Google\Chrome\ExtensionInstallForcelist

Note: the above are powershell queries.

If entries exist, it means extensions are controlled via Group Policy. You may need to remove the registry policies or update them via Group Policy (gpedit.msc)

2. Registry & Group Policy Validation

Your Infrastructure Team checked the Group Policies, but let’s verify Registry Settings to ensure the extension is properly installed.

Check Edge Extension Settings in Registry:

Get-ItemProperty -Path "HKLM:\Software\Policies\Microsoft\Edge"   -- run this PowerShell and look for entries like - ExtensionInstallForcelist, ExtensionAllowedTypes

Check Chrome Extension Settings in Registry: 

Get-ItemProperty -Path "HKLM:\Software\Policies\Google\Chrome" and ensure the extension is listed and allowed.

3. Ensure Proper Extension Installation

For Edge:

  1. Go to edge://extensions
  2. Find AA360 Extension
  3. If you see "Managed by your organization", it means the extension is controlled by policies.

For Chrome:

  1. Go to chrome://extensions
  2. If Managed by your organization appears, check the registry or policy settings.

4. Fix Policy Conflicts for Extension Permissions

If you cannot edit the extension settings, the issue may be due to Windows 11’s stricter security policies. Try:

  1. Check the Local Group Policy (gpedit.msc):

    • Navigate to: Computer Configuration → Administrative Templates → Microsoft Edge → Extensions
    • Ensure:
      • "Control which extensions are installed silently" is Enabled
      • "Allow users to modify extensions" is Enabled
  2. For Chrome (gpedit.msc):

    • Go to: Computer Configuration → Administrative Templates → Google → Google Chrome → Extensions
    • Check if extension settings are locked by policies.

5. Check Browser Profiles & User Permissions

If the extensions are installed, but settings are locked, check: or If AA360 is installed for "All Users" instead of "Current User" or If you have Admin rights on the server or If the server enforces strict security settings for extensions

6. Reinstall AA360 Browser Extensions

If all else fails:

  1. Uninstall AA360 extensions manually from edge://extensions and chrome://extensions
  2. Reinstall AA360 browser extensions via the Automation Anywhere Control Room
  3. Restart the browser and check if the issue persists.

Main reasons might be:

  1. If policies are controlling the extension, IT may need to modify Group Policy (GPO) settings
  2. If Windows 11 is blocking it, a registry fix may be required
  3. Reinstalling the extension ensures no corrupt settings

 

Also, you can try below PS Script to check and fix registry issues automatically:

function Remove-ExtensionPolicies {
    param (
        [string]$browserRegPath, 
        [string]$policyKey
    )

    if (Test-Path $browserRegPath) {
        Write-Host "Checking registry policies for: $browserRegPath" -ForegroundColor Yellow
        $regValue = Get-ItemProperty -Path $browserRegPath -ErrorAction SilentlyContinue
        if ($regValue -ne $null) {
            Remove-Item -Path $browserRegPath -Recurse -Force
            Write-Host "Removed policy restrictions from: $browserRegPath"
        } else {
            Write-Host "No policy restrictions found at: $browserRegPath"
        }
    } else {
        Write-Host "No registry path found for: $browserRegPath"
    }
}

$EdgePolicyPath = "HKLM:\Software\Policies\Microsoft\Edge"
$ChromePolicyPath = "HKLM:\Software\Policies\Google\Chrome"

Remove-ExtensionPolicies -browserRegPath $EdgePolicyPath -policyKey "ExtensionInstallForcelist"

Remove-ExtensionPolicies -browserRegPath $ChromePolicyPath -policyKey "ExtensionInstallForcelist"

Write-Host "Restarting browsers to apply changes..."
Get-Process -Name "msedge" -ErrorAction SilentlyContinue | Stop-Process -Force
Get-Process -Name "chrome" -ErrorAction SilentlyContinue | Stop-Process -Force

Write-Host "Restart Edge/Chrome and check the extension settings." 

 

Good Luck! Let me know how it goes :) 


Matt.Stewart
Automation Anywhere Team
Forum|alt.badge.img+6
  • Automation Anywhere Team
  • 11 replies
  • March 18, 2025

@Vatsy Can you answer a few questions for me?
 

  1. Are you able to install/uninstall any extension you want?
  1. Do your W11 servers need to belong in any specific OU to operate as bot runners?  And if so, have you verified they were set up in those OUs?
  2. Did you get to keep the old IDs to log in to these devices with, or are you on new IDs?  Do these IDs have the same access/permissions as the old IDs?

Vatsy
Pathfinder Advocate | Tier 6
Forum|alt.badge.img+14
  • Author
  • Pathfinder Advocate | Tier 6
  • 100 replies
  • March 18, 2025
Matt.Stewart wrote:

@Vatsy Can you answer a few questions for me?
 

  1. Are you able to install/uninstall any extension you want?
  1. Do your W11 servers need to belong in any specific OU to operate as bot runners?  And if so, have you verified they were set up in those OUs?
  2. Did you get to keep the old IDs to log in to these devices with, or are you on new IDs?  Do these IDs have the same access/permissions as the old IDs?

Hi ​@Matt.Stewart,

Glad to see your response.

Please find below my response to your questions,

1. Yes, except the AA360 extension

2. Yes, the new W11 servers need to be in a specific OU and yes they were set up in those OUs

3. We are using the same old IDs that we are still using in W10 servers as well with all the same settings.


Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Automation Anywhere Team
  • 524 replies
  • March 18, 2025

@Vatsy  I just tested this on my non-work laptop. I installed the Bot Agent and the Extension into Chrome. I was able to disable or enable the extension, and completely remove it.

What you’re probably facing is a policy within Chrome. Yes, there is a set of policies that are just for Chrome that aren’t a part of Microsoft’s regular GPO.

https://chromeenterprise.google/policies/


Dineshkumar Muthu
Navigator | Tier 3
Forum|alt.badge.img+9

Hi ​@Vatsy

I wanted to share the steps to remove a Chrome extension manually from its local path on a Windows 11 machine:

  1. Identify the Extension ID:

    • Open Chrome and go to chrome://extensions/.

    • Enable Developer Mode (top-right corner).

    • Copy the unique ID of the extension you wish to remove.

  2. Navigate to the Extension Directory:

    • Open File Explorer by pressing Win + E.

    • Go to: C:\Users\<YourUsername>\AppData\Local\Google\Chrome\User Data\Default\Extensions.

    • Replace <YourUsername> with your actual Windows user name.

  3. Delete the Extension Folder:

    • Locate the folder matching the noted extension ID.

    • Delete the folder.

  4. Restart Chrome:

    • Close and reopen Chrome to ensure the extension has been removed.

Please proceed with caution, as this will permanently delete the extension files. Let me know if you need further assistance!


Vatsy
Pathfinder Advocate | Tier 6
Forum|alt.badge.img+14
  • Author
  • Pathfinder Advocate | Tier 6
  • 100 replies
  • Answer
  • March 20, 2025

Hello Everyone!

Thanks a lot for all your replies! I really appreciate it!

We were able to fix this issue by following below steps:

  1. We first referred to the below AA360 documentation where it talks about a setting to be done within the AA360 Control Room using the Admin account to Disable the Automatic Installation of the Extensions (both MS Edge and Google Chrome) during the installation of the Bot Agent. - Documentation Link
  2. We had observed that whenever we installed the Bot Agent first with automatic install of the Extensions, it automatically locked the Extensions after installation. We then tried to install the extensions first (with no Bot Agent present in the system) and that worked, but as soon as we installed the Bot Agent it again locked the extensions.
  3. We then followed the below steps:
    a. Logged into the Control Room using our Admin account.
    b. Navigated to Administration > Settings > Devices.
    c. In the Browser extensions settings, select Edit and then selected the Disabled option to disable the automatic update of browser extensions. This option is applicable only when a Bot Agent is updated or a new Bot Agent is installed.
  4. After completing the above step, we then installed the Bot Agent with no additional steps and Voila!, this time the Bot Agent didn’t lock the Browser Extensions.
  5. We manually enabled the extensions in both MS Edge and Google Chrome and applied the appropriate settings after which our Bots ran successfully.

I wanted to share this information here so that we all are aware that whenever you will migrate to the Windows 11 servers from the Windows 10 servers, please ensure that you DO NOT MISS this checkpoint to ensure a smooth transition. I hope this post helps you all in the future! 😀

Once again a big thank you to all my fellow Pathfinders for all your help and support!

Cheers!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings