Ok here’s an update to my last post that might help. I found multiple instances of Inbound and Outbound Rules in my Windows Defender Firewall Advanced Settings, one set apparently from a much older version of Audirvana. My Audirvana Remote connection problems started when Audirvana first updated, and were exacerbated by Windows 10 updates, so this seemed suspect.
I then deleted all the mess of Audirvana Inbound and Outbound Rules and started over by launching Audirvana again and letting Windows Defender decide what fresh Rules to create (need to make sure “Notify me when Windows Defender Firewall blocks a new app” box is checked in Firewall > Customize Settings, then tell it to “Allow” for Private Networks).
Windows Firewall then created two Inbound Rules, one for Audirvana Private UDP and one for Audirvana Private TCP, and it created zero Outbound Rules, and so far the connection is working. Before I did this rules refresh I could not connect at all without disabling Windows Defender Firewall. Now I can connect with Firewall turned on so I think I’m on to something.
We’ll see if connection holds with just these two Inbound Rules. If not I will try going in to “Allow an app or feature through Windows Defender Firewall” and telling it to allow Audirvana through which I believe will create a set of Outbound Rules in addition to the Inbound Rules and test again. By the way, if you don’t see Audirvana in your “Allow an app…” list you need to go into Add or Delete Programs Control Panel and Repair Audirvana.
I will report on if this is a fix. Isn’t this fun?