Well, it’s the same version number as the last one mentioned in the beta sub-forum.
And reading all the changes in the all the beta 19.7 versions’ first posts I am disappointed to see that there’s nothing related to my one issue I reported some time ago - Avast blocks the use of the Connect function in the Windows 10 Action Centre, which actually uses Miracast to project the laptop screen onto e.g. a Miracast enabled TV or onto a TV via a Roku Express, which does Miracast. And Avast doesn’t even pop up a notification to say it stopped it or offer to allow it.
I’m using the paid version, and it’s the Firewall that blocks the Miracast, which isn’t in the free version. And they’ve removed the configuration options that would allow proper use - the only way currently is to use settings that open far too wide a hole. I told them exactly what the problem was, and how the now hardwired ‘friends’ list is blocking reserved private address ranges and reserved ports it shouldn’t, which Miracast uses.
But you would think that Avast would fix something that prevents a feature of Windows 10 from working - and not some obscure feature, but one with a honking great on/off button in the Action Centre. Maybe they are just relying on the fact that because Avast doesn’t put up a notification, users won’t realise that it’s the Avast Firewall stopping the built in Windows 10 screen casting working.
Thanks. Hope it does better than the support ticket I opened with chapter and verse on the details of the problem, the reserved-as-private IP ranges that should be in the 'Friend networks but aren’t etc.