Jump to content

st3fan

Members
  • Content Count

    3
  • Joined

  • Last visited

Profile Information

  • Location
    South Africa
  1. Thanks for the prompt reply Marcos. Does this mean that all future ESET updates will require a reboot?
  2. 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
  3. 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 repor
×
×
  • Create New...