Some multiplayer games refuse to connect, host lobbies, or let friends join, and the quiet culprit is often Windows Firewall silently blocking the game’s traffic. Adding an exception — whitelisting the game — tells the firewall to allow its connections through. It is a safe, targeted change that is far better than disabling the firewall entirely. Here is how to do it properly on Windows.
When firewall blocking is the problem
Typical symptoms are a game that loads fine but times out in matchmaking, cannot host, blocks direct joins, or throws connection errors only for online modes. If single-player works but multiplayer does not, and your NAT and router are fine, the firewall is a prime suspect — especially right after installing a game or a major update that added a new executable.
Let Windows prompt you
The first time a game needs network access, Windows usually pops a Security Alert asking whether to allow it. Always allow both private and public networks for games you trust, and the exception is created automatically. Problems arise when you dismissed that prompt by accident or clicked Cancel — then you must add the rule by hand.
Add the exception manually
Open the Start menu, search for Allow an app through Windows Firewall, and open it. Click Change settings, then Allow another app, browse to the game’s executable, and add it. Make sure both the Private and Public checkboxes are ticked so it works on any network type. If the game uses a separate launcher or anti-cheat service, add those executables too.
| Step | Action |
|---|---|
| 1 | Open “Allow an app through Windows Firewall” |
| 2 | Click Change settings, then Allow another app |
| 3 | Browse to the game’s .exe and add it |
| 4 | Tick both Private and Public |
| 5 | Repeat for the launcher and anti-cheat |
Find the right executables
Games are not always a single file. A launcher may start the actual game as a separate process, and competitive titles run an anti-cheat service that also needs the network. Right-click the game in your library, use the “browse local files” option, and note the main executable plus any launcher or service files. Whitelisting all of them avoids the frustrating situation where the game partly connects but multiplayer still fails.
Avoid the nuclear option
Disabling Windows Firewall entirely will make the game work, but it exposes your whole PC to unsolicited connections — a bad trade for convenience. Targeted whitelisting achieves the same result for that one game while leaving your defenses up everywhere else. If you also run a third-party security suite, it may have its own firewall you need to whitelist the game in as well.
Verify inbound and outbound rules
Windows Firewall keeps separate inbound and outbound rules, and multiplayer often needs both. Most games work with the default outbound-allowed policy, but hosting a lobby or accepting direct joins depends on inbound rules that your exception creates. If a game connects to matches but friends cannot join yours, focus on the inbound side: confirm the rule exists, is enabled, and is not restricted to a single network profile. You can review every rule in the Windows Defender Firewall with Advanced Security console, where you can spot a duplicate or a blocking rule that overrides your allow rule — Windows applies the most restrictive matching rule, so one stray block entry can defeat an allow. Deleting stale rules from an old install of the same game keeps the list clean and prevents these silent conflicts.
FAQ
Is it safe to allow a game through the firewall?
Yes, for games from legitimate sources it is perfectly safe and is exactly what the exception system is designed for. You are allowing one trusted program to communicate, not opening your PC to everything.
Why did multiplayer stop working after a game update?
Updates sometimes change or add executables, and the old firewall rule no longer matches. Re-add the current executable through the firewall settings, including any renamed launcher or anti-cheat files the update introduced.
Bottom line
If multiplayer fails while single-player works, whitelist the game rather than killing your firewall. Add the main executable plus its launcher and anti-cheat, tick both Private and Public, and re-check the rule after big updates. It is a two-minute fix that keeps you both connected and protected.
