I did. And the old settings. I started a thread about it when it first came up for me, and we went through all that. The only setting that allows the Miracast screen projection isn’t intended for that and opens up the firewall far more than is necessary, and far more than I am comfortable with.
The point is that not only does the Avast Firewall block a Windows 10 ability that isn’t even an obscure one (dirty great button in the Action Centre), but it doesn’t put up any message that it’s done it, let alone offer the user the choice to allow it - so the user may not figure that the problem is Avast and just think the Windows 10 function is broken (as i did before digging in to investigate - at first I assumed a Windows 10 update had broken the screen projection since I’d last used the function when I was still using Comodo Internet Security). And the settings that should exist to deal with this - the ‘Friends’ page in the old settings, which shows that chunks of the reserved-for-private iP address ranges as per IANA and IETF standards have not been set as 'Friends when they should be - has been deactivated so the user cannot even add them when needed like for this. It’s been hardwired now that only the 127.x.x.x and 192.168.1.x reserved-for-private ranges are ‘friends’, and the user cannot add the rest of those reserved ranges.
And in any case, the user shouldn’t need to dig into the bowels of obscure parts of Avast to permit a front-and-centre Windows 10 function that they’re not even told Avast is blocking. If the ‘friends’ (I hate this childish nomenclature) networks were set to include all the ranges that are reserved for use within a private network, as they should be, the Windows 10 built-in Miracast Connect would just work (like it does with several other Firewalls to my knowledge); and at worst on first use of the Miracast Connect Avast should pop-up a dialogue asking whether to allow it and remember the answer. I find it both amazing and frustrating that Avast, so good in so many respects, is so screwed up on this issue. The IP ranges reserved for use within private networks in the IANA and IETF STDs and RFCs are reserved for a reason and the ranges published for a reason. Avast should be configured to support all of them, and while it’s bad enough that it isn’t, the fact that the old settings actually allowed it to be corrected by the user but the page where the user can do that is still displayed but has been made non-functional is infuriating.
