Jump to content

AssVas

Members
  • Posts

    2
  • Joined

  • Last visited

About AssVas

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Greece
  1. Good afternoon all, To fellow IT personnel fighters out there, Confirming it started with one of our office users severe impacting his laptop at 13th July, most of the users received the update yesterday and massively compalined. Launching Outlook in Safe mode seemed to fix the issue. A colleague of mine came upon this topic thankfully for me saving hours of further troubleshooting with MS. As per above dont think its a good idea to disable any of the EMAIL to SCAN , but nevertheless proceed with disabling the Advanced email client processing , as it has a relative self-explanatory and further monitor. To Eset support, The detection of the exact cause is a matter of hours. Please coordinate with your dev teams and check the change log of the latest update pushed to ESET clients and if feasible clarify to us an estimated date rolling out another update to fix this, as for us to know how to handle this and if below switch found in ESET AV -> Advanced Setup -> Advanced email client processing , does the trick . We are hurt but still love you ❤️ Regards, V.T
  2. I 've had the same error, using a compiled installed from ESET CP to install Agent/AV . Found an anorthodox solution as per below : 1. Begin installation 2. On final step before proceeding to installing the agent/AV , navigate to temporary folder where the *.msi installer files are extracted and copy them to another location. For Agent : C:\Users\YourWindowsUserProfileName\AppData\Local\Temp\eset\bts.session\{02D83BBE-F7F7-F7A4-EF84-xxxxxxxxxx}\.pkg\0\ For Antivirus Endpoint : C:\Users\YourWindowsUserProfileName\AppData\Local\Temp\eset\bts.session\{02D83BBE-F7F7-F7A4-EF84-xxxxxxxxxx}\.pkg\1\ 3. Then abort installation 4. Proceed manualy to install agent and endpoint 5. Completed succesfully.
×
×
  • Create New...