chromedriver.cmd fails to launch with newer nodejs versions[🐛 Bug]:

[benm071]

What happened?

Trying to use selenium-webdriver against chrome instances fails to launch chromedriver.cmd and thus chrome for testing when run on Windows 11 against newer nodejs instances (such as 18.20.2) due to a security patch made in nodejs that prevents spawn/spawnSync from launching .cmd or .bat without { shell: true }

See nodejs/node#52681 for example

How can we reproduce the issue?

Try to run any nodejs based test script using chrome/chromedriver on a Windows system with one of the security-patched nodes.  chromedriver.cmd will never launch because it fails internally to selenium-webdriver with a node EINVAL error (which is eaten and never displayed)

Relevant log output

No output

Operating System

Windows 11

Selenium version

4.23.0

What are the browser(s) and version(s) where you see this issue?

Chrome 127

What are the browser driver(s) and version(s) where you see this issue?

chromdriver 127.x

Are you using Selenium Grid?

No

[github-actions]

@benm071, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[github-actions]

This issue is looking for contributors.

Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested.

[harsha509]

Hi @benm071,

Thank you for raising the issue.

I wasn’t able to reproduce it with the provided configuration (Windows 11, Node.js versions 18.20.2 and 20.16.0 LTS, Selenium WebDriver 4.23.0).

You can find the repo here: https://github.com/harsha509/issue-14353.

If the issue persists, could you please provide a Short, Self-Contained, Correct (Compilable) Example to help us investigate further?

Thanks,
Sri

[zlatinejc]

Hi @benm071,

Thank you for raising the issue.

I wasn’t able to reproduce it with the provided configuration (Windows 11, Node.js versions 18.20.2 and 20.16.0 LTS, Selenium WebDriver 4.23.0).

You can find the repo here: https://github.com/harsha509/issue-14353.

If the issue persists, could you please provide a Short, Self-Contained, Correct (Compilable) Example to help us investigate further?

Thanks, Sri

Hi,
I have to reignite this issue as it is not working.

I reran your tests and they fail the same as mine.

I am running:

• Node 18.17.1
• selenium-webdriver: 4.23.0
• Chrome: 127.0.6533.120 (Official Build) (64-bit)

[Delta456]

Does the issue still persists?