Jump to content

Marcos

Administrators
  • Posts

    36,830
  • Joined

  • Last visited

  • Days Won

    1,463

Posts posted by Marcos

  1. Since we were unable to reproduce the issue, would it be possible for you to prepare an image of the system for us on which the issue manifests so that we could debug it?

    Disabling HIPS completely is a bad idea since it also disables crucial protection modules such as Advanced memory scanner, Exploit Blocker and Ransomware shield. If inevitable, disable just self-defense temporarily.

  2. 9 hours ago, Morris B said:

    Is it possible to push disabling this HIPS setting to all of the servers running EFS 7.0.12014.0 and higher from ERAS 6.5?  (Upgrading to ESMC 7.x is on my list of projects to do soon.) 

    Or has this issue been fixed in 7.012016.0 or 7.012018.0? 

    Again, this is not an issue of ESET but Microsoft. There's nothing we could fix in this regard on our part. We've been waiting for Microsoft to come up with a fix.

  3. No problems here. I've also tried a full update and update files with the total size of 144 MB were downloaded withing 30 seconds and the subsequent update process finished alright.

    Should the problem persist:
    - enable advanced update engine and network protection logging
    - reproduce the update error
    - disable logging
    - gather logs with ELC.

  4. Please enable advanced operating system logging in the advanced setup -> Tools -> Diagnostics. Then reproduce the problem, disable logging and provide us with the etl log generated in C:\ProgramData\ESET\ESET Security\Diagnostics in a compressed form.

    Do not leave the logging enabled for longer than 1-2 minutes. Should it take longer to reproduce the problem, we'll provide you with further instructions.

  5. 17 minutes ago, Camilo Diaz said:

    Thanks Marcos. When you said "it's possible to disable protected service", do you mean to  disable 'Automatic exclusions to generate" for Microsoft SQL Server?

    I meant "Protected service" in the HIPS setup. Personally I wouldn't trade protection for convenience and would rather ignore the error until Microsoft fixes the issue.

×
×
  • Create New...