Unable to Launch Microsoft Edge using Selenium Manager in Leapwork
Unable to Launch Microsoft Edge using Selenium Manager in Leapwork
Introduction If you’re using Selenium.WebDriver v4.11, you’re likely experiencing issues where Microsoft Edge automation is failing because Selenium Manager isn’t downloading the EdgeDriver automatically. This challenge can cause your Edge tests or workflows to stop working unexpectedly. In this article, we’ll walk you through the root cause and show you how to fix it quickly.
Why does it happen? Microsoft recently updated the Fully Qualified Domain Name (FQDN) for EdgeDriver downloads:
- Old URL: https://msedgedriver.azureedge.net
- New URL: https://msedgedriver.microsoft.com
Since Selenium.WebDriver v4.11 is still using deprecated URL (azureedge.net), the Selenium Manager's automatic download of the Edge Driver is failing.
Resolution: Download the Edge Driver manually You can manually download and use browser drivers as an alternative workaround.
- Open Microsoft Edge.
- Click the three-dot menu (⋯) in the top-right corner.
- Help and feedback > About Microsoft Edge.
- You will see the version number listed at the top (e.g., Version 125.0.2535.51).
- Download the supported version of msedgedriver.exe from the official source.
- Place the downloaded EdgeDriver executable in the appropriate directory:
- Studio machine: C:\Program Files\Leapwork\Studio
- Agent machine: C:\Program Files\Leapwork\Agent
Note: Please be assured that this will be resolved as soon as Selenium.WebDriver releases an updated NuGet package addressing the issue. While a fix has already been implemented in later releases of related libraries such as SeleniumBase (v4.40), the official Selenium.WebDriver NuGet package has not yet incorporated this change.
We are closely monitoring the update and will apply it promptly once available to ensure smooth automation workflows for Edge using Selenium Manager in Leapwork.
If you have any questions, please contact our Priority Support.