Chromedriver fails to start new Chrome window if Chrome is already open on Windows 11

[Matt Campbell]

Hello!

I maintain an automated test suite that uses Selenium, Chrome, and Chromedriver to test our application in the browser.

As of yesterday, chromedriver has been unable to start a new chrome window if I already have a chrome window open. If I close my personal chrome window and try to run the tests, chromedriver has no issue. It opens chrome and the tests execute.

I've tried starting chrome with the --remote-debugging-pipe and --remote-debugging-port flags but the behavior didn't change.

Here is the chromedriver logs with the --remote-debugging-pipe flag:

[1765312527.493][DEBUG]: DevTools WebSocket Command: Browser.getVersion (id=1) (session_id=) browser {
}
[1765312587.507][SEVERE]: Timed out receiving message from renderer: 60.000
[1765312587.507][DEBUG]: Failed to obtain browser info: timeout: Timed out receiving message from renderer: 60.000
[1765312587.507][DEBUG]: Connection terminated while reading from pipe
[1765312587.509][INFO]: [7455ed13b465b571da33a7526e296012] RESPONSE InitSession ERROR session not created: Chrome failed to start: crashed.
  (timeout: Timed out receiving message from renderer: 60.000)
  (The process started from chrome location <chrome-path>\chrome.exe is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
[1765312587.509][DEBUG]: Log type 'driver' lost 1 entries on destruction
[1765312587.509][DEBUG]: Log type 'browser' lost 0 entries on destruction

Here is the chromedriver log with the --remote-debugging-port=0 flag:
[1765314202.807][INFO]: Launching chrome: "<chrome-path>\chrome.exe" --allow-pre-commit-input --disable-background-networking --disable-backgrounding-occluded-windows --disable-client-side-phishing-detection --disable-default-apps --disable-dev-shm-usage --disable-features=IgnoreDuplicateNavs,Prewarm --disable-hang-monitor --disable-popup-blocking --disable-prompt-on-repost --disable-sync --enable-automation --enable-logging=stderr --log-level=0 --no-first-run --no-sandbox --no-service-autorun --password-store=basic --remote-debugging-port=0 --start-maximized --test-type=webdriver --use-mock-keychain --user-data-dir="<app-data-path>\Temp\scoped_dir13556_284644129" --window-size=1920,1080 data:,
[1765314203.130][INFO]: [49cd9a5362600192f7c8116a6c15698a] RESPONSE InitSession ERROR session not created: Chrome failed to start: crashed.
  (session not created: DevToolsActivePort file doesn't exist)
  (The process started from chrome location <chrome_path>/chrome.exe is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
[1765314203.130][DEBUG]: Log type 'driver' lost 0 entries on destruction
[1765314203.130][DEBUG]: Log type 'browser' lost 0 entries on destruction

I would like to be able to keep my personal chrome window open while running the automated tests. Any advice on what to do?

Chromedriver version: 143.0.7499.4000
Chrome version:  143.0.7499.41