How to Block Network Access for an App on Windows 10

Sometimes an app on your PC behaves like that one friend who cannot stop texting: it keeps checking for updates, syncing data, calling home, downloading extras, or quietly using your bandwidth while you are trying to do something important. The good news is that Windows 10 gives you a built-in way to tell a specific program, “No internet for you.” No dramatic uninstall. No unplugging the router. No wrapping your laptop in aluminum foil like a conspiracy burrito.

This guide explains how to block network access for an app on Windows 10 using Windows Defender Firewall with Advanced Security. You will learn how outbound rules work, how to pick the correct app file, how to block the connection, how to test the rule, and what to do when the app still sneaks online like it has a tiny digital fake ID.

The main keyword here is simple: how to block network access for an app on Windows 10. But the real goal is even simpler: take control of which programs can connect to the internet, reduce unwanted background traffic, improve privacy, and stop specific apps from communicating online when you do not want them to.

Why Block an App from Accessing the Internet?

Blocking an app’s network access is not only for IT professionals, cybersecurity fans, or people who read router manuals for fun. Regular Windows 10 users do it for practical reasons every day.

Common Reasons to Block App Internet Access

You may want to block an app from the internet if it constantly checks for updates, shows online ads, syncs data you do not want synced, uses too much bandwidth, or communicates with servers you do not recognize. Some people block older software to prevent automatic updates that break compatibility. Others block games or launchers to avoid interruptions, background downloads, or login prompts.

Parents may want to block a game from connecting online while still allowing it to run locally. Small business users may want to stop a tool from sending data outside the company network. Privacy-focused users may simply want fewer apps phoning home. Whatever the reason, Windows 10 provides a reliable built-in option through Windows Defender Firewall.

Important: Use Outbound Rules, Not Just the Allowed Apps List

Before we jump into the steps, there is one detail that saves a lot of confusion: to stop an app from reaching the internet, you usually need an outbound firewall rule.

The “Allow an app through firewall” screen in Windows 10 is useful, but it mostly deals with whether apps are allowed to receive certain network traffic on private or public networks. That is helpful for multiplayer games, file sharing, remote desktop tools, and apps that need incoming connections. However, if your goal is to stop a program from sending data out to the internet, the better tool is Windows Defender Firewall with Advanced Security.

Think of it this way: inbound rules control who can knock on your app’s door; outbound rules control whether your app is allowed to leave the house. If an app keeps going online, you want to lock the outgoing door.

Before You Start: Find the App’s Executable File

Windows Firewall blocks programs based on their executable file, usually an .exe file. That means you need to know the exact file path of the app you want to block.

Where Apps Are Usually Installed

Most traditional desktop programs are installed in one of these folders:

• C:Program Files
• C:Program Files (x86)
• C:UsersYourNameAppDataLocal
• C:UsersYourNameAppDataRoaming

For example, if you want to block a photo editor, browser, game launcher, or media app, you need to locate its main .exe file. Right-click the app shortcut, choose Open file location, and then right-click the shortcut again if needed to find the actual executable. Windows shortcuts can be a little sneaky; they are often just signs pointing to the real program.

Example: Blocking a Game Launcher

Suppose you want to block a game launcher from downloading updates automatically. The executable might be located somewhere like:

C:Program FilesGameLauncherGameLauncher.exe

Write down or copy that path. You will need it when creating the firewall rule.

How to Block Network Access for an App on Windows 10

Now let’s get to the main event: creating a Windows Defender Firewall rule that blocks a specific app from connecting to the internet.

Step 1: Open Windows Defender Firewall with Advanced Security

Press Windows + R on your keyboard to open the Run box. Type:

wf.msc

Then press Enter. This opens Windows Defender Firewall with Advanced Security, the classic advanced firewall console in Windows 10.

You can also find it through the Start menu by searching for Windows Defender Firewall, opening it, and selecting Advanced settings on the left side.

Step 2: Select Outbound Rules

In the left sidebar, click Outbound Rules. This section controls traffic leaving your computer. Since you want to stop an app from accessing the internet, this is exactly where you need to be.

Do not panic when you see a long list of existing rules. Windows has many built-in rules for system services and installed apps. You are not breaking into a nuclear submarine. You are just adding one new rule.

Step 3: Create a New Rule

On the right side, under the Actions panel, click New Rule…. The New Outbound Rule Wizard will appear.

Choose Program and click Next. This tells Windows that the rule applies to a specific application rather than a port, protocol, or predefined Windows feature.

Step 4: Choose the App’s EXE File

Select This program path, then click Browse. Navigate to the app’s executable file and select it.

For example:

C:Program FilesExampleAppExampleApp.exe

Click Next. Be careful here: choosing the wrong executable is the most common reason a firewall rule does not work. Some apps have multiple .exe files, such as a launcher, updater, helper service, crash reporter, or background sync tool. If the app still connects after you block the main file, you may need to create additional rules for related executables.

