Selenium TimeoutException with Microsoft Edge v134.0.3124.68

Question

Selenium TimeoutException with Microsoft Edge v134.0.3124.68

Ravi Prakash 0

Selenium scripts fail with TimeoutException on Microsoft Edge v134.0.3124.68 however working perfectly with 132.0.2957.68. Script freezing when connecting to the Microsoft Edge Browser and throw an error. selenium.common.exceptions.TimeoutException: Message: timeout: Timed out receiving message from renderer: 600.000.

Anonymous

2025-03-31T02:25:04.73+00:00

Hi @Ravi Prakash

Which version of Edge WebDriver do you use? Could you please provide a minimal code snippet which can reproduce the issue?

Ravi Prakash 0

This is the code which i am using to lanuch edge:

import subprocess

url = "https://www.selenium.dev/"

# Launch Edge with remote debugging enabled
subprocess.Popen(
    [
        "C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe",
        "--remote-debugging-port=9220",
        "--user-data-dir=C:\\Users\\xxx\\xxx\\Data",
        url
    ],
    shell=True
)

print("Microsoft Edge launched with remote debugging on port 9220.")


and the code below which connect to edge

import socket

import os

from selenium.webdriver.edge.options import Options

from selenium.webdriver.edge.service import Service

from selenium import webdriver

def is_debugging_port_active(host, port):

with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s:

    try:

        s.settimeout(2)

        s.connect((host, port))

        return True

    except (socket.timeout, ConnectionRefusedError):

        return False
```def initialize_driver():

```python
# Use a more flexible path approach

src = os.path.join(os.path.expanduser("~"), "Downloads", "msedgedriver.exe")



if not os.path.exists(src):

    raise FileNotFoundError(f"EdgeDriver not found at {src}")



ser = Service(src, timeout=5)

opt = Options()

opt.add_experimental_option("debuggerAddress", "localhost:9220")



if not is_debugging_port_active("localhost", 9220):

    raise ConnectionError("Debugging port 9220 is not active. Please start Edge with remote debugging enabled.")



try:

    return webdriver.Edge(service=ser, options=opt)

except Exception as e:

    raise Exception(f"Failed to initialize WebDriver: {str(e)}")
```try:

```ruby
driver = initialize_driver()

print("Current URL:", driver.current_url)
```except Exception as e:

```yaml
print(f"Error: {str(e)}")

Ravi Prakash 0 Reputation points

2025-04-02T09:58:03.94+00:00

I am facing an issue both version v134.0.3124.68 and v134.0.3124.85 and also using same version of msedgedriver
Anonymous

2025-04-03T02:40:30.7033333+00:00

Hi @Ravi Prakash

I test your code and it works fine. I test with Edge version 134.0.3124.93. You could update to the latest version and test again.

Besides, you could kill all Edge progresses manually in task manager before you run the Selenium code.
Romain Joachim 0 Reputation points

2025-04-07T07:00:12.2066667+00:00

Hi,
I have the same problem, it works again if I delete the edge profile directory.
Does it also work for you if you delete the profile directory ? or specify a specific profile directory other than "Default" ?
Ravi Prakash 0 Reputation points

2025-04-20T08:34:06.27+00:00

there is issue in micrsofot edge version but now working fine with versio 134.0.3124.93
Smith, Steven N 0 Reputation points

2025-04-24T22:27:35.7833333+00:00

I am currently having this issue as well. We utilize the debugger address within our edge options when initializing the driver. This allows us to connect to an already open browser on the desktop. This worked fine for everyone using it on Edge 132 but has multiple people experiencing issues on Edge 134. This behavior is not consistent across all users. Rolling back to Edge 132 resolved the issue.

Your answer

Anonymous

2025-03-31T02:25:04.73+00:00

Hi @Ravi Prakash

Which version of Edge WebDriver do you use? Could you please provide a minimal code snippet which can reproduce the issue?
Ravi Prakash 0 Reputation points

2025-04-02T09:56:09.85+00:00

This is the code which i am using to lanuch edge:

import subprocess url = "https://www.selenium.dev/" # Launch Edge with remote debugging enabled subprocess.Popen( [ "C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe", "--remote-debugging-port=9220", "--user-data-dir=C:\\Users\\xxx\\xxx\\Data", url ], shell=True ) print("Microsoft Edge launched with remote debugging on port 9220.") and the code below which connect to edge

import socket

import os

from selenium.webdriver.edge.options import Options

from selenium.webdriver.edge.service import Service

from selenium import webdriver

def is_debugging_port_active(host, port):

with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s: try: s.settimeout(2) s.connect((host, port)) return True except (socket.timeout, ConnectionRefusedError): return False ```def initialize_driver(): ```python # Use a more flexible path approach src = os.path.join(os.path.expanduser("~"), "Downloads", "msedgedriver.exe") if not os.path.exists(src): raise FileNotFoundError(f"EdgeDriver not found at {src}") ser = Service(src, timeout=5) opt = Options() opt.add_experimental_option("debuggerAddress", "localhost:9220") if not is_debugging_port_active("localhost", 9220): raise ConnectionError("Debugging port 9220 is not active. Please start Edge with remote debugging enabled.") try: return webdriver.Edge(service=ser, options=opt) except Exception as e: raise Exception(f"Failed to initialize WebDriver: {str(e)}") ```try: ```ruby driver = initialize_driver() print("Current URL:", driver.current_url) ```except Exception as e: ```yaml print(f"Error: {str(e)}")
Ravi Prakash 0 Reputation points

2025-04-02T09:58:03.94+00:00

I am facing an issue both version v134.0.3124.68 and v134.0.3124.85 and also using same version of msedgedriver
Anonymous

2025-04-03T02:40:30.7033333+00:00

Hi @Ravi Prakash

I test your code and it works fine. I test with Edge version 134.0.3124.93. You could update to the latest version and test again.

Besides, you could kill all Edge progresses manually in task manager before you run the Selenium code.
Romain Joachim 0 Reputation points

2025-04-07T07:00:12.2066667+00:00

Hi,
I have the same problem, it works again if I delete the edge profile directory.
Does it also work for you if you delete the profile directory ? or specify a specific profile directory other than "Default" ?
Ravi Prakash 0 Reputation points

2025-04-20T08:34:06.27+00:00

there is issue in micrsofot edge version but now working fine with versio 134.0.3124.93
Smith, Steven N 0 Reputation points

2025-04-24T22:27:35.7833333+00:00

I am currently having this issue as well. We utilize the debugger address within our edge options when initializing the driver. This allows us to connect to an already open browser on the desktop. This worked fine for everyone using it on Edge 132 but has multiple people experiencing issues on Edge 134. This behavior is not consistent across all users. Rolling back to Edge 132 resolved the issue.

Share via

Selenium TimeoutException with Microsoft Edge v134.0.3124.68

Your answer