How to Block an App With Windows Firewall in 5 Minutes

5 min read

Windows Firewall can stop a single app from reaching the internet without affecting anything else. Blocking an app this way is useful when a program phones home too often, a game shows ads, or an old tool keeps trying to update itself. You do not need extra software, and the change takes five minutes.

This guide shows how to create an outbound firewall rule that blocks one app, how to check that it works, and how to undo it when you change your mind.

Why Block a Single App

Some apps call home more than they should. A simple tool may check for updates every few minutes, upload usage data, or show ads fetched from the internet. Blocking its internet access stops that traffic while the app keeps working offline. The whole job takes about 5 minutes.

Games are a common case. A single-player game does not need the internet, but it may still show ads or sync data in the background. Blocking the game executable keeps it fully offline, which also stops surprise downloads during play.

Old software is another reason. A program that no longer receives updates may try to reach a dead server, or worse, a server that now belongs to someone else. Blocking it removes the risk without uninstalling a tool you still use.

Blocking an app is also a good test. If a problem disappears when you block an app, the app network activity was the cause. Firewall rules make a clean on-and-off test for suspicious behavior.

Finding the App Executable

Every firewall rule points at one executable file, the program that actually runs. Find it by right-clicking the app shortcut and choosing Open file location, or by searching for the app name in File Explorer.

Some apps use a launcher that starts a second program. A game launcher, for example, opens the game executable from a subfolder. Block the executable that does the network activity, which is usually the game itself, not the launcher, unless you want to block both.

Apps from the Microsoft Store are harder to find, because they live in a hidden system folder. For Store apps, note the package name from the app settings, or use the firewall option that blocks by app package instead of by file path.

Copy the full path of the executable before you start. You will paste it into the firewall rule, and a typo means the rule blocks nothing. Double-check the path character by character, including the drive letter.

Creating the Outbound Rule

Open Windows Defender Firewall with Advanced Security from the Start menu. This is the advanced firewall console, not the simple settings page. In the left pane, click Outbound Rules, then click New Rule in the right pane to start the wizard.

Choose Program as the rule type, then paste the full path of the executable. On the next page, choose Block the connection. This tells the firewall to drop all outgoing traffic from that program, while leaving incoming traffic and other programs alone.

On the profile page, tick all three profiles: Domain, Private, and Public. An app can run on any network, and ticking all three makes sure the block applies at home, at work, and on public Wi-Fi. Leaving one profile unticked leaves a hole the app can use.

Give the rule a clear name, such as Block followed by the app name. A clear name lets you find the rule later when you want to change or delete it. Click Finish, and the rule takes effect immediately without a restart.

Testing That the Block Works

Test the app right away. Open the blocked app and try the feature that uses the internet, such as checking for updates or loading an online feed. The feature should fail, while the offline parts of the app keep working normally.

Check the firewall log if you want proof. Enable logging in the firewall properties, then look for dropped packets from the app executable. A log entry with the app name and the word DROP confirms the rule is catching its traffic.

If the app still reaches the internet, check whether it uses a second executable. Some apps run a helper or updater process with its own file. Open Task Manager, look for the app processes, and block the helper executable too.

Some apps use a background service instead of the main program. A service runs under a different name and may need its own rule.

Removing or Changing the Rule

To unblock an app, open the firewall console, find the rule by name, and delete it or disable it. Disabling keeps the rule for later, while deleting removes it completely. The app regains internet access as soon as the rule is gone, with no restart needed.

To block only one direction, create a matching inbound rule. Outbound rules stop the app from sending data out, which covers most cases.

Review your custom rules once in a while. Rules accumulate, and a rule you forgot can block an app you now want online. A yearly review of the outbound rules list keeps the firewall tidy and avoids mystery connection failures.

Never block Windows system processes unless you know exactly what they do. Blocking a core service can break updates, time sync, or activation. Limit your custom rules to apps you installed yourself, and leave system components alone.

More ideas, fewer dead ends: the related guides below continue this thread, beginning with Firewall Blocking Internet: Troubleshooting & Solutions.

What is your take?

Share your experience or questions in the comments — especially if you have used this tech yourself.

Found this useful? Share it with a friend who would want to know.