[Secure Browser not starting in Chrome, but works fine in Edge and Firefox]

24 minutes ago, Marcos said:

You can work around it by enabling "Secure all browsers" in the advanced setup or wait until the BPP module that adds support for the latest version of Chrome updates automatically.

Endpoint security does not have the option "Secure all browsers". Do we know when the BPP module will be updated automatically, since the chrome version was released two weeks before the endpoint release? 

[Secure Browser not starting in Chrome, but works fine in Edge and Firefox]

Product Version: 9.0.2032.2

Chrome: Version 96.0.4664.93 (Official Build) (64-bit) (Default Browser)

Windows 10 19044.1348 all updates installed

Even though in all other browsers, Eset Secure Browser pops up smoothly, when accessing a webpage via Chrome, the Secure Browser does not pop up. 

[Browsing Applications not open after install ERA 6.5 Latest Build]

Unfortunately, since i switched to the previous version i cannot generate a new memory dump. The CrashDumpEnabled was enabled to record only the kernel memory and as result sending you the current dmp will not help you at all.

The rules that have been created automatically in learning mode are approximately 87.

I will test another client pc as soon as possible and i will inform you.

[Browsing Applications not open after install ERA 6.5 Latest Build]

The same thing happened to two clients running Windows 10 (x64) in my company, that i tested the new version. However era and agent update was fluent. 

The one was in Automatic Mode and the other was in Policy Based Mode. Turning the second in Automatic solved the issue however when added a new pc user account the same happened even it was already in automatic mode.

Disabling the HIPS didn't help

Had to turn off the firewall and restart. As a result i switched them both to the previous version.