[🐛 Bug]: [java] Cannot instantiate ChromeDriver on Windows using selenium 4.16 #13261

jstefek · 2023-12-07T11:56:29Z

What happened?

I cannot instantiate ChromeDriver on selenium 4.16 on Windows 11.

Note: I was mainly focused to use version 4.16 to get over the bug #13091, which should be resolved by d1787a9 . On linux it seems to work correctly, but not on Windows.

How can we reproduce the issue?

Set up a simple maven project. Using just Selenium java.

    <dependencies>
        <dependency>
            <groupId>org.seleniumhq.selenium</groupId>
            <artifactId>selenium-java</artifactId>
            <version>4.16.0</version>
        </dependency>
    </dependencies>

with one executable main method:

import org.openqa.selenium.chrome.ChromeDriver;

public class Main {
    public static void main(String[] args) {
        ChromeDriver chromeDriver = new ChromeDriver();
        chromeDriver.quit();
    }
}

Relevant log output

Using selenium 4.16 I get following error:

Exception in thread "main" org.openqa.selenium.remote.NoSuchDriverException: Unable to obtain: Capabilities {browserName: chrome, goog:chromeOptions: {args: [], extensions: []}}, error Command failed with code: -1073741701, executed: [--browser, chrome, --output, json]

Build info: version: '4.16.0', revision: '15400459dd*'
System info: os.name: 'Windows 11', os.arch: 'amd64', os.version: '10.0', java.version: '21.0.1'
Driver info: driver.version: ChromeDriver
	at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:25)
	at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:13)
	at org.openqa.selenium.chrome.ChromeDriver.generateExecutor(ChromeDriver.java:100)
	at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:89)
	at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:84)
	at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:73)
	at org.example.Main.main(Main.java:8)
Caused by: org.openqa.selenium.WebDriverException: Command failed with code: -1073741701, executed: [--browser, chrome, --output, json]

Build info: version: '4.16.0', revision: '15400459dd*'
System info: os.name: 'Windows 11', os.arch: 'amd64', os.version: '10.0', java.version: '21.0.1'
Driver info: driver.version: ChromeDriver
	at org.openqa.selenium.manager.SeleniumManager.runCommand(SeleniumManager.java:157)
	at org.openqa.selenium.manager.SeleniumManager.getDriverPath(SeleniumManager.java:299)
	at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:22)
	... 6 more

Using selenium 4.15 all works as expected.

Operating System

Windows 11

Selenium version

4.16

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

Chrome 120

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

from SeleniumManager

Are you using Selenium Grid?

no

The text was updated successfully, but these errors were encountered:

github-actions · 2023-12-07T11:56:45Z

@jstefek, 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!

diemol · 2023-12-07T16:40:08Z

@joerg1985 @bonigarcia seems the issue is now happening in non Docker environments?

github-actions · 2023-12-07T18:36:14Z

We need more information about this issue in order to troubleshoot.

Please turn on logging and re-run your code. Information on how to adjust logs for your language can be found in our
Troubleshooting documentation.

letskodeit · 2023-12-07T19:15:38Z

@titusfortner
Can you please let me know how to enable logging?
I referred to the documentation and tried to enable. I followed these steps:

Downloaded the dependency using this:

<dependency>
  <groupId>com.titusfortner</groupId>
  <artifactId>selenium-logger</artifactId>
  <version>2.3.0</version>
</dependency>

Added this line in the code before initializing the driver
SeleniumLogger.enable();

Example:

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.edge.EdgeDriver;

import com.titusfortner.logging.SeleniumLogger;

public class MSEdgeDriverDemo {
	public static void main(String[] args) {
		
		SeleniumLogger.enable();
		
		WebDriver driver = new EdgeDriver();
		driver.manage().window().maximize();
		driver.get("https://www.letskodeit.com");
		driver.quit();
	}
}

I still see the same error in Console:

