We started seeing this error on Sunday: Could not communicate with the UiPath extension for browser ‘msedge.exe’. Please make sure the extension is installed and enabled.
I have checked with our security team and the extension isn’t being blocked by the firewall and we don’t have group policies that manage this extension.
This only occurs for existing projects we have, if I create a new project it will work correctly.
Looking at the packages we use they are all up to date and UiPath is up to date
If anyone has any idea we would be keen to try them out.
When encountering the error “Could not communicate with the UiPath extension for browser ‘msedge.exe’” in an ‘in-private’ mode of UiPath, there are a few troubleshooting steps you can follow to try and resolve the issue:
Extension Compatibility: Ensure that the version of the UiPath extension installed in the Microsoft Edge browser is compatible with the version of UiPath Studio you are using. Sometimes, an update to the browser or Studio might cause compatibility issues. Check the UiPath documentation or release notes for compatibility information.
Extension Reinstallation: Try uninstalling and then reinstalling the UiPath extension for Microsoft Edge. It’s possible that the extension installation got corrupted or the update process was not successful.
Check Antivirus/Firewall Settings: Even though you mentioned the extension isn’t being blocked by the firewall, double-check the antivirus and firewall settings to ensure that the UiPath extension is allowed to communicate with the browser and UiPath Studio.
Clear Browser Data: In Microsoft Edge, clear the browsing data, including cache and cookies. Sometimes, conflicts in the browser’s data can lead to communication issues with extensions.
Check Extension Permissions: In Microsoft Edge, go to the extension settings and verify that the UiPath extension has the necessary permissions to access and interact with web pages.
Check UiPath Project Dependencies: Examine the dependencies used in the existing projects that are causing the issue. There might be a conflict between the versions of some packages or activities that’s causing the problem. Ensure all dependencies are compatible and up to date.
Reset Edge Settings: If the issue persists, you can try resetting Microsoft Edge settings to their default values. This can sometimes resolve conflicts and issues with extensions
Hi, we’ve been having the same problem since yesterday.
If Edge browser is opened in an anonymous window, Chrome Native Messaging does not start.
If I open a new standard window at the same time as the anonymous window, the robot starts working in the anonymous window.
There are some changes in the new browser version: Microsoft Edge release notes for Stable Channel | Microsoft Learn
Thank you for any recommendations on how to resolve the issues.
I’ve the same issue, non of the standard solutions work. Tried reinstalling the extension, clearing whole browser, creating new profile. Error: Edge: Could not communicate with the UiPath extension for browser ‘msedge.exe’. Please make sure the extension is installed and enabled.
I experience this issue in the robot and running from studio.
Stops running the job and give the error Edge: Could not communicate with the UiPath extension for browser ‘msedge.exe’. Please make sure the extension is installed and enabled.
Extension is visible and running without errors
Error log:
UiPath.Executor 23.4.1.0
System.NullReferenceException: Object reference not set to an instance of an object.
at UiPath.UIAutomationNext.Services.SearchService.GetComputerVisionMatchesAsync(ISearchCVRequest request, TimeoutToken timeoutToken)
at UiPath.UIAutomationNext.Services.TargetServiceBase.GetMatchesBySingleSearchStepTask(ITarget target, TargetSearchSteps step, ISearchCache cache, IUiNodeX parentNode, TimeoutToken token)
at UiPath.UIAutomationNext.Services.TargetServiceBase.GetMatchesByTargetStep(ITarget target, TargetSearchSteps step, ISearchCache cache, IUiNodeX window, TimeoutToken token)
at UiPath.UIAutomationNext.Services.TargetFindService.FindMatchesParallelAsync(FindMatchesRequest request, ISearchCache cache, IUiNodeX window, TimeoutToken token)
and
UiPath.Executor 23.4.1.0
UiPath.UIAutomationNext.Exceptions.ApplicationOpenException: Could not communicate with the UiPath extension for browser ‘msedge.exe’. Please make sure the extension is installed and enabled.
We are having the same issue as well where Chrome Native Messaging does not start when opening Edge in InPrivate mode. We have tried all the standard troubleshooting steps including updating packages to their latest versions. The current workaround we have is to open a normal Edge browser follow by InPrivate Edge browser and closing the normal Edge browser.
A. Before processing the In Private window, add processing to launch Edge (normal mode instead of In Private window) by the “Open Browser” or “Use Application/Browser” activity.
“ChromeNativeMessagingHost.exe” will automatically start when you open the Edge browser (normal mode, not the In Private window), so you can get the elements of the In Private window from Studio/Robot.
The disadvantage of this method is that it requires changes to the automation project.
B. Set the “Incognito/Private Window” option in the “Use Application/Browser” activity to False and use “CustomFolder” in “User Data Folder Mode” instead of this option.
Information such as cookies can be cleared by deleting the custom folder.
The disadvantage of this method is that it requires changes to the automation project.
C. Install UiPath MV2 extension.
It can be installed by adding the extension ID “hmpkmolbbcopahpbplbdaapacncbbc” to the ExtensionInstallForcelist group policy.
The advantage of this method is that no changes to the automation project are required.
The disadvantage of this method is that the user must manually enable the “Allow in InPrivate” option in UiPath’s browser extension.
Reinstalling will probably fix this issue and have tried to reinstall
As said above have tried to reinstall but issue still continues.
Have checked with our security team they have told us the firewall isn’t blocking the Extension. They have said UiPath tries to communicate with the Extension but it cannot find it.
Cleared browsewr data and issue still exists
Permissions as per my screenshots above should allow UiPath to work with an in-private webpage.
Dependencies are all up-to-date none of them require any update.
Have yet to try this but will try exhaust all other alternatives first.
Open the browser application that you want to use for automation if it is chrome application.
Open the chrome application manually and at the top right corner you find the three dots hit on three dots → select the extensions → Then select the UiPath extension → if you are not given the extension to UiPath provide the extension and try.
Thanks for your reply. I think the issue has been figured out. Looks like its an issue where if Edge is launched in ‘in-private’ the ‘Chrome Native Messaging Host’ doesn’t launch.
This application is needed for UiPath to communicate with Edge.
The work around for now seems like:
Open a normal instance of Edge first to have ‘Chrome Native Messaging Host’ start up, and
Then to launch another instance of Edge in-private mode. This solution allows UiPath to work with Edge in-private mode.
