Your request for Endpoint Protector was sent!
One of our representatives will contact you shortly to schedule a demo.
Free, custom demo to suit your needs
One of our representatives will contact you shortly to schedule a live demo. We'll answer questions, address your concerns and tailor the demo to your needs.



* We don't share your personal info with anyone.
Check out our Privacy Policy for more information.
Please use a valid email address!
Thousands of global clients
already use our product
Trusted by companies of all sizes, from all industries. Fortune 500 companies, Universities, Governments, Banks, Media, and more.
Join them
Trusted by companies of all sizes, from all industries. Fortune 500 companies, Universities, Governments, Banks, Media, and more.
Endpoint Protector Knowledge Base

Below you can explore FAQs related to Endpoint Protector and find the information you need. For any other additional questions, suggestions, and improvements please contact the support team.

Why are my users experiencing browser issues on endpoints where the Endpoint Protector Client is installed?

This issue applies to endpoints with Endpoint Protector Clients, when using some of the latest versions of browsers such as Edge, Chrome or Mozilla Firefox.

Endpoint Protector offers sensitive content capabilities, by inspecting file transfers through various exist points such as browsers or other applications. In the middle of 2019, most browsers have introduced various security restrictions to restrict 3rd party interaction. As such, this can result in browsers displaying messages like Aw Snap! Something went wrong while displaying this webpage."
Note: The above scenario may occur also due to other security products like AV or other DLP solutions.

There are several options available to mitigate the above scenario:

1. Install an Endpoint Protector Client. This will be included within the Endpoint Protector Server 5.2.0.7. In the meantime, you can request it by contacting Support.

2. Change the browser settings to allow trusted 3rd party applications.
  • For Mozilla Firefox, simply change the “security.fileuri.strict_origin_policy” from “true” to “false”. The steps to do so are similar to the ones described in this FAQ.
  • For Chrome, simply run the with Code Integrity disabled
    Chrome.exe –disable-features=RendererCodeIntegrity
    or set the regkey to 0 (recommended for environments using AD)
    Key: HKLM\Software\Policies\Google\Chrome
    Name: RendererCodeIntegrityEnabled
    Type: DWORD (32-bit)
    Value: 0
Was this article helpful?
YES NO
Can you please tell us how we can improve this article.
Thank you for your feedback!