- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
01-16-2026 03:35 AM
Hello guys,
I have very strange problem, every time i try to start web application connection i receive error that it cannot find the chromiumdriver in DriverFolder path. The error in the PSM is PSMDU018E Dispatcher error: [HTMLPageController :: OpenWebBrowser -> Validate that chromedriver.exe is located under C:\Program Files (x86)\CyberArk\PSM\Components. My DriverFolder path is exactly that one, and the chromium driver is there, but cannot understand why it cannot find it. I implement Web Driver to be updated automatically every hour and the version is the same as it is the chrome browser itself - 144.0.7559. The PSM is hardened and the configuration is with UpdateApplocker.ps1 script in the configuration (even tried without that option). Nothing works. Someone with ideas?
Greetings!
01-16-2026 05:23 AM
@Anton Etimov You might have to perform the validatin of chrome version and driver version manully to confirm all looks same. Re-reun the applocker and validate
01-16-2026 05:23 AM
@Anton Etimov You might have to perform the validatin of chrome version and driver version manully to confirm all looks same. Re-reun the applocker and validate
01-16-2026 05:27 AM
I have validated the versions through the Command prompt and the 2 versions match. The logs in the WebDriver autmatic update are good too:
C:\Windows\system32>wmic datafile where name="C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe" get Version
Version
144.0.7559.60
C:\Windows\system32>cd "C:\Program Files (x86)\CyberArk\PSM\Components"
C:\Program Files (x86)\CyberArk\PSM\Components>chromeDriver -v
ChromeDriver 144.0.7559.31 (18537d992890dc68b11c8a4f748cad3c7df165c4-refs/branch-heads/7559@{#1444})
The major version match.
01-16-2026 09:43 AM
Just to clarify, when you say you "even tried without that option" at the end there - do you mean you already tried to put AppLocker in Audit Only mode and then test to eliminate AppLocker being the culprit?
Additionally, has this worked previously in the environment?
01-19-2026 03:35 AM
What version of PSM are you one? If 14.6 or later it might be the same problem we had; the change to 64-bit WebAppDispatcher infrastructure which involves a new folder path for 64-bit Connector files which now includes Web App and is now the default for existing OOTB and newly created We App Connectors. Web applications for PSM | CyberArk Docs
You might have to install the web driver(s) at the new folder location *\CyberArk\PSM\Components\x64 and also update the WebDriverUpdater utility to update driver in the new path as well as old. We found the same error in the PSM log to be misleading, even though it was complaining about driver being missing from the old path of *\CyberArk\PSM\Components it was actually missing from the new path of *\CyberArk\PSM\Components\x64. When we copied the web driver to the new location it started working.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

