- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
02-05-2026 12:33 PM
When launching Web apps, we receive an error message:
Session has been closed
Login failed
Failed to initialize web browser. Driver was not found.
Validate that the Selenium driver of the selected browser is
located under 'DriverFolder'.
I have followed all instructions here: How to download or update browser (Chrome\Edge) driver to validate the drivers and AppLocker. I have also tested with Applocker in Audit mode and with manually installing the drivers. My "DriverFolder" is set to C:\Program Files (x86)\CyberArk\PSM\Components. The "BrowserPath" is set to C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe.
What am I missing here? Thanks!
03-02-2026 07:24 AM
Hi Everyone,
I just fixed this with CyberArk support. The issue was that lines needed to be added to the PSMApplockerConfigure.xml file for both the regular and x64 versions of the driver. Even though we are using Edge, it was adding the lines for Chrome that fixed it: <Application Name="Chromedriver" Type="Exe" Path="C:\Program Files (x86)\CyberArk\PSM\Components\chromedriver.exe" Method="Path" /> and <Application Name="Chromedriver" Type="Exe" Path="C:\Program Files (x86)\CyberArk\PSM\Components\x64\chromedriver.exe" Method="Path" />. Thanks for all of the help!
02-05-2026 01:07 PM
Hey @Mikel Seidl The DriverFolder parameter isn't needed, unless you're specifically trying to use a 32bit vs. 64bit, etc. There are some differences if you're on 14.6+ I recommend removing it to ensure the correct Secure Web App Framework is leveraged:
https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/psm_webapplication.htm
You can also make sure msedgedriver.exe version matches the msedge.exe version (i.e. 144.0.3719.x) as close as possible.
02-05-2026 01:28 PM
Thanks! I just removed that Parameter from the web application and the same error persists. Edge is fully up to date and the most recent version of the msedgedriver is installed. Any other suggestions to try?
02-05-2026 03:57 PM
Hello,
You should both add 32 bit and 64 bit driver. 64 bit in psm/component/x64 and 32 bit in psm/components and make sure both 32 and 63 bit dispatchers are updated.
02-06-2026 06:15 AM
Did you add the path to driver folder in applocker policy ? Also try to rerun applocker scrip and configure Applocker for Audit only mode.
02-06-2026 09:26 AM
Under Target settings of the CC make sure you have Edge under ClientApp. If using Edge by default its Chrome
02-06-2026 09:49 AM
Where do we set this? I don't have these settings in the app config. My CC setup is attached.
02-06-2026 10:28 AM
In addition to other comments.
The title says web apps indicating it is occurring with any web app you have attempted to configure.
Is $Support_Web_Applications set to True in the hardening xml? It needs to be set to True. Reference - https://docs.cyberark.com/pam-self-hosted/14.2/en/content/pas%20inst/install_configurepsmservermachineforwebapps.htm
Newly installed environments may require activating the setting in the Master Policy for Session Monitoring and Isolation.
02-06-2026 11:07 AM
Not here
Configuration > Options > Connection Components
Also duplicate the sample onel, rename it and build urs
02-11-2026 02:29 AM
Hi @Mikel Seidl
Several community members have shared answers to your question. Could you let us know if any of these resolved your issue?
If so, please mark the appropriate answer as “Select as Best” to help other members find the solution easily.
If the issue remains unresolved, I recommend submitting a ticket with our support team for further assistance.
Thank you,
Shaked
02-11-2026 06:35 AM
Thanks for the responses everyone! I have tried all of the above without success. Our Web apps still don't open. I just escalated to CyberArk support to find the fix.
02-18-2026 02:34 AM
Hi,
this solution worked for me
https://community.cyberark.com/s/question/0D5Vy00001qKwA8KAK/its-a-information-if-you-are-getting-error-as-below-if-you-upgraded-to-146-failed-to-initialize-web-browser-driver-was-not-found-validate-that-the-selenium-driver-of-the-selected-browser-is-locted-under-driverfolderfollow-below-steps
I added chromedriver.exe into components\x64 folder and added extra line with this path for chromedriver.exe into Applocker xml and rerun the PSMConfigureApplocker script.
02-23-2026 07:50 AM
Hey, Can you share what have helped you fixed the issue with help of cya support ?
I am facing the similar issue after upgrading from 14.4 to 15.0
02-24-2026 05:36 AM
Hi MSeidl,
I've read the entire thread and the excellent suggestions you've already tried (removing DriverFolder, checking the location of 32/64-bit drivers, AppLocker, and making sure ClientApp is set to "Edge"). Since none of these resolved the "Driver not found" error, there's a critical configuration you shouldn't overlook.
As @Donovan Demshock pointed out, you must explicitly enable web application support in the PSM's hardening configuration.
Locate the Hardening XML file on your PSM server: C:\Program Files (x86)\CyberArk\PSM\Hardening
Open the main hardening XML file
Find the parameter $Support_Web_Applications.
It might be set to False by default.
Change its value to True:
$SUPPORT_WEB_APPLICATIONS = $true
Re-apply the hardening policy by running the hardening script again (usually PSM_Hardening.ps1 or Run the PSMHardening.ps1 script with the -supportWebApplication option) or rebooting the server if required by your organization's process.
The $Support_Web_Applications setting ensures the necessary Windows features and permissions are configured for the PSM shadow user to interact with the browser and its driver. Without it, even with all files in the right place, the PSM session cannot launch the web driver, leading to the exact error you're seeing: "Driver was not found".
(this link https://docs.cyberark.com/pam-self-hosted/latest/en/content/pas%20inst/install_configurepsmservermachineforwebapps.htm )
02-26-2026 05:32 AM
Hi! How are you?
Check if the x64 folder has appeared inside the PSM components folder starting with this version.
If it has appeared, you need to place the edgedriver and/or chromedriver there as well.
I encountered the same issue, I hope it works for you!
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!

