Windows Firewall blocks inbound traffic by default and allows nearly everything outbound. Closing that gap for one program is four clicks.
Create an **outbound rule** for the program's exe and set it to **Block**. The app keeps working locally; anything that needs the network fails fast instead of silently phoning home.
The name in Task Manager is not always the file that connects. Open the file location from the process list, or check the shortcut target.
Task Manager > Details > right-click the process > Open file locationThe advanced firewall console separates inbound and outbound rules. A program rule applies to every port, which is what you want for a single executable.
wf.msc > Outbound Rules > New Rule > ProgramBlock wins over allow on the same profile. The rule applies to domain, private and public networks unless you untick a profile.
Many suites launch a separate updater or crash reporter with its own exe. The rule only matches the one file; add the others explicitly or the app still reaches out.
Trigger the feature that needs the internet. A blocked app fails quickly; an app that hangs was probably allowed through a different path.
A security suite with its own firewall overrides the Windows rules. The block must be created in that product instead.
A helper exe or a service running as system. Add each one.
It needs a licence check online. Allow the specific port or the vendor's domain.
A suite reset the rules or the program was reinstalled to a new path.
That is the trade. Unblock the updater and keep the telemetry blocked.
No. It stops that program from using the network at all.
Only do it for third-party apps. Blocking system components breaks updates and time sync.
Disable or delete the outbound rule in **wf.msc** under Outbound Rules. Network access for that program returns immediately.
Free · no account needed · tracks your progress