Jump to content

April 12 Windows Updates causing issues with ESET

Go to solution Solved by itman,

Recommended Posts

  • Solution

The issue was resolved yesterday morning: https://forum.eset.com/topic/32063-ff-edge-bpp-cannot-be-opened-error-code-0x847695d2/

It is a "poster child" example though that when B&PP secure all browsers setting is enabled and something get's borked in B&PP, your browser also gets also borked.

Link to comment
Share on other sites

Posted (edited)

Thanks itman.  Didn't know the acronym B&PP (had to look it up).  "Banking & Payment Protection" - which doesn't exist in NOD32.

Edited by MarcFL
Link to comment
Share on other sites

  • Administrators

The issue was caused by a coincidence when the trust to certain Microsoft files signed with a specific MS certificate which was used on a malicious file was lost and the fact that certain recently updated dlls had not become popular enough yet. These dlls are now trusted which resolved the issue.

Users who had the Secure all browsers (SAB) option enabled could not start the browser since loading of the untrusted dll was blocked. Those with SAB disabled could use the browser and only redirection to a secured browser was failing. Users with products without Banking and payment protection (ie. ESET NOD32 Antivirus, ESET Endpoint Antivirus) were not affected.

Link to comment
Share on other sites

This topic is now closed to further replies.

  • Recently Browsing   0 members

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