ToolTip AI

Windows firewall,
rule by rule.

The firewall screen has one button that looks like a solution and twelve places where the actual reason lives. Twelve entries, ordered by how often each one is blamed for something it did not do.

firewall.cpl · Microsoft Entra ID · domain · private · public

How to read any firewall rule you did not write.

A rule is a match plus an action, and the match is usually the interesting part.

The console lets you create, enable and delete rules, so it invites you to treat the list as the cause. In practice most firewall failures are not a rule doing something wrong but a rule doing exactly what it says on a network you are not looking at, or a decision made by something else that happens to share the page.

Before changing anything, answer three questions in order: which profile is active right now, which direction the traffic goes, and is there any block rule that matches. Everything else — the log, the scope, an export — is how you prove your answers.

  • Profiles first. A rule can be correct, enabled and still not apply, because it belongs to the profile you are not on. netsh advfirewall show allprofiles state names the active one.
  • Direction is not optional. Inbound explains other machines reaching you. Outbound explains you reaching them. They are separate lists and separate defaults.
  • Block always wins. Not by order, not by specificity: any matching block rule ends the conversation, so the search is for a block you forgot, not for an allow you lack.
  • Nothing is logged until you ask. The dropped-packet log is off by default, which is why the honest debugging order is enable log, reproduce, read, then touch a rule.

The twelve places the firewall actually decides.

Ordered by how often each one is wrongly blamed, not by where it sits in the console.

