Windows 10: Right Click - Add Inbound/Outbound Firewall Rule?

Hi guys,

I've always wondered why isn't there an option to quickly add an inbound/outbound firewall rule to an application straight from the app by, say, right click menu, add instantly?

Wouldn't this be a great feature to have?

Why the need to go to that Windows Defender Firewall with Advanced Security path and many steps every time?

I do this a lot nearly with every software that I install... would be awesome to have that and doesn't seem too complicated.

New here so let me know where one can suggest a feature?

Cheers

submitted by /u/notmuchery
[link] [comments]

:)

 

Windows 10 Firewall won't keep my inbound/outbound rules

I'm having the exact same issue with Windows 10.

None of the inbound rules, outbound rules or application exceptions persist for more than a few minutes.

Also I noticed that if I disabled the firewall for just the private network it would re-enable itself after a few minutes.

It sounds like the

 

Inbound Firewall Rule that Blocks

Code:

Please help me understand how the 2 Inbound Rules created by MMC actually operate.

Action, Enabled, Service, Program,                     Protocol

Block,  Yes,     Any,     C:\windows\system32\mmc.exe, TCP

Block,  Yes,     Any,     C:\windows\system32\mmc.exe, UDP
If these 2 rules were Outbound Rules, I'd say that client process 'mmc.exe' is blocked.

But applying equivalent logic (that 'mmc.exe' is blocked) to Inbound Rules doesn't make sense -- why would 'mmc.exe' (which created these Rules) block itself?

What (somewhat) makes sense is that 'mmc.exe' is a requester, and that these rules block all TCP & UDP datagrams & all processes.

If so, then there's quite a difference between Outbound & Inbound Rules.

In Outbound Rules, 'Program' specifies the target (the process that's blocked), whereas in Inbound Rules, 'Program' specifies the requester (the process that provokes blocking).

This is crucial reasoning because, if correct, then, as a consequence, every process is the target of Inbound Rules that Block.

What about Inbound Rules that Allow? I've always assumed that an Inbound+Allow means the specified 'Program' installs a listener (i.e., has handler(s) for the specified socket(s)).

I think that's pretty straightforward.

I've read what Microsoft provides and it's grossly inadequate -- what a surprise, eh?

Microsoft documentation presents only trivial explanation of how to complete the fields (example: "Type the path to the program in the text box"), or the tutorial's scope is limited (example: "On the Action page, select Allow the connection, and then click
 Next" -- no mention of "Block the connection").

Other web hits are just plain wrong (examples: "Program – Block or allow a program"; "Program - creates rule that controls connections for an app or program"; "if you are downloading a file through BitTorrent, the download of that file is filtered through an
 inbound rule" -- Rules control connections, not streams) or show ridiculous cases (example: "I want to block all outgoing connections on port 80").
Does anyone know of an architectural reference or guidebook that explains how Firewall Rules are implemented in a running system?
Warm Regards -- Mark.

 

Windows 10 Firewall won't keep my inbound/outbound rules

I gave it a try. Went to services.msc and restarted the firewall service. I set up one rule to block a program inbound and outbound as a test. After that, I was able to restart the computer a few times and the rule held in place. I also wasn't getting asked
to allow any programs through the firewall like I was before.

Then, a few minutes ago, I started my computer, the prompts asking me to allow Chrome and gcupd.exe through the firewall came back. As soon as I saw this, I went back to the firewall and checked. My sample rule was gone again.

Pretty strange behaviour!