How to Check Firewall Settings on Windows
Knowing how to check firewall settings on Windows helps you confirm whether your PC is protected and whether an app, port, or network profile is being blocked.
This guide shows the fastest ways to review Windows Defender Firewall settings in 2026 and understand what each setting means.
What Windows Firewall does
Windows Defender Firewall is a built-in security feature in Windows 10 and Windows 11 that monitors inbound and outbound network traffic.
It uses rules to allow or block connections based on network profile, application, service, port, or protocol.
In most cases, the firewall is enabled for three profiles:
- Domain network for managed corporate environments
- Private network for trusted home or office networks
- Public network for less trusted places such as airports and cafes
Checking the firewall is not only about confirming that it is on.
It also means reviewing which profile is active, which apps are allowed, and whether any custom rules are affecting connectivity.
How to check firewall settings on Windows from the Settings app
The quickest way for most users is through the Windows Security app.
This view shows the current firewall status for each network profile.
- Open Start and search for Windows Security.
- Select Firewall & network protection.
- Review the status for Domain network, Private network, and Public network.
Each profile should show whether Microsoft Defender Firewall is On or Off.
If you click a profile, you can see more details such as whether incoming connections are blocked and whether notifications are enabled.
This page is useful for a fast health check, especially if you suspect a network issue after installing software or connecting to a new Wi-Fi network.
How to check firewall settings on Windows using Control Panel
Control Panel still provides a classic view that many administrators prefer because it clearly displays the active status for each profile.
- Open Control Panel.
- Go to System and Security.
- Select Windows Defender Firewall.
On this screen, you can see whether the firewall is turned on for private and public networks.
From the left sidebar, you can access:
- Allow an app or feature through Windows Defender Firewall
- Change notification settings
- Turn Windows Defender Firewall on or off
- Advanced settings
Control Panel is especially helpful when you want to verify older settings or compare the behavior of private versus public networks.
How to check firewall settings on Windows with PowerShell
PowerShell is the most efficient option when you want structured information or need to check multiple systems.
It is also useful for IT teams and support staff.
Open PowerShell as an administrator and use this command:
Get-NetFirewallProfile
This returns the status of each profile, including whether the firewall is enabled, default inbound and outbound actions, and notification preferences.
Typical fields you may see include:
- Enabled
- DefaultInboundAction
- DefaultOutboundAction
- AllowInboundRules
- AllowLocalFirewallRules
If you want a more specific view of a single profile, use:
Get-NetFirewallProfile -Name Domain,Private,Public
For example, if you are troubleshooting an app that cannot connect to a server, PowerShell can help confirm whether the profile is active and whether firewall behavior matches your expectations.
How to check firewall settings on Windows using the command line
Advanced users can also use Command Prompt with the netsh tool.
Although PowerShell is the modern approach, netsh advfirewall is still widely used in support environments.
Open Command Prompt as administrator and run:
netsh advfirewall show allprofiles
This displays the state of the firewall for the Domain, Private, and Public profiles.
It also shows whether inbound connections are blocked and whether notification settings are active.
If you need a quick compatibility check on an older system, this method can be practical.
However, PowerShell generally provides clearer output and is better suited for automation.
How to check allowed apps and exceptions
Sometimes the firewall is turned on, but an app still cannot reach the network because it is not allowed through the firewall.
To check exceptions, review the allowed apps list.
- Open Windows Security.
- Select Firewall & network protection.
- Click Allow an app through firewall or open Allow an app or feature through Windows Defender Firewall in Control Panel.
Look for the app in the list and verify whether it is allowed on private networks, public networks, or both.
If an application is missing, it may need a manual rule or administrator approval.
Common examples include remote desktop software, file-sharing tools, multiplayer games, database clients, and development tools that need inbound or outbound access.
How to check advanced firewall rules
If you need more detail than the standard interface provides, open Windows Defender Firewall with Advanced Security.
This console shows inbound rules, outbound rules, connection security rules, and monitoring data.
To open it, search for Windows Defender Firewall with Advanced Security from the Start menu.
From there, you can inspect:
- Inbound Rules for traffic entering the computer
- Outbound Rules for traffic leaving the computer
- Monitoring for active policy and firewall state
This view is essential when diagnosing problems that are not obvious in the standard Windows Security app.
It is also where administrators create granular rules for ports, programs, protocols, and IP ranges.
What to check if firewall settings do not look right
If you find unexpected results while checking firewall settings, review these common causes:
- Wrong profile active: A network may be set to Public instead of Private.
- Third-party security software: Another firewall product may be controlling traffic.
- Group Policy restrictions: In business environments, policy may override local settings.
- Disabled notifications: You may not see prompts even though the firewall is blocking traffic.
- Custom rules: A specific inbound or outbound rule may be allowing or blocking access.
If a work-managed device behaves differently from your home PC, policy enforcement is often the reason.
On enterprise devices, check with your IT administrator before making changes.
Best practices for reviewing firewall status
Checking firewall settings is more effective when you use a consistent routine.
Focus on the active profile, the firewall state, allowed apps, and any recent changes to software or network configuration.
- Keep the firewall turned on for all profiles unless you have a clear reason not to.
- Use the Private profile only on trusted networks.
- Review allowed apps after installing new software.
- Confirm that inbound rules are limited to what is necessary.
- Use PowerShell or Advanced Security when troubleshooting persistent issues.
If you are trying to identify why a device cannot access a shared folder, remote service, or web application, checking the firewall should be one of the first steps.
It often reveals whether the problem is caused by the local machine, the network profile, or a rule created by software or policy.
Windows versions and interface differences
The exact labels can vary slightly across Windows 10 and Windows 11, but the core locations remain the same.
Windows Security is the primary modern interface, Control Panel remains available for compatibility, and PowerShell provides the most precise view for administrators.
If you are using Windows Server, the same firewall concepts apply, but the management tools may be accessed through Server Manager, Group Policy, or PowerShell depending on the role and configuration of the server.
Quick reference for checking firewall settings
- Fastest visual check: Windows Security > Firewall & network protection
- Classic interface: Control Panel > Windows Defender Firewall
- Most detailed command: PowerShell
Get-NetFirewallProfile - Legacy command line:
netsh advfirewall show allprofiles - Rule-level troubleshooting: Windows Defender Firewall with Advanced Security
These methods give you a complete picture of how Windows Firewall is configured and whether it is likely affecting network access.