Step 5: Select “Block the Connection”

On the Action screen, choose Block the connection. Then click Next.

This is the moment when Windows puts up the tiny digital stop sign. The app may still open, but its outbound network traffic should be blocked by the firewall rule.

Step 6: Choose Network Profiles

Windows will ask which profiles the rule should apply to:

• Domain: Used on workplace or school domain networks.
• Private: Used for trusted home or office networks.
• Public: Used for coffee shops, airports, hotels, and other untrusted networks.

For most users, select all three: Domain, Private, and Public. This ensures the app is blocked no matter where your PC connects.

If you only want the app blocked on public Wi-Fi, select Public only. If you only care about your home network, select Private. But if you want a clean, consistent block, all three is the safest choice.

Step 7: Name the Rule Clearly

Give the rule a clear name, such as:

Block ExampleApp Internet Access

You can also add a description, like:

Blocks outbound network access for ExampleApp.exe

Click Finish. Your new outbound rule is now active.

How to Test Whether the App Is Actually Blocked

After creating the rule, open the app and check whether it can still access the internet. Try features that require an online connection, such as signing in, checking for updates, loading online content, syncing files, or downloading templates.

If the app shows a connection error, refuses to update, or cannot load online features, the rule is probably working. Congratulations: you have successfully put the app in airplane mode without putting your whole PC in airplane mode.

Use Task Manager or Resource Monitor

You can also use built-in Windows tools to check network activity. Open Task Manager with Ctrl + Shift + Esc, go to the Processes tab, and look at the Network column. For more detail, open Resource Monitor, go to the Network tab, and look for the app’s process.

If the app is still sending or receiving data, it may be using another executable or background service. In that case, repeat the firewall rule process for the related .exe files.

What If the App Still Connects to the Internet?

Sometimes an app is more complicated than it looks. Many modern programs use several background components. Blocking the obvious .exe may not be enough.

Check for Updaters and Helper Services

Look inside the app’s installation folder for files with names like:

• updater.exe
• service.exe
• helper.exe
• launcher.exe
• sync.exe
• crashreporter.exe

Create separate outbound block rules for each file if needed. This is especially common with game launchers, cloud storage tools, creative software, messaging apps, and programs that run background services at startup.

Restart the App or Reboot Windows

Some apps keep existing network sessions open. Close the app completely, including any tray icon near the clock. If you are not sure whether it is fully closed, restart Windows. After rebooting, test the app again.

Check Third-Party Security Software

If you use antivirus or internet security software with its own firewall, it may override or replace Windows Defender Firewall controls. In that case, you may need to create the block rule inside that security suite instead of Windows Defender Firewall.

Confirm the Rule Is Enabled

Return to Windows Defender Firewall with Advanced Security, click Outbound Rules, and find your rule. Make sure it is enabled. If the rule is disabled, right-click it and choose Enable Rule.

How to Temporarily Disable or Remove the Block

If you later want the app to access the internet again, you do not need to delete everything in a panic. You have two simple options.

Option 1: Disable the Rule

Open wf.msc, go to Outbound Rules, find the rule, right-click it, and select Disable Rule. This keeps the rule saved but turns it off. It is perfect if you want to block the app most of the time but allow occasional updates.

Option 2: Delete the Rule

If you no longer need the rule, right-click it and choose Delete. The app will return to normal network behavior unless another firewall rule blocks it.

Blocking Microsoft Store Apps on Windows 10

Traditional desktop programs are usually easy to block because you can point the firewall rule to a specific .exe file. Microsoft Store apps can be more annoying because they live in protected Windows app folders and may not behave like classic desktop software.

For many Store apps, Windows Defender Firewall may still show package-based entries or related executable paths, but finding the right target can be less obvious. If the app appears in the firewall list, you can remove its allowed access or create more specific rules where possible. If not, you may need to use app settings, privacy permissions, background app controls, or a third-party firewall interface that makes per-app control easier.

For most users, the easiest path is still this: identify the executable or background process, create an outbound block rule, test it, and repeat for any helper processes.

Should You Block Inbound Rules Too?

Usually, blocking outbound access is enough when your goal is to stop an app from reaching the internet. However, you may also block inbound access if you want to prevent other devices or servers from initiating connections to that app.

To do that, repeat the same process under Inbound Rules. Choose Program, select the same executable, choose Block the connection, apply it to the profiles you want, and name the rule clearly.

For example, if you are blocking a local server tool, remote control app, multiplayer game, or file-sharing program, creating both outbound and inbound rules may make sense. For a normal app that simply checks for updates or loads online content, outbound blocking is usually the main piece.

Best Practices for Blocking App Network Access

Name Your Rules Like a Human

Do not name a rule “test1” unless you enjoy confusing your future self. Use clear names like Block Spotify Outbound, Block GameLauncher Internet, or Block ExampleApp Updater. Six months later, you will thank yourself.

