Selenium 4.30 - .NET Unable To Get Driver

[Steven Smith]

I am having an issue with Microsoft Edge 134 and Selenium 4.30. In the edge options I am providing the debugger address of my open Edge browser that has the remote debugging port open.

For most people this works fine. It connects to the existing open browser and allows my application to access the pages and run automated tasks. Edge 134 introduced issues where selenium times out calling the session endpoint of the edge driver. Rolling users back to Edge 132 resolved the issue. Not sure how to address this issue since it appears that the msedgedriver.exe starts to run but Selenium never seems to connect for the user.

If I have the user close all open Edge browsers and then re-open the edge browser with the remote debugging port open it will work for some time and then eventually fail. Looking for any other possible ideas for this behavior. I cannot recreate it on my development machine, but it is happening on end user machines. I am not sure what is changing that is causing this issue.