SandyEggoScott

> Since your app installer creates these Win 10 inbound rules, there should be no issue in regards to the Eset firewall. Thank you itman. That's good to know. In that case, we may not have to do anything. 🙂

Thanks for the quick reply. Q1: Beyond our providing step-by-step instructions, is there anything we can do to make this easier for the user? (e.g. a script?) Understandable. I was hoping that a signed installer or elevated process might have some API access... Q2: What can we do (programmatically) to detect that ESET is active (vs. just being installed)? On first installation of our software, we can advise the user to take action, but we don't want to give them ESET instructions if ESET isn't the active firewall.

Our Windows desktop app installer adds exception rules for our app to Windows Defender Firewall, but many of our users have third-party security software installed, and lots of them show up on our support channel after trying to use our app and getting frustrated at their inability to connect. Even though we warn them about third-party firewalls, many of them don't know how to whitelist a program, and we have to ask which product they have and then walk them through the process. Does ESET offer some means for a signed installer (or app running with elevated privileges) to programmatically add firewall exception rules like we already do for Windows Defender Firewall?

We publish a Windows 10 app that communicates with a VR headset on the same LAN (behind the Wi-Fi Router firewall). ESET doesn’t identify our installed files on Windows as malware/PUPs (according to VirusTotal), but ESET Firewall 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 ESET. 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 ESET, 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