Allow one trusted app through Windows Firewall safely

When an app cannot receive the traffic it needs, turning off the entire Windows firewall is a large and usually unnecessary change. Windows can allow a named application instead. Even that is an exception, so identify the app and the network where it should work.

Before you start​

Confirm the app came from its official publisher and determine whether the problem occurs on a trusted home network, a public network or both. If a service uses only outbound traffic, a new inbound exception may not be needed.

Do it step by step​

1. Open Windows Security → Firewall & network protection and confirm the firewall is on for the active network. Note whether that network is marked Private or Public.
2. Select Allow an app through firewall, then Change settings if you are authorized to do so. Locate the exact executable or publisher entry, not a similar-looking name.
3. Allow the app only on the network type needed. For a home file-sharing tool, Private may be appropriate; Public on a café network usually is not.
4. If the app is absent, use Allow another app to select its official executable path. Do not add a broad port rule based solely on a forum comment or a pop-up's request.
5. Test the feature from the intended network. If it fails, inspect the app's own settings and vendor guidance before expanding the exception. Remove the firewall entry when you uninstall the app.

Check the result​

The feature should work with the firewall still on. Revisit the allowed-app list and confirm that Public was not selected unnecessarily.

If something goes wrong​

If Windows blocks the change on a work PC, ask IT. A firewall exception cannot repair a remote service outage or bad credentials; verify those separately.

Know the limit​

Microsoft says an allowed app is generally less risky than an open port because a port remains available until closed. Neither choice proves the application itself is safe. Microsoft's firewall exception guidance