Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Erlend

  1. 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.
  2. unassigned the default policy File Security for Windows Server - HTTP Proxy Usage now. i will report back how it goes after a few days.
  3. it's set in the default policy: File Security for Windows Server - HTTP Proxy Usage
  4. hm, yes i see that now it's configure to connect via the ESET management server.
  5. Hi again @Marcos, we see both activation errors and live grid communication errors at random how can we figure out what the issues is?
  6. Hi what's the hostnames for ESET LiveGrid and ESET License servers?
  7. what do i need to include in ESET Log Collector?, don't won't to upload any unnecessary information here.
  8. the servers are connected directly not via proxy the issues seems to be intermittent, sometimes it's ok if i check for updates 5 times one of them can be ok are there any logs i can check on the client, to see what source is used for updates?
  9. Hi any know issues with updates at the moment?
  10. @Marcos same issue, i have sendt the license details in a private message.
  11. one more thing, do you have a internal system to make local support in different countries aware of these kind of issues? i contacted ESET support in Norway, and they needed to check and get back to me.
  12. no, both ESET shell and GUI is non-responsive (not able to start them), but i can access the file system remotely on the affected servers. is the module a separate dll file?, that i can check the version on?
  13. is there a way to kill the update process and ESET? to avoid reboot.
  14. after a reboot it probably sort's itself out, i have only one server that needed a second reboot before the issue was resolved.
  15. it's also affecting servers without the RDS session host role installed, we are in the process of identifying all of them. is there a way to kill the stuck update/eset without doing a reboot?
  16. can i check this directly from the file system remotely? but can you answer if there is a known issue or not?
  17. Hi we see a similar issue, 1.ESET is stuck on update 2.The server is partly unresponsive and user's who attempts to logout is stuck on: Please Wait for the system Event Notification Service so between the 26 and today there must have been a bad definition/module release. i have a server where i can recreate the issue where the ESET update is stuck again after a hard reboot. update seems to have stopped here on some servers: 2019-10-26T12:00:15Z 09e5a745-679c-4215-90be-6b4c212bcf4e,efsw,211,7.0.12016.0,GA,biz paid(3),6.3.9600 SP 0.0 NT
  • Create New...