Jump to content

Erlend

Members
  • Posts

    36
  • Joined

  • Last visited

Posts posted by Erlend

  1. 8 minutes ago, Marcos said:

    There are no such known issues. Does temporarily disabling real-time protection in the advanced setup and/or disabling HIPS and rebooting the server make a difference?  If not, try temporarily uninstalling EFSW to make sure that it actually resolves the issue; otherwise you'll need to look for the root cause elsewhere. If you confirm that EFSW is somehow causing the issue, please open a support ticket with your local ESET distributor and provide your findings as well as logs collected with ESET Log Collector for a start.

    A complete memory dump from the freeze will be most likely needed to determine the cause.

    local support have always been slooooow, and eset log collector won't help, since it's non persistent. 

  2. Hi

    anyone else encountered this being reported as infected?

    triggered during windows update.

     

    Time;Scanner;Object type;Object;Detection;Action;User;Information;Hash;First seen here

    26.01.2021 14.53.10;Real-time file system protection;file;C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Host.win-x64\5.0.2\runtimes\win-x64\native\apphost.exe;Win64/Patched.U trojan;deleted;NT AUTHORITY\SYSTEM;Event occurred on a new file created by the application: C:\Windows\System32\msiexec.exe (9D336636A328D5B3F315093D86E4199A0FD7A5FC).;0DBB86B65FBBB41660DF36ABA0CED8FA4048FD7F;12.12.2020 03.44.18

    26.01.2021 14.53.20;Real-time file system protection;file;C:\Program Files\dotnet\sdk\5.0.102\AppHostTemplate\apphost.exe;Win64/Patched.U trojan;deleted;NT AUTHORITY\SYSTEM;Event occurred on a new file created by the application: C:\Windows\System32\msiexec.exe (9D336636A328D5B3F315093D86E4199A0FD7A5FC).;0DBB86B65FBBB41660DF36ABA0CED8FA4048FD7F;12.12.2020 03.44.18

×
×
  • Create New...