Extension for Edge

Important: UiPath Inc. and its affiliates, do not process, use, access, or store any customer data when using this product.

Important:

The deprecation of Manifest V2 extensions is scheduled to begin in June 2024.

Enterprises using the ExtensionManifestV2Availability policy to ensure the continued functioning of Manifest V2 extensions in their organization will have one additional year – until June 2025 – to migrate the Manifest V2 extensions in their organization. Browsers with the policy enabled will not be impacted by the rollout of the deprecation until that time.

The UiPath Extension for Edge MV2 installed by older versions of UiPathStudio.msi will stop working in Edge. We highly recommend upgrading your UiPath Studio and Robot installations before this happens.

See the full timeline for the Edge migration to MV3 extensions here.

The UiPath Extension for Edge MV3 is available starting with the following UiPathStudio.msi versions:

• 2022.10
• 2022.4.4+
• 2021.10.8+
• 2020.10.14+
• 2019.10.9+

These can be downloaded from the Resource Center of UiPath Automation Cloud.

This extension helps you create browser automations in Microsoft Edge. You can install this extension in multiple ways, as shown below:

Install from UiPath Studio

1. Open Studio.
2. Navigate to Home > Tools > UiPath Extensions.
3. Select Edge > Install. Choose one of the available methods from the drop-down:
   • Group Policy Offline
   • Group Policy Online
   • All Users
   • Current User
   • Native Host Only
4. Open Edge and navigate to edge://extensions.
5. Enable the UiPath Web Automation extension if needed.

Install from the Studio installer

1. Run the UiPathStudio.msi installer.
2. Select an install mode, and then select Advanced Settings > Extensions > UiPath extension for Edge Chromium. If Edge is installed on your machine, the option is selected by default.
3. Click Install. Studio setup continues while also installing the extension for Edge.

The UiPath Extension for Edge can also be installed from the command line of UiPathStudio.msi.

Install from Group Policy

You can also install the UiPath Extension for Edge by using Group Policies. This method silently installs the extension and enables it, without requiring user confirmation.

Offline

This installation method requires that the target machine is joined to a Microsoft Active Directory domain or Azure Active Directory.

It does not require access to the Edge Web Store so it can be used in controlled environments for machines that have restricted Internet access.

UiPathStudio.msi uses this installation method by default if its requirements are met.

You can also use this installation method by running from an elevated command prompt:

&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /edge-policy-offline /silent

If your organization uses Group Policies for browser extension management then the following changes are also required to be made in your organization's group policy definition:

1. In the ExtensionInstallForcelist policy, add the value:

   ndmegdjihnhfmljjoaiimbipfhodnbgf;file:///C:/ProgramData/UiPath/UiPath.Common/EdgeExtension_SelfHosted/extension_manifest_edge.xml

2. In the NativeMessagingAllowlist policy add the value: com.uipath.chromenativemsg_v2.

If you need to host the UiPath extension in your internal Web Store you can find the .crx file at this location:

C:\Program Files\UiPath\Studio\UiPath\BrowserExtension\uipath_extension_for_edge_self_hosted_mv3.crx

Online

This installation method requires that the target machine has access to the Edge Web Store (https://edge.microsoft.com/extensionwebstorebase/v1/crx and https://msedgeextensions.sf.tlu.dl.delivery.mp.microsoft.com).

UiPathStudio.msi uses this installation method if its requirements are met and the machine is not joined to a Microsoft Active Directory.

You can also use this installation method by running from an elevated command prompt:

&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /edge-chromium-policyglobal /silent

If your organization uses Group Policies for browser extension management then the following changes are also required to be made in your organization's group policy definition:

1. In the ExtensionInstallForcelist policy, add the value:

   cdfjcmjmgdnojgaojdnefhjjpaijapci;https://edge.microsoft.com/extensionwebstorebase/v1/crx

2. In the NativeMessagingAllowlist policy, add the value: com.uipath.chromenativemsg_v2.

Uninstalling

The UiPath Extension for Edge can be uninstalled by running from an elevated command prompt:

&"C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe" /edge-chromium-cleanup /silent

You can also uninstall by opening Studio, navigating to Tools > UiPath Extensions, and selecting Edge > Uninstall. The extension will be uninstalled with the same method used for the installation. This method is displayed in the disabled drop-down next to the Uninstall button.

Edge version requirements

The UiPath Extension for Edge MV2 works with all existing Edge versions.

The UiPath Extension for Edge MV3 requires Edge version 98 or greater.

When using one of the installation methods described above, the browser version will be checked and the extension with the appropriate format (MV2 or MV3) will be automatically installed.

New extension features

Support for IE Mode

Starting with UiPathStudio.msi 2020.10 the UiPath Extension For Edge can be used to automate web pages running in Internet Explorer mode.

Web pages containing Java Applets, Silverlight and ActiveX controls can be automated in Internet Explorer mode.

Automating Edge apps

Starting with UiPathStudio.msi 2022.4 the UiPath Extension for Edge can be used to automate Edge Apps.

Multiple Edge instances with multiple user profiles

Starting with UiPath version 2023.10, the UiPath Extension for Edge supports automating multiple browser instances running with multiple user profiles at the same time.

For versions lower than 2023.10, the UiPath Extension for Edge did not support automating multiple browser instances running with multiple user profiles at the same time. As such, browser automation required you to close all active instances of Edge and restart the browser using a single user profile. Starting with version 2023.10 we can accommodate scenarios of multiple browser processes running under different browser profiles, such as the case when a specific application must run on a dedicated profile to isolate sensitive data from other applications.

Note: Automating multiple browser profiles requires UiPath.UIAutomation.Activities v23.10 or newer and browser extension installed with UiPathStudio.msi v2023.10 or newer.

Opening the browser with a specific profile is now possible when using the Use Application/Browser activity. To specify a profile at browser start-up, you must append an argument to the browser command line. To do so, use the Arguments property in the Unified Application Target input section.

For Edge, the required argument is: --profile-directory="profile_path".

The profile_path is the relative path to the User data folder path specified for that Use Application/Browser activity. If the User data folder path isn't specified, then the profile path is relative to the default user data directory %LOCALAPPDATA%\Microsoft\Edge\User Data%. To find the profile path, navigate to edge://profile-internals/ and retrieve it from the Profile Path entry.

Troubleshooting

Your system administrator might have configured Group Policies that prevent theExtension for Edge from working. To enable it, please follow the instructions from the Group Policies page.

For any other issues regarding the UiPath Extension for Edge, please view the detailed troubleshooting page.