Jump to content

Secure Browser Couldn't Be Started


Recommended Posts

Win 10 x(64) 1909, FireFox x(64) 74.0, EIS 13.1.16 pre-release updates.

This just started today, The funny part is BP&P opens fine as far as I can determine:

Eset_BPP.thumb.png.48b47520be0ac7d303bcc8b058cdd530.png

Eset_BPP_2.thumb.png.f451bdaf9478cdd2672228b4abc9ef7b.png

Edited by itman
Link to comment
Share on other sites

  • ESET Insiders

Win 10x64 1909, pre release updates
B&PP module 1181

This error seems to trigger when the secured browser closes. It's only been occurring since the module update to 1181.

BTW Anyone got a secured browser working with Edge Chromium?

 

Link to comment
Share on other sites

18 hours ago, stackz said:

This error seems to trigger when the secured browser closes. It's only been occurring since the module update to 1181.

Confirmed this is the case. Also module 1181 has a date of 3/31/2020. Question is if this is just a pre-release updates issue?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...