SlashRose

So you knew about this problem (yes, this IS a problem) for several years. And after that you telling your clients - no, this is not a problem. And maybe in the future we fix this problem, that is not a problem. But no fix for several years!
FYI: the solution is simple - in firewall rule you can let user choose path to exe if it is a classical programm, or select from list of installed modern apps. There is API to tell which folder belongs to which installed app. That way user can create rule for whole app.

AFAIK, the eset files are not corrupted - I believe that the issue here is that ESET has updated them but not updated the security hashes.

This is usually accomplished the reverse of what you are doing.  In Win, the default browser would be set to IE11. The advantage of this is if your browsing in FF and then land on an Eset whitelisted banking site for example, Eset would auto open that site in IE11 using Banking and Payment Protection.
BTW - no one including Microsoft recommends using IE11 for anything anymore. Also as far as FireFox goes, Eset creates a separate profile used only for Banking and Payment Protection. The profile FireFox created for non-Banking and Payment Protection browsing activities is not used.

Thanks for the heads-up, I can confirm the issue too and have reported it to developers. Will keep you posted.

I am 100% there with you, I am now disappointed that you make the effort to test the software, report the errors found to the German support and all reported errors in the final, or so-called final, in my eyes nothing more than a very bad beta version is to find again + to find the errors of the previous build again, if this continues with Eset, I will also consider whether I should pay for it and that although I am an absolute Eset I'm a fan and have been using it since NOD v2, I am really very disappointed!

I am 100% there with you, I am now disappointed that you make the effort to test the software, report the errors found to the German support and all reported errors in the final, or so-called final, in my eyes nothing more than a very bad beta version is to find again + to find the errors of the previous build again, if this continues with Eset, I will also consider whether I should pay for it and that although I am an absolute Eset I'm a fan and have been using it since NOD v2, I am really very disappointed!

Yes, the scans with this build take much longer, it takes about twice the scanning time for the same files as the previous build!