Jump to content

JozefG

ESET Staff
  • Content Count

    32
  • Joined

  • Last visited

Profile Information

  • Location
    Slovakia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @itman@VanBuran would you be interested in testing module that should hopefully fix this issue?
  2. Not this again You say both working correctly I see Defender being the active one according to logs. Which means both realtime protections are running. From our logs I can see that once the wscsvc is running we try to update AV state to On we get E_PENDING results from AV API. After that we find out, through WSC public API, that we are unregistered(!!!) so we try to register and get E_PENDING again. Next we try to recover from that, but seems that there is some race condition which can be fixed rather easily. But again we get E_PENDING error for status update. Real question is why d
  3. According to logs last attempt was correct and we should be both on. Is it like that? There is visible one reporting of Off state from today morning. It seems you started logging after it happened. Off is usually tied with disabling of RTFS in advanced setup or if the license is expired and there is outdated detection engine. Please turn on this logging and try to reproduce it after it is reproduced turn it off and collect via LogCollector.
  4. @davidovitch Note that Windows Security Center service is delayed start service. Until it starts we cannot report anything as there would be bunch of errors. Can you please share screenshot of such alert?
  5. @jfksdt45245 Please if you are able to reproduce the issue continue according to @Marcos response. Those logs could tell us closely what is happening. Also that registry key should not be issue as we use dedicated private Windows API.
  6. TLDR; No. We are required by Microsoft to communicate with WSC in order to be an antimalware provider.
  7. @FRiC Can you please put machine to normal state and create ETL log from boot until the issue manifests? Do you happen to have some ESMC policy sent to application that could disable RTFS? Also it seems that you have Defender disabled via GPO(not critical issue). Edit: send please ELC log so I can see event logs
  8. @FRiC Something is really weird going on here. There is just too many ETL logs. Also according to Application event log 10/28/2020 12:28:58 PM The Windows Security Center Service has started. ... 10/28/2020 12:31:30 PM The Windows Security Center Service has stopped. 10/28/2020 12:34:38 PM The Windows Security Center Service has started. 10/28/2020 12:34:38 PM Updated ESET Security status successfully to SECURITY_PRODUCT_STATE_ON. 10/28/2020 12:34:40 PM Updated ESET Firewall status successfully to SECURITY_PRODUCT_STATE_ON. 10/28/2020 12:43:23 PM The Windows Security Center Serv
  9. @FRiC it is either display issue or there is something happening with Windows Security Center service (wscsvc). It is the source of data for UI, hard to say what could be the cause of issue since Firewall and Manage providers seems to get the data. You can try if manual change of RTFS state in our GUI will update it. Also can I ask you for ELC log? I might want to take a deeper look into this issue
  10. @FRiC according to the log we tried to update status for AV provider and we got this HRESULT 0x8000000a(E_PENDING). For us this means our request was queued by wscsvc and it will be handled. Firewall updates are working correctly. However in your case it looks like wscsvc has some issue with too many requests or something. IIRC this E_PENDING is usually seen around wscsvc start.
  11. @FRiC please provide ETL logs created by In case of default installation it should be present in C:\ProgramData\ESET\ESET Security\Diagnostics folder.
  12. @FRiC Please make sure you have latest Security Center integration module 1026.1 present. Can you also post screenshot of Manage providers in WSC UI?
  13. You can enable it in Advanced setup accessible by F5. Logs will be present in C:\ProgramData\ESET\ESET Security\Diagnostics after you stop logging. Is the problem visible even after module update and reboot?
  14. @Pepestift If the problem still persists please turn on Enable Kernel advanced logging setting. Run update or reboot. Note that Security center service has delayed start so let it sit for a while. Turn off logging and provide ETL logs from Diagnostics folder. @itman there was new Security Center integration module released Tuesday afternoon to all channels. It is possible that you got it after installation of 14.0.21.0
  15. @Page42 Is the problem still visible? If so please turn on Enable Kernel advanced logging setting. Run update or reboot. Note that Security center service has delayed start so let it sit for a while. Turn off logging and provide ETL logs from Diagnostics folder.
×
×
  • Create New...