- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- Variables
- Arguments
- Imported Namespaces
- Control Flow
- Object Repository
- Logging
- The ScaleCoordinates Migration Tool
- The ScreenScrapeJavaSupport Tool
- StudioPro
- Extensions
- Troubleshooting
This page presents the most frequent reasons for which the UiPath Extension for Microsoft Edge might not work properly, and how to solve these issues.
Check if the Extension for Microsoft Edge is installed and enabled
- In Microsoft Edge, navigate to
edge://extensions/. - Make sure the extension is installed and enabled, as explained here.
- If the extension was installed correctly but does not appear in Microsoft Edge, check if there are Group Policies that affect the extension, as explained here.
Check If ChromeNativeMessaging.exe Is Running
The ChromeNativeMessaging.exe enables communication between the UiPath Extension for Edge and the UiPath Studio/Robot.
-
Open Microsoft Edge.
-
Open Task Manager.
-
Check if the
ChromeNativeMessaging.exeprocess is running. -
If the process is not running:
Check if ComSpec variable is defined correctly
Description
The ChromeNativeMessaging.exe process runs under the current user and it uses cmd.exe to start the browser.
If the ComSpec environment variable is missing or has an invalid value, then Microsoft Edge cannot launch the ChromeNativeMessaging.exe.
Furthermore, the administrator may disable the command prompt for some users or configure it to always run with elevated privileges.
Solution
Manually add the correct value for the ComSpec environment variable. This variable is set at Windows installation and must be set to: %SystemRoot%\system32\cmd.exe.
Other workarounds
If the ComSpec environment variable is set correctly but the problem persists, the user may not have permission to run the command prompt. In this case, the ChromeNativeMessaging.exe process cannot be started with cmd.exe running under the current user.
Starting with Chromium 120.0.6090+, a NativeHostsExecutablesLaunchDirectly Group Policy allows admins to turn this on for users in restricted environments (Cloud PCs that forbid cmd.exe, for example).
Enable access to file URLs and InPrivate mode
By default, the extension is not granted access to File URLs or InPrivate mode. To enable these:
-
In Microsoft Edge, navigate to
edge://extensions/. The Microsoft Edge Extensions page is displayed. -
Navigate to the UiPath Browser Automation extension and click the Details button.
-
Make sure the Allow in InPrivate and Allow access to file URLs options are selected.
Multiple browser profiles
Multiple Microsoft Edge instances with multiple user profiles
UiPath Extension for Microsoft Edge does not support automating multiple browser instances running with multiple user profiles at the same time. Therefore, browser automation requires you to close all active instances of Microsoft Edge and restart the browser using a single user profile.
Stopping all Microsoft Edge instances
In some cases, Microsoft Edge background processes prevent it from closing completely, which interferes with automations even if the browser instance is not visible.
We recommend closing Microsoft Edge by right-clicking the Microsoft Edge icon in the System Tray, and selecting Close Microsoft Edge. This ensures that no other user profiles remain in use in the background.
Known Issues Specific to MV3 Extensions
Click activity with Simulate fails on specific web page elements
The Click activity with the Simulate input method no longer works on HTML elements that have a click handler with javascript: URI.
In this case, the simulated click will not take effect and no errors will reported.
This was reported as a Chromium bug here: https://bugs.chromium.org/p/chromium/issues/detail?id=1299742 This issue is quite rare as very few HTML elements have click handlers in this form.
Workaround
Change the input method for the failing Click activity from Simulate to any other input method:
- Chromium API
- Hardware Events
- Window Messages
The DeveloperToolsAvailability Group Policy value must be set to 1
The DeveloperToolsAvailability has the following possible values:
- 0 = Disallow usage of the Developer Tools on extensions installed by enterprise policy, allow usage of the Developer Tools in other contexts
- 1 = Allow usage of the Developer Tools
- 2 = Disallow usage of the Developer Tools
If the UiPath Extension for Edge is installed using Group Policy, then the DeveloperToolsAvailability must be set to 1 to enable the full functionality of the extension.
This value is automatically set correctly when the extension is installed but it will be overwritten if your system administrator has set another value for this policy.
The other values for DeveloperToolsAvailability cause the problems listed below.
If DeveloperToolsAvailability is set to 0 then:
- The UiPath Extension for Edge will be restricting to working with LTS versions of UiAutomation (19.10.x, 20.10.x, 21.10.x, 22.4.x)
- The
InjectJSActivity will not work.
If DeveloperToolsAvailability is set to 2 then:
- All the limitations from
DeveloperToolsAvailability=0apply - The
ChromiumAPIinput method will not work.
The UiPath Web Automation browser window shows a warning
The UiPath Web Automation browser window shows the following warning if ChromeNativeMessaging.exe could not be started:
Cannot communicate with UiPath Platform The native part of the extension is not configured correctly.
Re-install the extension from UiPath Studio.
Open Browser activity has an insufficient timeout
For MV3 extensions, the browser loads the extension later, after the web pages have loaded. This means that on slower machines, the Open Browser activity from UiPath.UiAutomation.Activities version 20.10 or older can reach the internal timeout of 20 seconds before the extension has started.
Starting with v20.10.13, the internal timeout for the Open Browser activity has been increased from 20 seconds to 60 seconds.
Additionally, you can configure the timeout through the UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS environment variable. For example, set UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS=120 to use 120 seconds for the activity's timeout.
- Check if the Extension for Microsoft Edge is installed and enabled
- Check If ChromeNativeMessaging.exe Is Running
- Check if ComSpec variable is defined correctly
- Description
- Solution
- Other workarounds
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Multiple Microsoft Edge instances with multiple user profiles
- Stopping all Microsoft Edge instances
- Known Issues Specific to MV3 Extensions
- Click activity with Simulate fails on specific web page elements
- The DeveloperToolsAvailability Group Policy value must be set to 1
- The UiPath Web Automation browser window shows a warning
- Open Browser activity has an insufficient timeout