The three profiles — and the one Windows actually picked for you
What it is
Every rule belongs to a profile: Domain (a work or school network you authenticated to), Private (a network you declared trusted) and Public (everything else). The firewall can be enabled, disabled or audited separately per profile, which is why «the firewall is off» and «it is blocking me» are two different sentences.
What changes
Nothing in the rule set changes when a network is reclassified — the rules stay, and a different set of them applies. Reclassifying your home Wi-Fi from Public to Private is what turns on network discovery, file sharing and printing, because those features are blocked by the built-in Public rules rather than removed. Windows asks you «Do you want to allow your PC to be discoverable» exactly once per SSID; answering nothing leaves it Public, and a router that renews its identifier can make the same café look like a new network every visit.
Risk
Careful Reading the wrong profile is the most common false diagnosis here: Settings shows the rules of the active profile only, so a rule you deleted «yesterday» may have belonged to a network you are not on now.
Inbound and outbound are not opposites, and outbound is open by default
What it is
Two rule groups per profile. Inbound decides who may reach this machine; the default is to block anything that no rule allows. Outbound decides what this machine may ask for; the default is to allow, and the only outbound rules that ship with Windows are exceptions to make that default work.
What changes
Inbound is where a blocked port lives, and it is the only direction that explains «other computers cannot see me». Turning outbound off entirely does not make the machine invisible — inbound is still what controls that — it just breaks Windows Update, the Store, certificate revocation, time sync and every telemetry and licence check, which is how «I hardened the firewall» turns into a machine that cannot validate its own certificates.
Risk
Expensive Deleting the built-in outbound allow rules, or setting outbound block-by-default on a machine that also needs updates, is expensive to unwind: the symptom appears hours later as a Store that will not open or a Windows Update stuck at 0%.
“Allow an app through Windows Firewall” — the checkbox that is not what it says
What it is
The list in firewall.cpl → Allow an app is a per-program rule, and it only writes what Windows can guess: the executable path and the two profile columns, Private and Public. The «Change settings» button is greyed until you are elevated, and entries for services are hidden because a service has no window to unblock.
What changes
A program rule allows the specific image path, not the feature. So the same app can be allowed on Private and still blocked on Public, and a program that launches its actual networking through a different executable (updaters, helpers, a bundled Python, a second process under a different name) is not covered at all by the entry you ticked. Removing an entry from the list does not remove the rules it created — those stay in the rule store until deleted by name.
Risk
Careful Ticking both columns is the reflex, and it is the one that silently opens a home app to hotel and café networks. Tick only the profile you are actually on, and read which column the rule is set to before you call it fixed.
Block beats allow, always — and rules from policy cannot be deleted
What it is
Four actions exist: Allow the connection, Allow the connection if it is secure (IPsec-authenticated only), Do not allow the connection, and the same three scoped to a group. The engine does not evaluate them in list order: any matching block rule wins over any number of allow rules, regardless of which was created first.
What changes
This is the whole explanation for «it worked until someone touched the firewall». A block rule can sit in a different group with an unrelated name, scoped to a remote address you would never think to check, and it will win. Rules created by Group Policy or by a mobile-device management profile appear in the list greyed out, with the note that they are associated with a setting: they cannot be deleted or edited from this machine at all, and the only honest fix is upstream in the policy.
Risk
Expensive Deleting allow rules to «clean up» while the block rule stays gives a machine that looks tidy and connects to nothing. Sort the list by Action before you touch anything.
Scope: the reason a rule works from one network and not another
What it is
Each rule has a remote and a local IP scope, and «Any IP address» is the default people never look at again. The scope also carries the predefined values Default gateway, Local subnet and Remote DHCP servers, and the local scope — which is hidden in the wizard and visible only on the Advanced tab — decides which of the machine's own addresses the rule applies to.
What changes
A rule scoped to your old office subnet stops working the day the network is renumbered, and it keeps showing as Enabled, so nobody suspects it. Multi-homed machines (VPN plus Wi-Fi plus Ethernet) fail in the other direction: the reply to a request arrives on an interface the local scope does not list, and the packet is dropped with no notification at all.
Risk
Careful Widening a scope to Any looks like the fix but it changes the exposure of the port to the internet, not just to your subnet. Add the specific address instead.
What the prompt is really telling you when it names an app
What it is
The dialog «Windows Defender Firewall has blocked some features of this app» fires when a program starts listening on a port and no rule covers it. Its two answers are not symmetric: Allow access creates a rule for the network you are connected to right now; Cancel creates nothing and leaves the app listening on a blocked port.
What changes
The rule it writes is inbound, scoped to the current profile, and points at the executable that happened to call listen — which is frequently a launcher rather than the service. That is why an app can prompt again after a reinstall, after an update that moved its files, after a profile change, or on every reboot when it binds a dynamic port. «Cancel» the first time and the app is silently crippled, and the notification never appears again once a rule exists.
Risk
Reversible Answering honestly is reversible: the rule is editable afterwards, and deleting it brings the prompt back. What is not obvious is that the dialog does not tell you which profile it just wrote to.
Loopback: why the packaged app cannot see localhost
What it is
Traffic from the machine to itself on the same interface. Win32 programs do it freely. Store and other packaged apps are blocked from loopback by default, in a layer that is not in the firewall UI at all, because the isolation model does not assume an app may talk to any local service it finds.
What changes
The exemption list is machine-wide and managed with CheckNetIsolation LoopbackExempt -a -n="AppFamilyName", and the family name comes from Get-AppxPackage — not from the display name you see in the Start menu. Adding an exemption is what makes a local development server reachable from a packaged client; removing it restores the isolation but leaves the rule harmless-looking.
Risk
Careful Loopback problems are usually blamed on the firewall and are not fixed by any rule in it. If a packaged app fails only against localhost while everything else works, you are in this entry.
Which service is actually deciding, and who turned it off before you
What it is
The engine is the Windows Firewall (mpssvc) service, sitting on the kernel filter platform wfp.sys. The UI in Settings is a client of it. When a third-party security product registers itself in the Security Center, it takes over filtering and Windows reports «managed by your security product» — the Microsoft rules then have no effect on the decisions being made.
What changes
Stopping the service does not «disable the firewall»: it removes the filter driver's policy source, breaks the UI, and leaves IPsec and remote-management behaviour undefined. A machine that shows three profiles all «not configured» is usually either taken over by another product or has had the service disabled by something. Confirm with netsh advfirewall show allprofiles state rather than trusting the page you are looking at.
Risk
Expensive Disabling mpssvc by hand, or setting it to Disabled with sc config, can leave a workstation that cannot be re-entered through the UI until the service starts again — and that state looks identical to «the firewall is the problem».
Connection security rules: the busy-looking page most machines never use
What it is
Below the firewall rules there are Connection security rules (IPsec with certificates or preshared keys) and Core isolation (machine-wide IPsec policy). Windows creates them through Group Policy or a management profile, never by itself on a home PC.
What changes
If your work or school account enrolled the device, an organisation policy can require that traffic be authenticated, and the resulting rules are not editable locally; they also explain failures that look like the firewall blocking an app when the real event is that a connection could not be authenticated. netsh secsh ipsec shows the dynamic security associations, and the SecStart state is where you can see that a policy is loaded.
Risk
Careful Nothing here is a knob for a home user. Editing a rule you did not create is the fastest way to lose access to a share you use every day.
The log is off by default, and it is the only honest witness
What it is
Two files in %windir%\system32\logfiles\firewall\pfirewall.log — one per direction family — recording allowed and dropped packets with the time, protocol, source, destination and the rule that matched. Both log dropped packets and log successful connections default to off, and the file rotates when it hits the size limit.
What changes
Turning on dropped-packet logging is the difference between guessing and knowing: a line that says DROP TCP 192.168.1.20:54123 192.168.1.7:5432 proves the firewall is the cause, and the absence of any line for that port while it still fails proves it is not. Logging successful connections on a busy server fills the file in minutes and buries the interesting part.
Risk
Reversible Enabling dropped-packet logging is the safe diagnostic, and it is the one thing to do before you start deleting rules. Turn it back off when you are done.
SmartScreen, Defender and the firewall are three different switches in one page
What it is
Settings → Privacy & security → Windows Security presents Firewall & protection, which also links app-and-browser control (SmartScreen), the antivirus engine and the network-protection feature. Only the first of those is packet filtering.
What changes
SmartScreen blocks a download or a first run by reputation, not by port; nothing in the firewall can produce its message, and no firewall rule can remove it. The antivirus blocking a connection reports itself differently again, usually as a notification about a network scan being blocked. Treating «Windows blocked it» as one system is why people spend an afternoon in the rule list with nothing there.
Risk
Reversible Reading which of the four produced the message costs one look and saves the whole session. The wording of the prompt, not the page you are standing on, tells you which one.
Reset without losing the rules you never made
What it is
Restore firewall defaults in the control panel, or netsh advfirewall reset, rewrites the whole policy store: profiles back to their shipped state, every manually created rule deleted, and the allow-list of apps rebuilt from Windows's own defaults.
What changes
This is the one action that removes rules created by other software — the database, the backup agent, the printer vendor, the game you stopped playing. Those applications do not notice their rule vanished, so the failure arrives later as «the printer stopped being reachable». Exporting first with netsh advfirewall export "C:\\fw.wfmx" gives you the only undo that exists; importing puts the store back.
Risk
Expensive A reset on a machine that has been in use for years removes rules nobody can re-create, because nobody remembers what they were for. Export before you do it, even if you expect to add nothing.

Firewalls fail quietly, and that is the expensive part.

A blocked port produces no message on the machine that is blocked. The screen you are looking at shows rules, not decisions, and the decision that broke your connection was made by a rule created three years ago by an installer, on a profile you only joined last week.

Get ToolTip AI on Microsoft Store
Windows 10 build 19041 or newerWindows 1164-bit onlyNo administrator rights
Part of the guides library.