2023-12-07 11:12:26 FINE Selenium [SeleniumManager getBinary] Selenium Manager binary found at: C:\Users\aniltomar\.cache\selenium\manager\0.4.16\selenium-manager.exe 
2023-12-07 11:12:26 FINE Selenium [SeleniumManager runCommand] Executing Process: [--browser, MicrosoftEdge, --output, json, --debug] 
2023-12-07 11:12:27 FINE Selenium [ExternalProcess] completed to copy the output of process 4848 
Exception in thread "main" org.openqa.selenium.remote.NoSuchDriverException: Unable to obtain: Capabilities {browserName: MicrosoftEdge, ms:edgeOptions: {args: [], extensions: []}}, error Command failed with code: -1073741701, executed: [--browser, MicrosoftEdge, --output, json, --debug]

Build info: version: '4.16.1', revision: '9b4c83354e'
System info: os.name: 'Windows 11', os.arch: 'amd64', os.version: '10.0', java.version: '17.0.6'
Driver info: driver.version: EdgeDriver
	at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:25)
	at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:13)
	at org.openqa.selenium.edge.EdgeDriver.generateExecutor(EdgeDriver.java:72)
	at org.openqa.selenium.edge.EdgeDriver.<init>(EdgeDriver.java:61)
	at org.openqa.selenium.edge.EdgeDriver.<init>(EdgeDriver.java:57)
	at org.openqa.selenium.edge.EdgeDriver.<init>(EdgeDriver.java:49)
	at org.openqa.selenium.edge.EdgeDriver.<init>(EdgeDriver.java:45)
	at basicweb.MSEdgeDriverDemo.main(MSEdgeDriverDemo.java:12)
Caused by: org.openqa.selenium.WebDriverException: Command failed with code: -1073741701, executed: [--browser, MicrosoftEdge, --output, json, --debug]

Build info: version: '4.16.1', revision: '9b4c83354e'
System info: os.name: 'Windows 11', os.arch: 'amd64', os.version: '10.0', java.version: '17.0.6'
Driver info: driver.version: EdgeDriver
	at org.openqa.selenium.manager.SeleniumManager.runCommand(SeleniumManager.java:157)
	at org.openqa.selenium.manager.SeleniumManager.getDriverPath(SeleniumManager.java:299)
	at org.openqa.selenium.remote.service.DriverFinder.getPath(DriverFinder.java:22)
	... 7 more

joerg1985 · 2023-12-07T19:17:59Z

@diemol I don't think this is related to the other issue, the other issue could not read the json output.
This one can not execute the selenium manager and returns a windows error code why.
-1073741701 is 0xC000007B aka. STATUS_INVALID_IMAGE_FORMAT

joerg1985 · 2023-12-07T19:55:51Z

@letskodeit could you please try to run the C:\Users\aniltomar\.cache\selenium\manager\0.4.16\selenium-manager.exe from the command line and check if it fails?
If not, add the --browser MicrosoftEdge --output json --debug as parameters and check if it is still working.

titusfortner · 2023-12-07T20:52:52Z

@letskodeit yes, using that jar works! I was expecting to see SM logs, but looks like SM didn't even start in the first place.

As with @joerg1985, I'm curious what it shows when you run selenium-manager.exe with those parameters. Thanks.

letskodeit · 2023-12-08T02:31:23Z

@joerg1985 @titusfortner
This is what I see:

joerg1985 · 2023-12-08T04:02:30Z

@bonigarcia is the Visual C++ Redistributable for Visual Studio 2015-2022 mandatory to run a rust binary in windows?

jstefek · 2023-12-08T09:32:04Z

Installed https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022 , did not help, still getting the 0xC000007B.
Also tried running as admin, same result.

nvborisenko · 2023-12-08T09:37:55Z

Windows x86? :)

jstefek · 2023-12-08T09:43:53Z

ic, ok.
I can confirm that installing the x86 version helped.
The manager produces desired output.
And the reproducer also works -- I am able to start Chrome browser and close it.

letskodeit · 2023-12-08T13:57:44Z

