We publish a Windows 10 app that communicates with a VR headset on the same LAN (behind the Wi-Fi Router firewall). Avast doesn’t identify our installed files on Windows as malware/PUPs, but it does block incoming connections to our app from the VR headset (on unregistered ports our app uses). This has been a source of frequent support incidents from our users with Avast.
We prevent connection blocking in Windows Defender Firewall by calling an API from our signed/trusted setup program that create exceptions rules. How can we prevent connection blocking behavior in Avast, without requiring users to manually allow our app? Is port information included in vendor application whitelisting, or do we need to do something else?
Thanks
