NetGuardian Pro

Windows Security app open on a laptop screen showing the firewall and network protection settings

How to check a Windows Firewal

Most Windows PCs have a firewall running right now, and most people have never opened the settings to check. That’s usually fine. But it’s worth two minutes to confirm your windows firewall is actually switched on, and to understand what it’s protecting you from and what it isn’t.

Check that Windows firewall is on

This takes about a minute on Windows 10 or 11.

  1. Search for “Windows Security” in the Start menu and open it.
  2. Select Firewall & network protection.
  3. Look at which network profile is active. Windows shows you whether you’re on a domain, private, or public network.
  4. Under Microsoft Defender Firewall, check the toggle is set to On for the profile you’re using at home.
  5. If it’s off, switch it on. If an app you need stops working, it’s better to allow that app through the firewall than to turn the whole thing off.

Your home Wi-Fi should be set as a private network, not public. The difference matters: on a private network other devices you trust can see yours, while on a public network (a coffee shop, an airport) Windows locks things down harder because strangers share the same connection.

What Windows firewall actually blocks

A firewall filters traffic. It decides what gets in and out based on rules tied to IP addresses, ports, and the specific program trying to make the connection. That’s genuinely useful. It stops random incoming connections from reaching a program that has no business listening for them, and it can block an app entirely if you want.

What it doesn’t do is look at what’s inside that traffic or judge whether a program is behaving normally. If a piece of software is already allowed to reach the internet, and something hijacks that same software, the firewall has no reason to stop it. The connection still matches an approved rule. The firewall isn’t wrong here, it’s just answering a narrower question than people assume: is this connection allowed, not is this connection safe.

Firewall for a home network: router and PC, not just one

A home network really needs two layers. CISA recommends a firewall at the router, which blocks threats before they reach any device in the house, plus a firewall on each PC, which filters that machine’s own traffic. Most routers ship with a firewall built in, though it’s sometimes off by default, so it’s worth checking the router’s settings alongside Windows. If you want a fuller checklist for locking down the rest of the home network, Home Network Protection: Practical Security for 2026 walks through the router side in more detail.

Is Windows firewall enough on its own?

No, not by itself. A firewall filters connections. It doesn’t remove malware that’s already run, and it doesn’t replace antivirus, which CISA still recommends running on every device. Signature-based antivirus has its own gap too: it’s built to catch known threats, so brand-new or disguised malware can slip past both layers.

This is the gap between “connection allowed” and “program behaving normally.” A firewall won’t tell you that a program which was always trusted has started sending data somewhere odd. That’s a different kind of watching, one that looks at ongoing activity rather than just the rule a connection matched on the way in. NetGuardian Pro does that on top of the firewall, watching network activity on the PC and flagging anything that looks off, with a plain suggestion for what to do next.

It also helps to know what’s actually connected to your network in the first place. If you’ve never checked, Is my Wi-Fi or PC hacked? How to check and the Wi-Fi scanner for Windows guide both cover how to spot a device that shouldn’t be there, which a firewall alone will never flag since it only cares about traffic rules, not who’s sitting on the network.

Sources

If it isn’t for you, there’s a 7-day refund window.

Related reading: Network monitoring tools for Windows: what a home or small office needs.

About the author. Published by Joel Papenfus, founder of NetGuardian and creator of NetGuardian Pro. The sources this post draws on are linked in the post. Reviewed and checked by Joel on 1 October 2026.