[🐛 Bug]: Error using user-data-dir= in Chrome 103.0.5060.53

What happened?

When using chrome_options.add_argument(‘user-data-dir=’ in Chrome 103 the error occurs:

Selenium.common.exceptions.WebDriverException: Message: unknown error: unexpected command response (Session info: chrome=103.0.5060.53)

if I remove this parameter, it works.

How can we reproduce the issue?

from selenium import webdriver
from selenium.webdriver.chrome.service import Service

chrome_options = webdriver.ChromeOptions()
chrome_options.add_argument('user-data-dir=C:\\Perfil')

driver_path = 'chromedriver.exe'
service = Service(driver_path)
driver = webdriver.Chrome(service=service,options=chrome_options)

driver.get("https://google.com")

Relevant log output

elenium.common.exceptions.WebDriverException: Message: unknown error: unexpected command response
  (Session info: chrome=103.0.5060.53)
Stacktrace:
Backtrace:
	Ordinal0 [0x007E6463+2188387]
	Ordinal0 [0x0077E461+1762401]
	Ordinal0 [0x00693D78+802168]
	Ordinal0 [0x00687210+750096]
	Ordinal0 [0x0068675A+747354]
	Ordinal0 [0x00685D3F+744767]
	Ordinal0 [0x0068557C+742780]
	Ordinal0 [0x00699BF3+826355]
	Ordinal0 [0x006ECF6D+1167213]
	Ordinal0 [0x006DC5F6+1099254]
	Ordinal0 [0x006B6BE0+945120]
	Ordinal0 [0x006B7AD6+948950]
	GetHandleVerifier [0x00A871F2+2712546]
	GetHandleVerifier [0x00A7886D+2652765]
	GetHandleVerifier [0x0087002A+520730]
	GetHandleVerifier [0x0086EE06+516086]
	Ordinal0 [0x0078468B+1787531]
	Ordinal0 [0x00788E88+1805960]
	Ordinal0 [0x00788F75+1806197]
	Ordinal0 [0x00791DF1+1842673]
	BaseThreadInitThunk [0x75F7FA29+25]
	RtlGetAppContainerNamedObjectPath [0x77987A9E+286]
	RtlGetAppContainerNamedObjectPath [0x77987A6E+238]

Operating System

Windows 10 and Manjaro

Selenium version

Python (Selenium 4)

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

Chrome 103

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

ChromeDriver 103.0.5060.53

Are you using Selenium Grid?

No response

[dianis55]

+ Having a same problem now

[diemol]

Folks, posting “I have the same issue” does not help much, we cannot do anything because this is a Chrome issue. Please add yourself as a watcher to https://bugs.chromium.org/p/chromedriver/issues/detail?id=4121