Senortubbs

Thanks guys. Ultimately I have found a solution. I deleted, then reinstalled both games. ESET still didn't 'learn' a rule, but at least when I made one for it, it actually stuck. Hearthstone was just a particular challenge, because for whatever reason, where most games simply throw up a "can't find connection" error, it would just straight up crash. So, to summarise, for anyone else who has this problem in future. If you have a program that ESET - Refuses to recognise while in "learning" or "interactive" mode Doesn't seem to apply manually created rules to But does let through if you turn off the firewall entirely Then try reinstalling the program if at all possible, because the issue might be that it isn't correctly identifying the path to the program or some such.

It simply refuses to learn the rules for these applications.

I'm actually not familiar with the firewall troubleshooting wizard, how do I find/use that? I did try deactivating all the blocking rules (by unchecking them in the rule management view), still couldn't load them up. My suspicion is it has something to do with port 3724, since Hearthstone and WoW have that in common. Diablo III, which I launch through the same Blizzard launcher etc does not use that port, and operates fine.

Can't get the ESET firewall to play nice with Blizzard games, specifically World of Warcraft and Hearthstone. I've used ESET for years, played these games with it previously. But this last month, it refuses to let them connect. The only way I've been able to run either is to disable the firewall the entire time I play, and that's not a good solution. That also tells me though, that ESET is definitely the problem. Every other thread I've seen on this topic ends with "delete all the existing rules and put it into interactive mode" but that has not worked for me. Interactive mode is how I normally leave the firewall, and it works for everything else, but I am never getting the pop-up for these. I've even tried a trick I've learnt with some other programs, which is to disable for 10 minutes, run the application and then wait for ESET to 'discover' it when it turns back on. But in these cases it just shuts down all communication at that point. Which in WoW kicks me off, and in Hearthstone crashes the application completely. I've been trying to manually configure both applications. First allowing all, then specifically allowing the ports indicated on https://us.battle.net/support/en/article/firewall-proxy-router-and-port-configurationbut I'm not getting anywhere with that either. It's possible I'm setting it up wrong, because I have no idea what I'm doing there. Does anyone have any thoughts? I feel like I've exhausted all the normal solutions here. Surely someone else has managed to get either of these to run through ESET.