WebDriverManager for .Net - DriverManager + VersionResolveStrategy.MatchingBrowser throws a System.IO.FileNotFoundException

[belugui]

WebDriverManager for .Net - DriverManager + VersionResolveStrategy.MatchingBrowser throws a System.IO.FileNotFoundException

[rosolko]

Is this path valid C:\Users\xxxxx\AppData\Local\Chromium\Application\chrome.exe and chrome really exists there?
For first it's really strange that you're trying to communicate with chrome but file path points to chromium

[andriusrbsy]

I encountered a similar error on my Windows machine. The issue was that my registry key "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe" was pointing to an outdated version of Chrome installed at "C:\Users\andrius.ramanauskas\AppData\Local\Chromium\Application\chrome.exe" (version 79.0.3918.0), which likely came pre-installed on my PC.

However, my actual Chrome browser is located at "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe", and the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe" correctly points to this location.

Deleting the "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe" registry key resolved the issue, and DriverManager started working normally.