Check Your Firewall Status in Windows 11 & 10 (3 Ways)
—
To check your firewall status in Windows 11 or 10: press Start, type firewall, and open Firewall & network protection. The page shows three entries — Domain, Private, and Public network — each with its own on/off state; on a healthy PC all three read Firewall is on. That triple listing is not clutter, and it is the fact this page is really about: Windows does not run one firewall — it runs three rulebooks, and it switches between them based on a question you probably clicked past years ago: that little "Do you want your PC to be discoverable?" popup when you joined a network. Ten seconds to check, one page to actually understand it — and the terminal one-liners for the days you want proof.
Jake found the worst version of this during a routine tune-up. A customer's laptop came in for "general slowness," and his standard once-over stopped cold at the firewall page: all three profiles off, and by the look of things, off for years. The archaeology was easy — back in 2023 an online game kept disconnecting, a forum post said "disable your firewall," it seemed to work, and the setting was never thought about again. Every coffee shop, airport, and hotel network since had met that laptop with its front door removed. Jake turned all three back on and added one allow rule for the game — which, it turns out, was all the game had ever needed.
Ethan: "The pizza guy couldn't get through, so instead of giving him a doorbell, they took the door off the house — and left it off for two years. The firewall has a whole system for letting the right visitor in. Removing the door was never on the menu; it just happened to be the first search result."
The 15-second check, properly read
- Press Start, type firewall, and open Firewall & network protection (it lives inside the Windows Security app).
- Read the three rows: Domain network (workplaces with a company network), Private network (your home), Public network (cafés, hotels, everywhere untrusted).
- One row is tagged (active) — that is the rulebook currently guarding you, chosen by the kind of network you are on right now.
- Healthy state: all three say Firewall is on. Any Off — especially on the active one — is worth fixing before you finish your chai.
If the page instead announces that another program is managing the firewall, that is a different (and usually fine) situation — covered below.
Three firewalls, and the popup that picks between them
Here is the piece that turns this from trivia into understanding. When you join a new network, Windows asks whether your PC should be discoverable — and your answer files that network as Private (trusted: file sharing and printer discovery allowed through) or Public (untrusted: your PC goes quiet and invisible). That choice decides which of the three firewall rulebooks applies on that network, every time you connect to it. It is why your printer "disappears" when the home Wi-Fi accidentally got filed as Public, and why sharing anything at a hotel is harder than at home — not glitches, but the correct wall for the declared neighborhood. We flagged this setting from the connection side in our Wi-Fi guide; this page is where the other end of that wire was going the whole time.
The terminal one-liners (proof, not vibes)
Two commands, no admin needed, both great for checking a machine remotely or scripting a family fleet. Classic: netsh advfirewall show allprofiles — scan for State ON under each profile heading. Modern PowerShell: Get-NetFirewallProfile | Select Name, Enabled — three rows, True or False, no scanning required. If the graphical page and the commands ever disagree, believe the commands and suspect the app — the same dashboard-vs-engine split we covered for Windows Security's antivirus pages applies to its firewall pages too.
Turning it on (and the honest word about turning it off)
- On the Firewall & network protection page, click the profile that shows Off.
- Flip Microsoft Defender Firewall to On. Approve the admin prompt.
- Repeat for each Off profile — all three should end up On.
- If something you use breaks afterward, do not come back to this toggle — give that one app an allow rule instead. Doorbell, not door removal.
Is turning it off ever legitimate? For a few minutes of deliberate diagnosis — "is the firewall even the thing blocking this?" — with the toggle going straight back on afterward, sure. As a standing state, no: the modern internet portscans everything constantly, and an unfirewalled laptop on public Wi-Fi is volunteering for every one of those knocks. Every "disable your firewall" fix has a narrower, better version, and the allow-rule guide is usually it.
"These settings are managed by…" — the third-party case
Security suites (Norton, McAfee, Bitdefender and friends) often bring their own firewall, and Windows politely steps aside — the status page then names the product in charge instead of showing its own toggles. That is a working arrangement, not a problem: check status inside that product's own window. The trouble twin, exactly as with antivirus, is a suite that was uninstalled carelessly — leaving Windows convinced someone else is on duty when nobody is. The cure is the same one from our security-app guide: the vendor's dedicated removal tool, a restart, and Windows' own firewall resuming automatically. And if the toggle refuses to turn on with an error about the service, that exact failure has its own dedicated fix page.
Reading the status page like a technician
| What you see | What it means | Action |
|---|---|---|
| All three profiles On | Healthy — the normal state | None; close the page content |
| Public (active) — Off | Doorless on an untrusted network — the worst combination | Turn it on now, before reading further |
| Home network showing as Public | Network mis-filed — sharing and printers will misbehave | Wi-Fi properties → set network to Private |
| "Managed by [product name]" | A third-party suite runs the firewall | Check status in that product; fine if you installed it on purpose |
| Toggle snaps back off / service error | The firewall service itself is down | The dedicated service-fix guide (linked above) |
| Settings grayed out, "managed by your organization" | Policy control — workplace IT, or a "tweaker" tool's leftovers | IT on a work PC; undo the tweaker on a personal one |
What the firewall does — and what it never promised
Honest scope, because the name gets overloaded: the Windows firewall's main job is blocking unsolicited incoming connections — strangers on the network knocking on your ports uninvited. Outgoing traffic your own programs start is allowed by default, which means a firewall showing On does not stop malware you invited in from phoning home, does not scan downloads (that is the antivirus's desk), and does not make public Wi-Fi private (that conversation is our network-security reality check). It is one guard with one clear job — done silently and well for twenty years — not a force field. Knowing the boundary is what keeps you from either dismissing it or expecting magic from it.
Every firewall errand, and the right page for it
Firewall questions arrive wearing each other's clothes — a "firewall broken" complaint is often a mis-filed network, and a "network problem" is often one missing allow rule. This site has grown a page for each real errand over the years, so rather than stretching this one to cover them all badly, here is the map. Bookmark whichever row describes your recurring life:
| You want to… | Go to |
|---|---|
| Check it is on | This page — the 15-second check above |
| Let a blocked game or app through | Allow/block an app through the firewall |
| Undo years of mystery rules in one move | Reset the firewall to defaults |
| Fix "cannot start the firewall service" | The service-error fix |
| Fix sharing/printers vanishing at home | Set the network to Private (Wi-Fi properties), not the firewall toggle |
FAQ — the Windows firewall
How do I check if my firewall is on?
Start → type firewall → Firewall & network protection. All three profiles (Domain, Private, Public) should read "Firewall is on." Or run netsh advfirewall show allprofiles for the terminal version.
Why does Windows show three firewalls?
They are three rulebooks — Domain for company networks, Private for home, Public for untrusted places — and Windows applies the one matching your current network's classification. One firewall engine, three postures.
Which profile is protecting me right now?
The one tagged (active) on the status page — decided by whether the network you are on was filed as Private or Public when you first joined it.
What did that "make your PC discoverable" popup actually do?
It filed the network as Private (discoverable, sharing-friendly) or Public (quiet and invisible) — which is precisely the switch that selects your firewall rulebook on that network forever after. Probably the most consequential popup people click blind.
How do I turn the firewall on?
On the status page, click each profile showing Off and flip Microsoft Defender Firewall to On. If the toggle refuses or errors about the service, that failure has its own dedicated fix guide, linked on this page.
Is it ever okay to turn the firewall off?
For a few minutes of deliberate testing, with it going straight back on: fine. As a standing state: no — whatever an old forum post said, the correct fix was an allow rule for one app, not removing the door.
A game or app stopped working — is the firewall blocking it?
Possibly — the test is adding an allow rule for it (two minutes, covered in our allow/block guide) rather than disabling anything. If the app works with a rule, you have your answer and your fix in the same move.
What is the PowerShell command for firewall status?
Get-NetFirewallProfile | Select Name, Enabled — three rows, True or False. No administrator rights needed just to look.
My status page says another program manages the firewall. Bad?
Fine if you knowingly run a security suite with its own firewall — check status in that product. Bad only when such a suite was uninstalled sloppily and nobody is actually on duty; the vendor's removal tool untangles that.
Does the firewall stop viruses?
No — it blocks uninvited incoming connections. Scanning files and catching malware is the antivirus's job; the two guards work different doors of the same building.
Why can't I see my printer or other PCs at home?
Nine times out of ten the home network got filed as Public, so the firewall correctly went invisible-mode. Set the network to Private in its Wi-Fi properties — do not loosen the Public profile itself; you want that one strict for actual cafés.
Does the firewall slow down my internet or gaming?
Not measurably — it inspects connection attempts, not your bandwidth. Game lag has a hundred causes; this is reliably not one of them.
What are inbound and outbound rules?
Inbound rules govern who may connect to you (strict by default); outbound rules govern what your programs may reach out to (allowed by default). The advanced console manages both, but everyday needs rarely require it.
My firewall settings are grayed out. Who owns them?
Group policy does — your IT department on a work machine, or a "privacy/debloat tweaker" tool's leftovers on a personal one. Undo the tool, or accept IT's arrangement.
When should I reset the firewall completely?
When years of accumulated rules from old apps and old fixes have made behavior unpredictable — a reset returns factory defaults, after which you re-allow the few things you actually use. Our reset guide walks it through.
Is the Windows firewall good enough, or do I need a third-party one?
For nearly everyone: it is genuinely good, on by default, and silent — the best kind of security. Third-party firewalls earn their place mainly through outbound-control features most people never configure. Same song as antivirus: habits and defaults first, products on merit only.
Where to go next
- Allow or block an app through the firewall
The doorbell rule — the fix every "disable your firewall" post should have said. - Cannot start the firewall service — solved
For when the toggle itself refuses to obey. - Reset the firewall to factory defaults
The clean-slate move for rule collections gone feral. - Windows Security won't open? Fix it
When the app holding all these pages is the thing that's broken.
Revision note. Originally published July 2016 as a quick tutorial for finding the firewall switch in the Control Panel era. Rewritten August 18, 2026: the modern Windows Security route, the three-profiles truth and the popup that picks between them, the terminal one-liners, the third-party-suite cases, and honest boundaries on what a firewall actually does. If a forum post ever talked you into switching yours off "just to fix one game," you have plenty of company and an easy road back — two clicks, one allow rule, door restored. Spotted something wrong or something missing? Tell me through the contact page and I will fix it. Stay walled — sensibly.