Jump to content

Marcos

Administrators
  • Posts

    36,334
  • Joined

  • Last visited

  • Days Won

    1,445

Posts posted by Marcos

  1. 14 minutes ago, lagunero said:

    11.2.63.0 just right installed. The problem is still here, at least for me.

    It must be a different issue since the problem with freezing of debuggers was resolved in v11.2.63. Please provide ELC logs. Also generate a complete memory dump during the freeze as per the instructions at https://support.eset.com/kb380. When done, compress it, upload it to a safe location and drop me a message with a download link.

  2. Google will ultimately block injection for 3rd party software (including antivirus programs, no matter whether it's ESET or another one). You should also understand that the fact that ESET or another application is reported as incompatible doesn't mean that it is actually incompatible according to a developer of Chrome quoted in the above mentioned article:

    Quote

    Since it is effectively impossible for Chrome to automatically determine whether any particular piece of software is innocently injecting or purposefully injecting and interfering with Chrome code. To keep things simple we warn about all injected software, without making value judgments. Note that soon we will actually start blocking software from injecting, at which point this warning will cease to show.

    Vendors are gradually removing or limiting support for Chrome due to the restrictions as per https://www.bleepingcomputer.com/news/google/bitdefender-disables-anti-exploit-monitoring-in-chrome-after-google-policy-change/.

  3. What about other https websites? Are you able to open them on the troublesome machine?

    Let's try the following:
    - disable SSL/TLS filtering
    - reboot the machine
    - without launching any browser or app, re-enable SSL/TLS filtering
    - launch a browser and try to reproduce the issue.

    Let us know if the issue is resolved.

  4. In the screen shot I only see that self-defense prevented system processes from performing certain operations with ESET's processes. There doesn't appear to be a record that ESET blocked its own gui.

    I would strongly recommend disabling logging of blocked operations in the advanced HIPS setup to avoid performance issues and wasting disk space by generating big HIPS logs.

×
×
  • Create New...