- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-03-2026 06:28 AM
Hi all,
It seems that the Chrome web-based connection not working with EnableTrace=No after Chrome is updated to version 151. Does anyone experience the same issue?
The web-based connection is working with EnableTrace=Yes. However, this is not ideal for production situation. Referring to this article: https://community.cyberark.com/s/article/KI00023857, it seems that a new version of WebAppDispatcher is needed.
08-03-2026 11:31 PM
Did you try adding MinimizeBrowserWhenLoading = No under Target Settings > Client Specific (same place as EnableTrace) ?
Also make sure you have the latest version of the WebAppDispatcher and the ChromeDriver that corresponds to the version of the installed Chrome browser
Finally re-run the applocker script if anything was updated.
08-03-2026 11:31 PM
Did you try adding MinimizeBrowserWhenLoading = No under Target Settings > Client Specific (same place as EnableTrace) ?
Also make sure you have the latest version of the WebAppDispatcher and the ChromeDriver that corresponds to the version of the installed Chrome browser
Finally re-run the applocker script if anything was updated.
08-04-2026 01:18 AM
Hi Pierre-Yves, thanks for your response.
The combination of installing the latest WebAppDispatcher version (v20.2.4.31) and adding MinimizeBrowserWhenLoading = No in the connection components seems to work. The drawback is that the screen blinks a bit in the beginning.
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!

