For the moment, until GW works at least as fully as a Windows Firewall front end, I’m using Windows Firewall Control. As a reasonable security measure I’d checked the option for WFC to delete any unauthorized rules created by programs other than WFC. But then today I twigged as to the most likely reason for WFC recently giving me a daily prompt to allow / deny Net access to GlassWire.exe. Each time this happened I would examine WFC’s listing of Windows Firewall’s rules, and after my allowing GW there would be only the one entry - which means that repeatedly the existing rule for it was getting deleted. As far as I can make out, no other rules are getting deleted and requiring re-prompts.
I assume therefore that GlassWire.exe is writing its own Windows Firewall rule each day, probably when it checks for GW update, and is thus triggering WFC to delete that rule. If that is what is happening, it is unhelpful behaviour, because it is good security practice to disallow any non-Windows processes apart from WFC from writing or amending Windows Firewall rules. I want GW not to go creating rules for itself at all - at least until it has advanced to the stage where I can use GW as a complete and superior replacement for WFC.