Jump to content

Recommended Posts

  • Administrators
Posted

Agree, didn't find any ironic posts in the mentioned topic either, we all were trying to help and nobody was teasing Doctor-Z. I've just replied there that the blocking rule for svchost.exe is a custom rule and was created after installation. Default rules commence with "Block" but this rule commenced with "Deny". Also I don't have such rule in my firewall rule list. I conclude that ESET firewall merely did its job as expected and blocked svchost.exe as instructed to by the custom rule.

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...