[🐛 Bug]: [dotnet] Chrome browser may not initialize if chromedriver file path is not specified

[PCG-MMast]

Description

Recently upgraded from selenium 3.141.0 to 4.29.0.

1. When creating a new ChromeDriver object, Chrome does not open.
2. When calling any action on the newly initialized driver object, an error is thrown (error differs based on the method called)
3. Why: when the user has a separate chromedriver executable in a different file location on their computer, there is a chance that the underlying selenium manager service (selenium-manager.exe) will find that executable and its file path instead of the latest installed one in the project/solution. If that executable is very old, the driver will not be compatible with newer versions of chrome. In my case, the other chromedriver executable was in C:\Program Files (x86)\SomeThirdPartyFolderAndSubfolders

Reproducible Code

// driver instance is returned, but the Capabilities property contains errors and the 
// chromedriver filepath is not the expected file path
var driver = new ChromeDriver();

// Throws an error message similar to: The setWindowRect command returned an unexpected error. unknown command
// This error is a red herring. The issue is that the driver object was not initialized correctly
driver.Manage().Window.Position = new Point(0, 0);

---

ℹ️ Last known working version: 3.141.0

[titusfortner]

@PCG-MMast, 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 J-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]

⚠️ You reported using Selenium version 4.29.0, but the latest release is 4.30.

Please verify that this issue still occurs with the latest version. If it no longer applies, you can close this issue or update your comment.

This issue will be marked "awaiting answer" and may be closed automatically if no response is received.

[PCG-MMast]

We are using latest Appium 7.2.0 which uses Selenium.WebDriver 4.29.0 as of submitting this

[titusfortner]

We're still working out the kinks in our fancy new Issue automation process.

[titusfortner]

Selenium Manager will only use the old version of the driver if the location of that driver is included in the PATH environment variable. This is as intended. Remove the folder from PATH, or specify the location you want used with an Environment Variable. You can turn on logging to see exactly what Selenium Manager is doing, I'll include the link for that below...