Block Only What You Understand

Be careful when blocking Windows system files or services. Blocking the wrong Windows process may break updates, activation, Microsoft Store downloads, time synchronization, network discovery, or other features. If you are not sure what a process does, research it before blocking it.

Keep the Firewall Turned On

Turning off the entire firewall to solve one app problem is like removing your front door because one key is annoying. Keep Windows Defender Firewall enabled and use specific rules instead. A targeted rule is cleaner, safer, and easier to reverse.

Remember That Updates Can Change File Paths

Some apps install updates into new folders or version-numbered directories. When that happens, your old firewall rule may point to an outdated executable. If an app suddenly gets online again after an update, check whether the file path changed and create a new rule.

Practical Examples

Example 1: Block a Program from Auto-Updating

Let’s say you use an older design tool that works perfectly, but every update breaks your workflow. You can block the main app executable and its updater executable. The app still opens, but it cannot check online for updates.

Example 2: Block a Game from Online Features

If a game works offline but keeps launching online services, block the game executable and the launcher. This can reduce background traffic and prevent unwanted online login prompts.

Example 3: Block a Media App from Loading Ads

Some free apps load promotional content from the internet. Blocking the app may stop online content from appearing, although it can also break legitimate features. Test carefully and disable the rule if the app becomes unusable.

Common Mistakes to Avoid

Mistake 1: Blocking the Shortcut Instead of the EXE

A shortcut is not the actual program. If you block a shortcut path, the rule will not work. Always locate the real .exe file.

Mistake 2: Creating an Inbound Rule Only

If you only create an inbound rule, the app may still connect outward. For blocking internet access, start with an outbound rule.

Mistake 3: Forgetting Public, Private, or Domain Profiles

If you apply the rule only to Private networks, the app may connect when you are on Public Wi-Fi. Select all profiles if you want the block to apply everywhere.

Mistake 4: Ignoring Helper Processes

Many apps use more than one process. If the app still connects, look for updaters, launchers, services, and background sync tools.

Experience-Based Notes: What Actually Happens When You Block Apps on Windows 10

After using Windows Defender Firewall rules across many everyday Windows 10 setups, one thing becomes clear: blocking network access for an app is simple in theory, but the little details matter. The most common “why is this not working?” moment happens when the wrong executable is selected. Many people right-click a desktop shortcut, copy its path, and assume the job is done. But shortcuts are often just launch buttons. The real app may live deeper inside Program Files, Program Files (x86), or the user’s AppData folder.

Another real-world lesson is that apps have become very modular. A single program may include a main app, a launcher, an updater, a helper service, a crash reporter, and a background sync process. Blocking only the main executable may stop visible online features, but the updater might still contact servers quietly. This is especially common with game clients, cloud software, messaging tools, and creative apps. When an app keeps connecting after you create a rule, do not assume Windows Firewall failed. More often, the app is using a different process.

Testing also matters. A firewall rule should be tested immediately after creation. Open the app, try to sign in, check for updates, load online content, or use whatever feature normally requires the internet. If everything still works online, check the rule path and confirm that it is enabled. Then restart the app completely. Some programs minimize to the system tray instead of closing, so click the small arrow near the Windows clock and exit the app from there. A full reboot is sometimes the cleanest test because it clears old sessions and starts the app fresh.

It is also wise to create rule names that make sense. A firewall list can become messy fast. A name like Block VideoEditor Outbound is much better than Rule 47. When you return later to allow an update, troubleshoot a connection issue, or remove a rule, clear naming saves time and prevents accidental changes to unrelated rules.

One more practical point: blocking network access is not the same as uninstalling an app or making it safe. If you think a program is malicious, blocking its internet access is only a temporary containment step. You should still scan your PC, remove suspicious software, check startup entries, and avoid running files you do not trust. A firewall rule is a seatbelt, not a mechanic.

Finally, blocking an app can have side effects. Some apps need online access for license checks, cloud saves, templates, fonts, maps, collaboration, or activation. If a program suddenly becomes slow, throws login errors, or refuses to open after you block it, disable the rule and test again. The best approach is not to block everything randomly. Block with a purpose, test the result, and keep notes. Windows 10 gives you strong control, but like any good tool, it works best when used carefully.

Conclusion

Learning how to block network access for an app on Windows 10 is one of those small skills that makes your PC feel more under your control. Instead of letting every program connect whenever it wants, you can use Windows Defender Firewall with Advanced Security to create targeted outbound rules. The process is straightforward: find the correct executable, create a new outbound program rule, choose Block the connection, apply it to the right network profiles, and test the result.

The most important thing is precision. Block the correct .exe, watch for helper processes, and name your rules clearly. If an app still connects, investigate whether it uses an updater, launcher, or background service. If something breaks, disable the rule and adjust. No drama, no router wrestling, and no need to turn off your whole firewall.

Windows 10 already includes the tools you need. You just have to know where they are hiding. And now you do.