I've even tried Learning mode but after switching back to Interactive mode, the issue comes back. I've even used the ESET Cleaner and performed fresh installs. After reboot, the traffic is once again blocked and I get the same prompt. Shouldn't the rule depicted below, allow the traffic depicted in the image above:įor the sake of clarity, if I get the prompt depicted in the first image and select Remember until application quits, or if I select Create rule and remember permanently, and click the Allow button, traffic is allowed and the app works until I reboot the system even when I have selected Create rule and remember permanently.
I even created a rule and added 127.0.0.1. After each reboot, I'm promted again… Rinse, repeat.Īnd before anyone asks, there's no corresponding entries listed under Setup->Network-> Resolve blocked Communication or Resolve temporarily blocked IP addresses. After selecting Allow and adding a permanent rule, everything works until the next reboot. I currently have 8 identical rules for the same Veeam exe. This page displays changelog information and release notes for recent ESET product releases (listed by the most recent version to earlier versions and are.
To keep this simple, I'll focus on one application Veeam Agent for Microsoft Windows.Īfter every system reboot, ESET prompts about traffic for which I have already added a permanent rule for, from previous prompts.
Several apps stopped functioning because ESET is blocking connections even though rules do exist to allow those connections. Every thing worked until these updates were installed. Both ESET Endpoint and ESET Internet Security 16.2.11 suffer from the same issue that did NOT exist prior to these updates.
0 kommentar(er)
