Breach

OK, I uninstalled, reinstalled, and couldn't even activate. But Google helped. I had to reset winsock: netsh winsock reset [Edit: So it is related to Symantec PGP Desktop, which sets itself as first entry on the winsock catalog. Not sure who should fix the incompatibility - ESET or Symantec]

Thanks, no this is a brand new installation (Jan 2017) with the latest version (10.x). All was fine until today.

Hi, Strangely enough I cannot update defs since 04 March. I'm currently on 15032 and see there are a couple of new releases since. The message I receive is 'Could not connect to server'. Using the latest 10.x release. I don't think anything changed on my side Is it specific to me? Thanks [I attached the update log, but I guess it may contain sensitive info so I can provide it to an Admin]

Problem solved. I found the solution in another thread. For some reason I had to install the driver manually as described here: https://forum.eset.com/topic/6487-firewall-non-functional-issue/ Then restarted and no issue.

Thanks, here you go: C:\WINDOWS\system32>sc query epfwlwf SERVICE_NAME: epfwlwf TYPE : 1 KERNEL_DRIVER STATE : 1 STOPPED WIN32_EXIT_CODE : 31 (0x1f) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 C:\WINDOWS\system32> C:\WINDOWS\system32>sc query epfwwfp SERVICE_NAME: epfwwfp TYPE : 1 KERNEL_DRIVER STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 C:\WINDOWS\system32>sc query epfw SERVICE_NAME: epfw TYPE : 1 KERNEL_DRIVER STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 And here's what happens when I try to start the service manually: C:\WINDOWS\system32>sc start epfwlwf [sC] StartService FAILED 31: A device attached to the system is not functioning. C:\WINDOWS\system32>sc start epfwlwf [sC] StartService FAILED 31: A device attached to the system is not functioning.

Any help on this please? I just tried uninstalling/reinstalling ESS 9 (rebooting in-between). HIPS works, but Firewall doesn't.

Hard to say, because I think I moved to ESS 9 around that time. What I know is that ESS 8 didn't have firewall issues with 102xx. Regards

I uninstalled ESET SS 8 and installed 9. Pre-release updates didn't help. I have this in the event log: The Epfw NDIS LightWeight Filter service failed to start due to the following error: A device attached to the system is not functioning.

Hi there, I'm aware that HIPS doesn't work with non-RTM builds of Windows 10, but in my case the firewall is also disabled and doesn't turn on. Is this expected? Build 10586 here, ESET SS 9.0.318.0 Thanks

Hey Marcus, any update on this? Thanks.

Same issue here - dump link provided via PM to Marcos.

Yes, same here. Also HIPS can't be enabled. Given Windows 10's status I don't expect a quick fix, but hopefully it will be there before RTM hits.