Here are the windows firewall settings that glaswire made when I manually added it(I had to since it never shows up automatically). I don’t see anything that jumps out as competing with it.
Nothing is set to block port 443(which is what the curl is targeting in the logs)
And I don’t (currently) have an AV installed except the windows defender. (and a noisy little bugger it is)
The way GlassWire works in Click To Allow mode is everything is blocked by default. Allowed apps are then added through a rule like the one you showed. So you won’t find a rule that explicitly blocks port 443. The rule you showed looks fine and should do the job, assuming that executable doesn’t rely on something else to make the connection. Perhaps check the game folder for any other executables that might be in the mix.
The only other executables are The unity crash handler and ffmpeg so… nope.
edit: well the unity crash handler CAN make its own connection to call out when a crash happens but I doubt they are using it to make connections…
I’m afraid I am out of ideas then. I don’t own the game and so cannot test.
Probably best to open a support call with GlassWire.
I will ask our team to look into this. Can you confirm which firewall mode you are using? We have “Click to Block” which auto allows outgoing connections unless you manually block from the list, and "Ask to Connect’ which blocks everything by default and prompts you to allow/block when an app connects to the network.
