Please remind that when apps on your computer initiate outbound connections then the corresponding inbound connections belonging to those outbound connections is always granted by CFW. Only inbound connections initiated from outside your computer can be blocked.
Thats not how your supposed to do it that’s why, I said you need to create a global rule to allow only the necessary port/ports that you want the application to accept incoming connections from with the global rules. For example, if you want an application to accept incoming connections on TCP port 80, then you would create a global rule to allow incoming with protocol tcp and destination port 80. Application rules are mainly used to control outgoing connections, while global rules are for setting up incoming connections.
Thanks for the suggestion. What you are saying is, Allow inbound connections for particular listen ports, rather than for apps.
I’m just curious though. In the previous screenshot I posted, I don’t see anything fundamentally wrong with my rules setup. But why are the incoming connections still getting through for all apps rather than just the one app.
I kind of had same question a while ago here Firewall traffic rules processing order.
From that thread I didn’t get a clear view or answer on how inbound connections are being processed either.
I'm just curious though. In the previous screenshot I posted, I don't see anything fundamentally wrong with my rules setup. But why are the incoming connections still getting through for all apps rather than just the one app.
Even though that is not the correct way, I don't believe other applications have active incoming connections, assuming those are the only rules defined in both the application and global rules. When I did the same, I get blocked firewall events for MS Edge as it listens for incoming connections and the same when I launch qbittorrent.