It would be nice if there was a 'block' option instead of only an 'unblock' option. As shown here:
I realize it's a whitelist but 'layering' these things is necessary sometimes when the System account is set to only allow certain ports out, and yet it allows extra ports to connect that are not in your custom list. That part is a reproducible bug for me. Likewise trying to restrict the system process to intranet-only connections cuts down on some connections, but not all. Blocking everything from System works, as does letting everything through.
Also Get-NetTCPConnection shows outbound connections coming from the Idle Process rather than the System process, but it doesn't show up inside TinyWall's process list:
Not sure if anyone else noticed this. I pretty much use just TinyWall to block Windows annoyance connections, which Defender or even heavier software firewalls are often unwilling to do.
It would be nice if there was a 'block' option instead of only an 'unblock' option. As shown here:
I realize it's a whitelist but 'layering' these things is necessary sometimes when the System account is set to only allow certain ports out, and yet it allows extra ports to connect that are not in your custom list. That part is a reproducible bug for me. Likewise trying to restrict the system process to intranet-only connections cuts down on some connections, but not all. Blocking everything from System works, as does letting everything through.
Also Get-NetTCPConnection shows outbound connections coming from the Idle Process rather than the System process, but it doesn't show up inside TinyWall's process list:
Not sure if anyone else noticed this. I pretty much use just TinyWall to block Windows annoyance connections, which Defender or even heavier software firewalls are often unwilling to do.