You mean windows firewall? There are no Avast records/rules.
What I meant was that if the autosandbox would not solve the problem, then similar behaviors as the one you described are seen when updating security tools, like avast. Like "suddenly I can't browse with Chrome / FF / IE..." and those type of problems. Then by deleting old (seemingly working) rules, it forces the firewall to ask again for permission and re-creates them anew, "really" correctly.
It seems that sending the file (or link to it) to avast (and for now adding the respective exclusion to autosandbox) would be enough for your case.
Sorry for adding confusion
.
What you think about the same problem on machines, that run non-Avast antivirus?
Sorry, sincerely, no idea. If I had to guess, is also something of the same sort. Either some firewall rule to be re-created, or some "heuristics" feature (as in avast, behavior shield / autosandbox).