Home > Article > Backend Development > Why Does Chrome v87 Cause 'Failed to read descriptor from node connection' Error After Windows 10 Update?
Chrome v87 USB Device Error upon Update
In recent updates to Windows 10, ChromeDriver v87, and Chrome v87, users may encounter an error message indicating "Failed to read descriptor from node connection: A device attached to the system is not functioning."
This error appears in the console upon running minimal Selenium code, hindering test execution. Could this be an issue specific to ChromeDriver/Chrome v87 or a compatibility concern?
Suppressing Error Logs
While the error doesn't affect functional operation, it can be distracting on the console. Fortunately, this error can be suppressed using a simple "hack."
By adding the following argument to the ChromeOptions via add_experimental_option(), the error messages will be excluded from the console:
options.add_experimental_option('excludeSwitches', ['enable-logging'])
With this modification, the updated code block becomes:
from selenium import webdriver options = webdriver.ChromeOptions() options.add_argument("start-maximized") options.add_experimental_option('excludeSwitches', ['enable-logging']) driver = webdriver.Chrome(options=options, executable_path=r'C:\WebDrivers\chromedriver.exe') driver.get('https://www.google.com/')
This solution will effectively hide the error messages, allowing for uninterrupted test execution.
The above is the detailed content of Why Does Chrome v87 Cause 'Failed to read descriptor from node connection' Error After Windows 10 Update?. For more information, please follow other related articles on the PHP Chinese website!