Cannot communicate with browser Please check

Hi everyone,

The UiPath chrome extension is installed, and i have attached screenshot of the extension settings for reference. Rebooting the machine helps sometimes, and reinstalling the extension fixes the issue temporarily but after a while the problem comes back again.

Has anyone experienced a similar issue where browser extension randomly stops responding even though it is properly installed??

Any guidance or best practices would be really helpful.

Thanks for the help :folded_hands:

1 Like

Hi @Mridul_iyer

Welcome to UiPath Community!

This mostly happens due to group policy or security restriction on the machine or may be Messaging Host Exe was not running or blocked

you can check from this:

1 Like

The UiPath Chrome extension is present in the Chrome Web Store. In fact, there are several Chrome extension versions, bundled with different Studio versions.

The installation directly from the Chrome Web Store is not presented in the online doc because the extension should be installed either from Studio, or with the Studio Installer UiPathStudio.msi, or with SetupExtensions.exe, to ensure a correct installation of all the components.

Possible causes for disabled extension:

  • The extension may become disabled if Studio is upgraded with UiPathStudio.msi while Chrome is running.This will also upgrade the Chrome extension, but if Chrome is running then the user will have to manually re-enable the extension.The solution is to simply close Chrome when upgrading Studio.
  • Extensions may be removed when they are installed via Group Policies and new Group Policies are enforced, that block certain extensions or override the entries added by UiPathStudio.msi in the initial installation.To re-enable the UiPath extension, the Chrome Extension ID should be added to the ExtensionInstallForcelist policy. More details for the installation from Group Policy are available here and here.

For reference, here is a summary of the installation methods available for Chrome extension:

1. Per-user enabled manually

  • Command: /chrome
  • Used for UiPathStudio.msi without Admin rights
  • Outcome: Requires the user to manually enable the extension in the browser

2. Per-machine enabled manually

  • Command: /chromeglobal
  • Pre-requisites: Admin rights
  • Outcome: Requires the user to manually enable the extension in the browser

3. Group Policy Online

  • Command: /chromepolicyglobal
  • Pre-requisites: Admin rights, Internet access (to the Web Store URLs)
  • Outcome: Extension automatically enabled in the browser, All permissions granted

4. Group Policy Offline

  • Command: /chrome-policy-offline
  • Pre-requisites: Admin rights, Machine joined to Active Directory
  • Outcome: Extension automatically enabled in the browser, All permissions granted

So, the first 2 installation methods require the extension to be enabled manually in the browser, after installation.

The benefit of the installation using Group Policy is that the extension is automatically enabled in the browser. The extension cannot be disabled when installed using this method, so it should solve these types of issues.

Hi @Mridul_iyer

Welcome to the Community

This is not a permissions issue (as your screenshot confirms). It’s mainly a Chrome–Robot communication stability problem. Please try this steps

1.Close all Chrome instances completely
Ensure no chrome.exe processes are running (Task Manager) before starting the automation.
You can also use a Kill Process (chrome) activity.
2.Verify Chrome profile
Make sure the UiPath extension is installed in the same Chrome profile that UiPath launches during automation.
3.Restart UiPath Robot service
Restarting the UiPath Robot Service (not just Studio) often restores the extension connection.
4.Disable “Continue running background apps when Chrome is closed”
Chrome → Settings → System → turn this OFF.
5.Avoid Incognito unless required
Incognito mode can cause instability unless explicitly needed.
6.Keep Chrome and UiPath versions compatible
After Chrome updates, reinstalling the extension once is expected.
7.Ensure same user session
For attended automations, Chrome and the robot must run under the same Windows user

Hope it resolve your issue if yes then please mark as solved .

Thanks & Happy Automations

Hi @Mridul_iyer

This is temp. issue, due to some group policies or antivirus..
pls check with IT Team.

For more:
https://docs.uipath.com/studio/standalone/2023.10/user-guide/chrome-group-policies#group-policies

Happy automation with UiPath

Hi @Mridul_iyer

Yes, I’ve seen this behavior before. Even when the UiPath Chrome extension is installed, it can stop responding randomly due to browser updates, corrupted extension state, or Chrome running in the background after a crash.

A few things that helped in my case:

  • Fully close all Chrome processes from Task Manager before running the bot
  • Disable and re-enable the UiPath extension instead of reinstalling every time
  • Make sure the Chrome and UiPath Studio versions are compatible
  • Turn off Chrome’s “Continue running background apps when Chrome is closed” option
  • If using multiple Chrome profiles, ensure the extension is enabled for the correct profile

Reinstalling works only temporarily because it resets the extension state. Usually, cleaning up background Chrome instances and keeping versions aligned fixes the issue long-term.

Hope this helps :folded_hands:

Hi @Mridul_iyer ,

First Clean your cookies & chache from your browser and disable “collect error” field and then close your browser.

After that goto the location where UiPath installed and first uninstall extension by

“path”/SetupExtensions.exe/ chrome/uninstall

as shown in the below screenshot

After that install chrome extension using

“Path”/SetupExtensions.exe/ chrome

As shown in below screenshot

Then go to browser and click on install extension popup

Issue will be resolved.

You can refer below screenshot for edge browser and chrome browser extension installation

@Mridul_iyer

most chances are the group policies if its a corporate laptop

generally because of chromenaticemesaaging.exe not running also it can happen

you can check the frequent issues and fixes here..even group policy issue and the fix is mentioned

cheers

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.