C:\Users\aniltomar\.cache\selenium\manager\0.4.16\selenium-manager.exe --browser MicrosoftEdge --output json --debug
Ran command for version Selenium Manager version 0.4.15 without installing Visual C++ Redistributable for Visual Studio 2015-2022 and received the below output:

{
  "logs": [
    {
      "level": "DEBUG",
      "timestamp": 1702043695,
      "message": "msedgedriver not found in PATH"
    },
    {
      "level": "DEBUG",
      "timestamp": 1702043695,
      "message": "MicrosoftEdge detected at C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe"
    },
    {
      "level": "DEBUG",
      "timestamp": 1702043695,
      "message": "Running command: wmic datafile where name='C:\\\\Program Files (x86)\\\\Microsoft\\\\Edge\\\\Application\\\\msedge.exe' get Version /value"
    },
    {
      "level": "DEBUG",
      "timestamp": 1702043695,
      "message": "Output: \"\\r\\r\\n\\r\\r\\nVersion=119.0.2151.97\\r\\r\\n\\r\\r\\n\\r\\r\\n\\r\""
    },
    {
      "level": "DEBUG",
      "timestamp": 1702043695,
      "message": "Detected browser: MicrosoftEdge 119.0.2151.97"
    },
    {
      "level": "DEBUG",
      "timestamp": 1702043695,
      "message": "Reading msedgedriver version from https://msedgedriver.azureedge.net/LATEST_RELEASE_119_WINDOWS"
    },
    {
      "level": "DEBUG",
      "timestamp": 1702043696,
      "message": "Required driver: msedgedriver 119.0.2151.97"
    },
    {
      "level": "DEBUG",
      "timestamp": 1702043696,
      "message": "msedgedriver 119.0.2151.97 already in the cache"
    },
    {
      "level": "INFO",
      "timestamp": 1702043696,
      "message": "Driver path: C:\\Users\\aniltomar\\.cache\\selenium\\msedgedriver\\win-arm64\\119.0.2151.97\\msedgedriver.exe"
    },
    {
      "level": "INFO",
      "timestamp": 1702043696,
      "message": "Browser path: C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe"
    }
  ],
  "result": {
    "code": 0,
    "message": "C:\\Users\\aniltomar\\.cache\\selenium\\msedgedriver\\win-arm64\\119.0.2151.97\\msedgedriver.exe",
    "driver_path": "C:\\Users\\aniltomar\\.cache\\selenium\\msedgedriver\\win-arm64\\119.0.2151.97\\msedgedriver.exe",
    "browser_path": "C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe"
  }
}

Why is it working with version 0.4.15 and not with 0.4.16?

chadlwilson · 2023-12-10T09:43:44Z

Why is it working with version 0.4.15 and not with 0.4.16?

Possibly related to the change in #13134 I guess

