Allow an App Through Windows Firewall on Windows 10 and 11

To allow an app through Windows Firewall, open Windows Security, select **Firewall & network protection**, choose **Allow an app through firewall**, and enable the verified app on the required network profile. Allow it on **Private** networks whenever possible; enable **Public** access only when the app genuinely needs it. Do not turn off the firewall: create the narrowest exception that fixes the connection, then test it.

Before you allow the app, check what access it actually needs

First confirm that Windows Firewall is the likely cause. Check whether the app fails to connect while Windows Firewall is enabled, and look for a Windows Security notification saying that Windows Defender Firewall blocked an app. A failed connection can also result from the app’s settings, an offline service, a proxy, a router, or another security product.

You will need:

• Windows 10 or Windows 11
• The app’s name and, ideally, its executable file (.exe)
• An administrator account, or access to someone who can approve the change
• The current network profile: Private or Public

To identify the executable, open the app, press Ctrl + Shift + Esc to open Task Manager, select the app under the Processes tab, right-click it, and choose Open file location. Confirm that the file belongs to the software publisher you expect. Do not approve a random executable because its name resembles the app’s name.

You can also right-click the app’s shortcut, select Properties, and inspect the Target field. If the app updates itself, its executable may be inside a versioned folder. Make sure the path points to the current installation rather than an old copy.

Check the network profile before changing the rule:

1. Open Settings.
2. Select Network & internet.
3. Select Wi-Fi or Ethernet, then select the connected network. Windows shows its profile as Private or Public.

A home or trusted work network is usually Private. Hotel, airport, café, school, and other shared networks should normally remain Public.

How to allow an app through Windows Firewall in Windows 10 or 11

Windows Security provides the quickest supported route. The wording is nearly the same in Windows 10 and Windows 11.

1. Open Windows Security from the Start menu.
2. Select Firewall & network protection. Windows displays the active network and available firewall profiles.
3. Select Allow an app through firewall. This opens the permitted-app list in Control Panel.
4. Select Change settings. Approve the User Account Control prompt if Windows requests administrator permission.
5. Find the app in the list, then select its checkbox under Private, Public, or both. Leave the other network type unchecked unless the app needs access there.
6. Select OK. Windows saves the exception.

To open the same page through Control Panel:

1. Open Control Panel.
2. Select System and Security, then Windows Defender Firewall or Windows Defender Firewall with Advanced Security, depending on the view and Windows version.
3. Select Allow an app or feature through Windows Defender Firewall.
4. Select Change settings, approve the administrator prompt, and select the app’s network profile.
5. Select OK.

If the app is not listed:

1. Select Allow another app.
2. Select Browse and locate the correct executable.
3. Select Open, then Add.
4. Select Private or Public for the new entry.
5. Select OK.

Add the executable that actually makes the network connection. Allowing a desktop shortcut or an unrelated launcher will not fix the connection. If Allow another app is unavailable, see “What to do if Windows will not let you allow the app” below.

Should you check Private, Public, or both networks?

Select Private when the app only needs to work on a trusted home or workplace network. Windows applies the exception only while the current network has a Private profile, which limits exposure on unfamiliar networks.

A Public exception applies on networks where other devices may be present and untrusted. Depending on the app, the rule may allow incoming network traffic that other devices could try to reach. That does not automatically make the computer unsafe, but it increases the attack surface. Do not enable it for convenience alone.

Use this rule of thumb:

Some apps need a firewall exception only for local-network features such as file sharing, device discovery, remote control, or multiplayer hosting. Internet access alone does not always mean the app needs to accept connections from other devices. If the app works with Private selected, do not also select Public as a precaution. Keep the narrower rule.

Test the app, then remove the exception if it was not needed

After saving the exception, close and reopen the app. Repeat the action that failed, such as loading content, connecting to a service, or joining a session. If it works, the exception may have addressed the problem, although another change made at the same time can also affect the result.

If the app still fails, do not keep adding broader permissions. Check that you selected the correct executable, that the app is using the network profile you allowed, and that another firewall or security product is not blocking it. Confirm that the service is online and that the app does not require a proxy, VPN, separate login, or outbound rule.

To remove the exception later:

1. Open Windows Security.
2. Select Firewall & network protection.
3. Select Allow an app through firewall.
4. Select Change settings and approve the administrator prompt.
5. Clear the app’s Private and Public checkboxes, or select the app and choose Remove if that option is available.
6. Select OK. The app no longer has the permitted-app exception.

If the app no longer appears in the permitted-app list, the exception may already have been removed. For a more specific rule created through Advanced settings, open Windows Defender Firewall with Advanced Security, inspect Inbound Rules, locate the rule associated with the app, right-click it, and choose Delete. Only delete a rule after confirming that it belongs to the app.

What to do if Windows will not let you allow the app

A missing Change settings button, a disabled Allow another app button, or a prompt requesting credentials usually means you are not running with administrator rights. Sign in with an administrator account or ask the device administrator to make the change. On a work or school computer, policy may deliberately prevent users from adding firewall exceptions.

If the app is not listed, do not choose a similarly named program at random. Use Task Manager or the shortcut’s Properties to find the executable, then add it with Allow another app. Some apps use more than one executable, especially launchers and games. The publisher’s support documentation can identify which component needs network access.

If Windows Security shows the exception but the app still cannot connect, check for third-party antivirus, endpoint-security, VPN, or firewall software. These products can filter traffic separately, so changing Windows Firewall will not override their rules. Do not disable all security software as a first step; inspect its application or network protection settings instead.

The permitted-app list mainly controls Windows Firewall’s application access rules, commonly for inbound traffic. A separate outbound rule can still block a connection. Open Windows Defender Firewall with Advanced Security, select Outbound Rules, and look for a rule that explicitly blocks the app or its executable. Do not delete a managed rule on a work device without approval. If no block exists, the failure is likely outside this particular firewall exception.

Conclusion

Allow the verified executable on a **Private** network first, then test the app while it is connected to the profile you selected. If the connection still fails, check the app, network, and other security software instead of repeatedly broadening the rule. When the app no longer needs access, clear its **Private** and **Public** permissions or remove its firewall rule.

Frequently Asked Questions

Should I turn off Windows Firewall instead?

No. Turning off the firewall removes protection for other apps and services as well. Add a narrow exception for the correct executable and network profile instead.

Why can an app work on Private networks but not Public networks?

Windows applies separate permissions to each network profile. If only **Private** is checked, the app’s permitted traffic is blocked while the computer is connected to a **Public** network. Enable **Public** only if the app truly needs to work there.

Can I allow an app through the firewall without administrator access?

Usually not. Changing permitted apps requires administrator approval, and a work or school device may also be controlled by organizational policy. Ask the administrator to review and add the exception.