MSEdgeIE driver update does not work

[mlipok]

Bug report

Describe the bug

MSEdgeIE driver update does not work

How to reproduce

1. run wd_demo.au3
2. in browser combobox select MSEdgeIE
3. select the option to force a driver update
4. run DemoNavigation

Expected behavior

driver should update and browser should start

Screenshots

none

Additional context

none

System under test

MSEdgeIE

[Danp2]

This is the issue --

• Change log for IEDriverServer was updated 3 months ago to v4.16.0
• Last release is from 6 months ago for v4.14.0

[mlipok]

Please provide
Links to check

[Danp2]

Links come from entry in $_WD_SupportedBrowsers

[mlipok]

So the solution is to just wait until the appropriate version is available for download?

[Danp2]

Yes, unless someone can come up with a more reliable way to retrieve this webdriver that works with the current functionality of _WD_UpdateDriver.

[mlipok]

So, since this is beyond our scope, should we consider this issue closed for our project?

[Danp2]

I suggest leaving it open to prevent further reports on the same issue.

[sven-seyfert]

Is it a valid consideration to skip the support of the IE driver variant in the near future? Or do you think it's good to support that driver as long as possible? I am just curious what you both think of 😇 ?

Best regards
Sven

[mlipok]

As long as possible, as long selenium support it.

[sven-seyfert]

Maybe it's time to let IE go 😁 .

[Elias1958]

The solution below worked for me, tested Only for 64Bits
Change: msedgedriver.azureedge.net
to: msedgedriver.microsoft.com

wd_core.au3

Global Const $_WD_SupportedBrowsers

Change:
[ _
"msedge", _
"msedge.exe", _
"msedgedriver.exe", _
True, _
"ms:edgeOptions", _
"'https://msedgedriver.azureedge.net/LATEST_RELEASE_' & StringLeft($sBrowserVersion, StringInStr($sBrowserVersion, '.') - 1) & 'WINDOWS'", _
"", _
'"https://msedgedriver.azureedge.net/" & $sDriverLatest & "/edgedriver" & (($bFlag64) ? "win64.zip" : "win32.zip")' _
], _

To:
[ _ ; Updated by Elias using Claud IA
"msedge", _
"msedge.exe", _
"msedgedriver.exe", _
True, _
"ms:edgeOptions", _
"'https://msedgedriver.microsoft.com/LATEST_RELEASE_' & StringLeft($sBrowserVersion, StringInStr($sBrowserVersion, '.') - 1) & 'WINDOWS'", _
"", _
'"https://msedgedriver.microsoft.com/" & $sDriverLatest & "/edgedriver" & (($bFlag64) ? "win64.zip" : "win32.zip")' _
], _

[sven-seyfert]

Hi @Elias1958 👋 ,

thanks for your input but we are talking about the old IE variant "msedgeie" (IEDriverServer.exe), not MSEdge. The URL changes are already fixed here, but there is no published version for that yet. Such "unreleased" changed can be found in the CHANGELOG file. I assume @Danp2 will release a new version soon 🤞 .

Best regards
Sven

[JALucena]

Checking the website that au3WebDriver uses to obtain the latest available version of IEDriverServer.exe:
https://github.com/SeleniumHQ/selenium/blob/trunk/cpp/iedriverserver/CHANGELOG
It can be seen that the latest version is 4.16.0.0. This is what au3WebDriver reports in the internal function __WD_GetLatestWebdriverInfo.

However, on the Selenium download site:
https://www.selenium.dev/downloads
The latest available version is 4.14.0.

When creating the URL for version 4.16.0 (as the internal function __WD_GetLatestWebdriverInfo does), this URL doesn't point anywhere, resulting in a "not found" error.

In my opinion, the problem stems from a discrepancy between the latest version published in the changelog by the driver maintainer and the version that is actually available.

Personally, I've been using version 4.14.0 with MS Edge, and it works fine for my needs, but I had to download it manually.

[sven-seyfert]

Hi @mlipok ,

is this Github issue still relevant? I mean would you expect to support an old IE variant "msedgeie" (IEDriverServer.exe) which is only availble on unsupported Windows operation systems?

I guess there are cases where users use the old IE, but where to draw the line regarding support?
In my opinion it would be okay to get rid of the old IE support.
Nevertheless it's up to @Danp2 , at the end.

You opened the issue in April 2025, do you depend on that in any case?

Best regards
Sven