As @nvborisenko and @jstefek realised above (but I didn't quite follow initially) , installing VC++ redistributable 14.38.33130 works - but only if you install the x86 version (even on an x64 system or arm64 system).

It looks it's linked to the x86 version (i686 -> x86 -> 32-bit) which is possibly where folks are going wrong installing the runtime, and is probably a less common runtime variant to already be installed on folks' systems for other reasons.

Bit of a shame that the extra hidden runtime dependency is needed (especially to x86 arch), but perhaps there are other considerations here.

letskodeit · 2023-12-10T15:42:05Z

Does it mean 4.15 version doesn't need Visual C++ Redistributable for Visual Studio 2015-2022?

chadlwilson · 2023-12-10T16:05:56Z

Does it mean 4.15 version doesn't need Visual C++ Redistributable for Visual Studio 2015-2022?

As far as I can see, 4.15 does not need the redist - which is why it worked as you posted above?

To build with the Microsoft Visual C++ toolchain as in #13134 and statically link the C runtime so that users don't need to install the redistributable I believe it would require the devs to configure the rust build with something like rustflags = ["-C", "target-feature=+crt-static"] but haven't tried it myself to see if it works, and how much it increases the binary size by. Some discussion is at https://users.rust-lang.org/t/windows-binaries-vcruntime140-dll-not-found-unless-crt-static/94517

letskodeit · 2023-12-10T16:14:29Z

@titusfortner @chadlwilson
Is that a new requirement with version 4.16 listed in changelogs or this is still a bug which needs to be fixed to remove the requirement?

titusfortner · 2023-12-10T23:51:33Z

I think there was a change to how we built for windows in 4.16 to fix a different problem. We need to hear back from @bonigarcia on this one.

bonigarcia · 2023-12-11T11:52:48Z

Sorry for the inconvenience. Installing Visual C++ should not be necessary. It seems the Rust flags -Ctarget-feature=+crt-static are required to avoid the problem related to Visual C++ Redistributable for Visual Studio 2015-2022. In fact, these flags were already available in former versions of Selenium Manager, but they were not in Selenium 4.15 and 4.16.

I created PR #13281 to restore these flags when building Selenium Manager.

If anyone needs the binaries built with that flag, it can be downloaded from here:

https://github.com/SeleniumHQ/selenium/actions/runs/7166910213

letskodeit · 2023-12-11T14:42:42Z

@bonigarcia
Thanks for the clarification. Does it mean, we will have a fix in future versions?

bonigarcia · 2023-12-11T14:45:23Z

Thanks for the clarification. Does it mean, we will have a fix in future versions?

Yes.

titusfortner · 2023-12-11T15:45:51Z

Fixes are in trunk. Thanks.

benken-parasoft · 2023-12-22T20:08:11Z

How soon can we expect 4.17? Or could a selenium-java 4.16.2 be pushed out sooner just to fix this regression?

titusfortner · 2023-12-22T22:52:06Z

You can use nightly if you need. https://www.selenium.dev/downloads/#nightly

benken-parasoft · 2024-01-24T17:51:29Z

You can use nightly if you need. https://www.selenium.dev/downloads/#nightly

I see that 4.17.0 was published with commit for "Restore rust flags" mentioned in the release notes. Thanks!

github-actions · 2024-02-24T00:10:32Z

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

jstefek added I-defect needs-triaging labels Dec 7, 2023

jstefek changed the title ~~[🐛 Bug]: Cannot instantiate ChromeDriver on Windows [java]~~ [🐛 Bug]: Cannot instantiate ChromeDriver on Windows using selenium 4.16 [java] Dec 7, 2023

jstefek changed the title ~~[🐛 Bug]: Cannot instantiate ChromeDriver on Windows using selenium 4.16 [java]~~ [🐛 Bug]: [java] Cannot instantiate ChromeDriver on Windows using selenium 4.16 Dec 7, 2023

titusfortner mentioned this issue Dec 7, 2023

[🐛 Bug]: v4.16.1 Not able to open a browser with NoSuchDriverException #13263

Closed

titusfortner added the I-logging Applied to issues where logging information would help troubleshoot label Dec 7, 2023

chadlwilson mentioned this issue Dec 10, 2023

Rollback selenium-webdriver to 4.15.0 gocd/gocd#12356

Merged

bonigarcia mentioned this issue Dec 11, 2023

[ci] Restore rust flags for build SM in CI #13281

Merged

8 tasks

diemol added C-rust and removed needs-triaging labels Dec 11, 2023

titusfortner closed this as completed Dec 11, 2023

nvborisenko mentioned this issue Dec 15, 2023

[🐛 Bug]: Selenium 4.16.x fails on selenium-manager.exe when vcuntime140.dll is not installed #13312

Closed

joerg1985 mentioned this issue Dec 19, 2023

[🐛 Bug]: After updating from 4.15.0. to 4.16.1. getting "No drivers have been configured or have been found on PATH" but works in 4.15.0 #13295

Closed

dcdraper mentioned this issue Dec 27, 2023

[🐛 Bug]: Selenium 4.15 with C# - Exception in Parallel Test Execution "OpenQA.Selenium.NoSuchDriverException : Unable to obtain chrome using Selenium Manager" #13342

Closed

This was referenced Jan 5, 2024

[🐛 Bug]: selenium-manager(1.60or1.61) in selenium-server-4.16.0.jar is not worked #13396

Closed

[🐛 Bug]: #13403

Closed

github-actions bot locked and limited conversation to collaborators Feb 24, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[🐛 Bug]: [java] Cannot instantiate ChromeDriver on Windows using selenium 4.16 #13261

[🐛 Bug]: [java] Cannot instantiate ChromeDriver on Windows using selenium 4.16 #13261

jstefek commented Dec 7, 2023 •

edited

Loading

github-actions bot commented Dec 7, 2023

diemol commented Dec 7, 2023

github-actions bot commented Dec 7, 2023

letskodeit commented Dec 7, 2023

joerg1985 commented Dec 7, 2023

joerg1985 commented Dec 7, 2023 •

edited

Loading

titusfortner commented Dec 7, 2023

letskodeit commented Dec 8, 2023

joerg1985 commented Dec 8, 2023

jstefek commented Dec 8, 2023

nvborisenko commented Dec 8, 2023

jstefek commented Dec 8, 2023 •

edited

Loading

letskodeit commented Dec 8, 2023 •

edited

Loading

chadlwilson commented Dec 10, 2023

letskodeit commented Dec 10, 2023 •

edited

Loading

chadlwilson commented Dec 10, 2023 •

edited

Loading

letskodeit commented Dec 10, 2023

titusfortner commented Dec 10, 2023

bonigarcia commented Dec 11, 2023

letskodeit commented Dec 11, 2023

bonigarcia commented Dec 11, 2023

titusfortner commented Dec 11, 2023

benken-parasoft commented Dec 22, 2023

titusfortner commented Dec 22, 2023

benken-parasoft commented Jan 24, 2024

github-actions bot commented Feb 24, 2024

[🐛 Bug]: [java] Cannot instantiate ChromeDriver on Windows using selenium 4.16 #13261

[🐛 Bug]: [java] Cannot instantiate ChromeDriver on Windows using selenium 4.16 #13261

Comments

jstefek commented Dec 7, 2023 • edited Loading

What happened?

How can we reproduce the issue?

Relevant log output

Operating System

Selenium version

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

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

Are you using Selenium Grid?

github-actions bot commented Dec 7, 2023

diemol commented Dec 7, 2023

github-actions bot commented Dec 7, 2023

letskodeit commented Dec 7, 2023

joerg1985 commented Dec 7, 2023

joerg1985 commented Dec 7, 2023 • edited Loading

titusfortner commented Dec 7, 2023

letskodeit commented Dec 8, 2023

joerg1985 commented Dec 8, 2023

jstefek commented Dec 8, 2023

nvborisenko commented Dec 8, 2023

jstefek commented Dec 8, 2023 • edited Loading

letskodeit commented Dec 8, 2023 • edited Loading

chadlwilson commented Dec 10, 2023

letskodeit commented Dec 10, 2023 • edited Loading

chadlwilson commented Dec 10, 2023 • edited Loading

letskodeit commented Dec 10, 2023

titusfortner commented Dec 10, 2023

bonigarcia commented Dec 11, 2023

letskodeit commented Dec 11, 2023

bonigarcia commented Dec 11, 2023

titusfortner commented Dec 11, 2023

benken-parasoft commented Dec 22, 2023

titusfortner commented Dec 22, 2023

benken-parasoft commented Jan 24, 2024

github-actions bot commented Feb 24, 2024

jstefek commented Dec 7, 2023 •

edited

Loading

joerg1985 commented Dec 7, 2023 •

edited

Loading

jstefek commented Dec 8, 2023 •

edited

Loading

letskodeit commented Dec 8, 2023 •

edited

Loading

letskodeit commented Dec 10, 2023 •

edited

Loading

chadlwilson commented Dec 10, 2023 •

edited

Loading