Jump to content

st3fan

Members
  • Posts

    6
  • Joined

  • Last visited

About st3fan

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    South Africa
  1. Yes I did. It is just as bad unfortunately.
  2. Thanks for your reply Marcos. Yep, that's what we did a few years ago when we first encountered this problem. We spent a lot of time on troubleshooting with Support but in the end we had to disable this setting. Pity this is still a problem after all these years.
  3. Hi everyone We have had issues with the ESET addin and Outlook 2016 (but also with Outlook 2010, 2013...) for many years. Outlook often freezes when emails and attachments are opened, especially emails from shared mailboxes. What made a huge difference and fixed the problem for us: we disabled the scanning of "Read email" in "Web and Email - Email client protection". We only disabled the scanning of read email - sent/received emails are still scanned without causing any issues. Currently we are on Endpoint Antivirus 7.3.2041.0 and 8.0.2028.0. This morning I disabled the above policy for testing purposes as I wanted to see if things have improved in the interim. Outlook stopped responding almost immediately, so it seems scanning of read emails is still not working well. The are a few posts on this topic, so I a assume this is (still?) a common issue. How is everyone else handling this? Is disabling this setting still the way to go? Thank you. Regards, Stefan
  4. Thanks for the prompt reply Marcos. Does this mean that all future ESET updates will require a reboot?
  5. Hi everyone We just finished updating to 7.3.2044.0 which was a nightmare due to the required reboot. What a mission to plan this with all our users. And now I noticed that 8.0.2028.0 has been released and I am seeing the same "computer restart will be required" message. I can't believe this anymore. Why is this a requirement all of the sudden? Updating ESET was seamless in the past and we never had to bother our users. This has become a logistical nightmare for us. How is everyone else handling this? And does anyone know if this is the new norm now? Thanks, Stefan
  6. We have exactly the same issue (EFSW 7.1.12006 and 7.1.12008 on Server 2016). We contacted ESET Support a long time ago but they were unable to help. Installing EFSW without network protection makes a bit of a difference, however, in order to get the full performance, we would have to remove EFSW completely. This problem does not occur with Windows Defender or other AV-solutions. Does anyone here have any further information or advice how to proceed? We would like to make use of network protection and get the full performance. I will test the pre-release update channel and will report back in the interim.
×
×
  • Create New...