Jump to content

JozefG

ESET Staff
  • Posts

    51
  • Joined

  • Last visited

Everything posted by JozefG

  1. Windows security service has delayed start which means until it is running these sections are empty. Does it show anything after some time? Other option is that there are failures logged in our event log or in Windows Event log.
  2. @Vangelis Try to remove this registry key and see if it helps. HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\StartupApproved\Run\egui
  3. Please collect logs via Logcollector and provide also Boot Process monitor log. You can send me link to logs in PM.
  4. @Crunch Bootlog was correctly saved now, but it confirmed what I saw in Logfile.pml from previous run. Security Center service failed to establish connection with WMI because it is not running.
  5. @Crunch thanks for the logs. Even though Bootlog.pml was corrupted/incorrectly closed. Logfile.pml contained the start of wscsvc So the issue in your case is that WSC cannot initialize its connection with WMI. Most probably due to fact that there is no WMI service running. Also there is no WMI Provider Host application running. What does running this command from command prompt say? wmic /namespace:\\root\SecurityCenter2 Path AntivirusProduct GET displayName,ProductState
  6. @Crunch you can generate such log by following steps here https://support.eset.com/en/kb6308-using-process-monitor-to-create-log-files#boot_logs It seems that you are experiencing very nasty issue API calls are returning ERROR_DISK_OPERATION_FAILED. Most probably due to failure during initialization of WSC service.
  7. @Crunch Could you collect new set of logs? Hopefully we could find solution for those errors. Edit: It would be great if you provide also process monitor log from boot stopped after the notifications start popping up. That could really help me with investigation.
  8. @waluigiguatemala Does your issue with newer versions lie within Advanced Setup?
  9. Do I understand it correctly that if Shadow Defender's Shadow Mode is not active it does work correctly? From the description of Shadow Mode it looks like it may prevent some things to be done correctly.
  10. They were some things that it should recognize, but due to some other things missing it failed to detect them. Glad to hear that either way your logs helped us identify some places to improve in Uninstaller.
  11. Which version was installed? Was MalwareBytes installed alongside ESET or afterwards? According to Windows event logs MSI found multiple installations. These events from around same time. Windows Installer installed the product. Product Name: ESET NOD32 Antivirus. Product Version: 4.0.68.0. Product Language: 1051. Manufacturer: ESET, spol s r. o.. Installation success or error status: 1603. Windows Installer reconfigured the product. Product Name: ESET Security. Product Version: 11.2.49.0. Product Language: 1033. Manufacturer: ESET, spol. s r.o.. Reconfiguration success or error status: 1603.
  12. @Prayer1 Which version of ESET product do you have installed? Are you asking about postponing ESET updates to newest product version?
  13. @SeriousHoax @itman are you having these issues with Security Center integration module 1029? If so please provide logs.
  14. Yesterday new Security Center integration module: 1029 was released to pre-release channel. Can you try this module and see if it fixes your issue? There were some timing related issues combined with possible long initialization inside WSC fixed. There might be slight chance of Defender starting even with all these fixes caused by long initialization in WSC itself.
  15. @itman@VanBuran would you be interested in testing module that should hopefully fix this issue?
  16. 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 do we find ourselves unregistered after some reboots as we definitely do not unregister unless it is needed/requested e.g. full uninstall. Possible cause could be that WSC cannot get some data.
  17. 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.
  18. @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?
  19. @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.
  20. TLDR; No. We are required by Microsoft to communicate with WSC in order to be an antimalware provider.
  21. @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
  22. @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 Service has stopped. 10/28/2020 12:47:20 PM The Windows Security Center Service has started. 10/28/2020 12:47:21 PM Updated ESET Security status successfully to SECURITY_PRODUCT_STATE_ON. 10/28/2020 12:47:22 PM Updated ESET Security status successfully to SECURITY_PRODUCT_STATE_OFF. 10/28/2020 12:47:22 PM Updated ESET Firewall status successfully to SECURITY_PRODUCT_STATE_ON. 10/28/2020 1:26:24 PM The Windows Security Center Service has started. 10/28/2020 1:26:24 PM Updated ESET Firewall status successfully to SECURITY_PRODUCT_STATE_ON. 10/28/2020 1:26:24 PM Updated ESET Security status successfully to SECURITY_PRODUCT_STATE_ON. according to system event log there seems to be reboots triggered 10/28/2020 12:25:53 PM The process C:\Windows\System32\RuntimeBroker.exe (RMP01) has initiated the restart of computer RMP01 on behalf of user RMP01\itp for the following reason: Other (Unplanned) Reason Code: 0x0 Shutdown Type: restart Comment: 10/28/2020 12:31:22 PM The process C:\Windows\System32\RuntimeBroker.exe (RMP01) has initiated the restart of computer RMP01 on behalf of user RMP01\itp for the following reason: Other (Unplanned) Reason Code: 0x0 Shutdown Type: restart Comment: Is the machine rebooting by itself?
  23. @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
  24. @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.
  25. @FRiC please provide ETL logs created by In case of default installation it should be present in C:\ProgramData\ESET\ESET Security\Diagnostics folder.
×
×
  • Create New...