Intermittent Selenium failures on dynamic elements after migration to Windows 11 (Edge)

[Mateusz Ciałowicz]

Hi everyone,

I’ve been dealing with random Selenium test failures since we migrated our environments from Windows 10 to Windows 11.

We’re running Selenium 4.36 using Edge WebDriver (in GUI mode locally and headless mode in the cloud). The issue occurs on multiple local Windows 11 machines as well as on the build agents — so it’s not machine-specific.

Here’s what happens:

• Some tests fail randomly, especially when interacting with dynamic elements (e.g. elements that appear after AJAX or DOM updates).

• .click() executes without any exception, but the page doesn’t seem to receive the click — the action simply doesn’t trigger.

• Occasionally, we also get timeouts waiting for elements that are clearly visible and interactable.

• Adding explicit waits or retry logic (even clicking up to 5 times in a loop) doesn’t solve it.

Static elements always work fine — this only affects dynamic content.
This started happening around the same time WebDriver Manager stopped working, so we’ve been downloading the Edge drivers manually since then.

Has anyone experienced similar behavior on Windows 11 with Selenium 4 and Edge?
Could this be related to driver versions, WebDriver event handling, or OS-level focus/timing issues?
Any suggestions  would be greatly appreciated!