Windows VPN split tunneling lets you choose which traffic uses a VPN and which traffic connects through your regular network. For an app-based setup, that usually means selecting programs in the VPN client rather than changing a Windows-wide setting. The exact controls depend on the client: some let you include selected apps in the tunnel, others let you exclude selected apps, and some offer only destination-based routing. Before changing anything, identify which type your software supports, then test each rule with the same program you configured.
What split tunneling means on Windows
With a full-tunnel VPN, the client attempts to route most or all eligible device traffic through the VPN connection. With split tunneling, traffic takes different paths according to a rule. In an app-based setup, the rule is associated with a program or app identity: selected traffic uses the VPN, while other traffic continues through the ordinary network connection. This can be useful when a work tool needs a VPN but a local printer, a game, or another service works better without it.
There are two common rule styles. Include mode sends only the apps you choose through the VPN; other apps use the normal connection. Exclude mode sends traffic through the VPN by default and makes exceptions for apps you choose. The names and default behavior vary, so read the client’s description carefully. A list labeled “bypass VPN” is usually an exclusion list, while “only these apps use VPN” describes inclusion.
App routing is not the same as domain-based or destination-based routing. A domain rule can affect requests to a particular website across several apps, while an app rule is intended to follow traffic from a selected program. Windows’ built-in VPN controls can also work with routes to destination networks, but that is not automatically an app-by-app rule. A route to a network does not mean “send only this browser through the VPN.”
Implementation matters. A VPN client may use Windows filtering components, a virtual network adapter, or another supported mechanism to identify and route traffic. Some programs launch helper processes, use services running in the background, or change executable files during an update. As a result, a rule for the main application window may not cover every connection the software makes. Consider the rule a routing policy to verify, not a guarantee based solely on a checkbox.
Check client support before adding rules
Open the VPN client’s settings and look for terms such as split tunneling, app routing, per-app VPN, included apps, or bypass VPN. The option may sit under connection, network, advanced, or security settings. If you cannot find an app list, check the client’s help page or its built-in documentation before trying to imitate the feature with Windows firewall rules. Firewall rules can allow or block traffic, but they do not by themselves create a reliable second network route.
Check the supported app types as well. A client might list desktop executable files but not Microsoft Store apps, packaged apps, or background services. It may require you to browse to an executable instead of selecting a friendly app name. If an app has a launcher and a separate game or work-process executable, determine which process makes the network connections. A rule for the launcher may only affect its update check, not the application it starts.
Also check how the client handles DNS, IPv6, local network access, and its kill switch. DNS requests may be handled by a system service rather than by the visible app, and a rule that routes application traffic may not make every name lookup follow the same path. A kill switch may block traffic that leaves the VPN, including apps intended to bypass it, or it may have a separate setting for those apps. Do not assume that “bypass” means an app remains online if the tunnel disconnects.
Before editing settings, note the current mode and list. If you are configuring a work device, follow your organization’s policy; centrally managed VPN settings can override local choices. On a personal device, close programs you plan to change, make one rule at a time, and keep the VPN client’s default or reset option in mind. That gives you a clear way back if the change produces unexpected behavior.
- ✅ Confirm whether the client supports app inclusion, app exclusion, or only destination routes.
- ✅ Check whether the target is a desktop program, packaged app, service, or launcher.
- ✅ Read how the client treats DNS, IPv6, local network traffic, and the kill switch.
- ❌ Do not run two VPN clients at once to try to make separate app rules.
Set app-routing rules in the VPN client
The labels differ between Windows clients, but the procedure follows a consistent pattern. First connect to the VPN normally and confirm that the client reports an active connection. Then open its split-tunneling or app-routing page. Select the intended mode before adding programs: choose inclusion if only a small set of apps should use the VPN, or exclusion if nearly everything should use it except a known set of exceptions. Choosing the wrong mode can make a correct-looking app list behave in the opposite way you expect.
Add one program and use the client’s app picker where available. If you must browse for a file, choose the executable that actually makes the connections, not just a shortcut or installer. A shortcut points to an application but is not normally the process used for routing. If the program uses a launcher, helper, or separate service, consult the client’s guidance on whether those processes need separate entries. Avoid adding every executable in a program’s folder without understanding the effect; an overbroad list makes later troubleshooting difficult.
Save or apply the rule, then reconnect if the client asks you to. Some clients apply changes immediately; others rebuild their routing rules only after a disconnect and reconnect. Keep the selected VPN location and other connection settings unchanged while testing. If you alter the route, app list, and protocol at the same time, it becomes harder to tell which change caused a result.
If you use Windows’ built-in VPN connection rather than a third-party client, distinguish its split-tunneling setting from app selection. PowerShell can inspect a built-in profile and enable destination-based split tunneling, for example:
Get-VpnConnection | Select-Object Name, SplitTunneling
Set-VpnConnection -Name "ProfileName" -SplitTunneling $true
Replace ProfileName with the name of your existing profile. Depending on how the profile was created, you may need to run PowerShell with the relevant user permissions or use the corresponding all-user profile option. Enabling this setting does not select individual Windows programs. It changes how the built-in VPN handles routes; the destinations that should use the VPN must be configured as routes according to the profile and network design. If you need true per-app behavior, use a client or managed VPN configuration that explicitly supports it.
For personal browsing, a simple initial test is easier to interpret than a large policy. Put one known app in the intended list, leave the remaining settings unchanged, reconnect if necessary, and verify the result before adding more entries. Once that app behaves as expected, add the next rule and repeat the test. This staged approach also helps reveal whether a helper process or system service needs separate handling.
Verify each rule without relying on assumptions
Use the application itself to test its route. If you are routing a browser through the VPN, open an IP-check page in that browser and compare the displayed public address with the result from a browser that is meant to bypass the VPN. A browser result verifies that browser’s request, not every program on the computer. For a work app, test a normal sign-in or connection to the expected service and consult its connection diagnostics if available. Do not use a successful VPN status indicator as proof that every app follows the intended path.
Make comparisons under the same conditions. Keep the same Wi-Fi or Ethernet connection, VPN location, app version, and destination while checking the before-and-after behavior. If the app offers a connection log, note whether it shows the VPN adapter, a direct route, or a failed lookup. A public IP check can help distinguish the two paths, but it does not establish that DNS, IPv6, or every background connection is routed identically.
Check both sides of the policy. In inclusion mode, confirm that a selected app uses the VPN and that an unselected app follows the normal route. In exclusion mode, confirm that an excluded app bypasses the tunnel while an ordinary, non-excluded app still uses it. Repeat the check after reconnecting the VPN and after restarting the affected program; some clients do not apply a new rule to a process that was already open.
Windows can show useful context in Task Manager, the VPN client’s connection page, and the application’s own logs. These do not always expose the final route in a simple way, but they can reveal a mismatched process name, a helper executable that is not covered, or an app that is failing before it reaches the network. A local firewall, endpoint security product, proxy setting, or organization policy can also interfere, so do not immediately attribute every connection error to the VPN route.
When researching a compatible client or its setup, start with its official documentation and the Q9VPN homepage for the service’s available client information. Client menus and platform capabilities can change between versions; use instructions that match the Windows release and client build you have installed rather than copying a rule from a different operating system.
Troubleshoot common routing problems
The selected app still appears to use the normal connection. Check that the client is in inclusion mode if you intended to send only selected apps through the VPN. Confirm that you selected the executable making the request, not its shortcut or launcher. Close and reopen the app, reconnect the VPN, and test again. If the app uses a background service, ask the client’s documentation whether that service needs its own rule.
An excluded app cannot connect. Verify that the client is in exclusion mode and that the app appears in the bypass list. Review the kill-switch behavior, since some clients block direct traffic when the VPN is active or reconnecting. Also check whether the app depends on another process for DNS, authentication, updates, or media playback. If the client has a “local network” or “allow LAN” option, treat it separately: local network access and public internet bypass are different policies.
The app works until the VPN reconnects or the PC restarts. Some clients apply app rules only after the tunnel is re-established, and some rule lists can refer to a program path that changed after an update. Reopen the settings, confirm the entry is still present, and check whether the executable has moved or been replaced. Update the rule using the current supported application picker rather than adding a broad folder exception.
Only some features of an app fail. The main interface may work while sign-in, notifications, updates, or content loading fail because those functions use separate processes or network services. Check the app’s documentation and the VPN client’s logs for the process associated with the failed feature. Before changing DNS or firewall settings, test with the client’s app rules temporarily returned to their default state; changing several security controls at once can conceal the cause.
Connections fail when two networking tools are open. Disconnect and fully exit the other VPN or proxy client before testing. Multiple tools can compete to install routes, set DNS servers, or control traffic filtering. If you use a corporate VPN alongside a personal VPN, follow the organization’s approved configuration rather than forcing both to operate concurrently. Restarting Windows may clear stale connections, but it does not make incompatible routing policies compatible.
If the rule causes broad connectivity problems, remove the new entry or use the client’s reset-to-default control, disconnect, and reconnect. Confirm that ordinary browsing works before rebuilding the policy. If the client has an option to restore its original routing mode, use that instead of deleting drivers or editing unrelated system networking settings. Escalate to the client’s support channel or your administrator when a managed profile, security policy, or work network is involved.
Return to the default setup safely
To undo an app-based configuration, first open the client’s routing settings and remove the apps you added. If you changed the mode from full tunnel to inclusion or exclusion, restore the mode you originally used or select the client’s default option. Save the change, disconnect and reconnect the VPN, then close and reopen the affected programs. Check both a program that previously used the VPN and one that previously bypassed it.
For a Windows built-in VPN profile, inspect the profile’s split-tunneling state before changing routes. If you enabled split tunneling only for a test and want to return to the profile’s previous full-tunnel behavior, turn that setting off for the same profile:
Set-VpnConnection -Name "ProfileName" -SplitTunneling $false
This does not automatically remove custom routes that may have been added separately. Review the profile’s route configuration and remove only entries you created for the test, following the documentation for your Windows profile. Avoid deleting routes you do not recognize, especially on a managed device.
Finally, check that the client reports its expected connection state, the app list is back to the intended baseline, and the programs you tested can reach their normal services. Keep a short note of the original mode and any changed entries when experimenting. That small record makes it much easier to reproduce a working setup—or restore it—after a client update.
Frequently asked questions
Does Windows have a built-in switch to route any app through a VPN?
Not as a general-purpose app picker for every built-in VPN connection. Windows VPN profiles can use split tunneling and routes based on network destinations, while per-app behavior depends on a VPN client or managed configuration that supports it. Check the specific client’s documentation before assuming a Windows route setting will apply to one program only.
Should I include apps or exclude them?
Use inclusion when only a small, known set of apps should use the VPN and other traffic should remain on the normal connection. Use exclusion when the VPN should carry traffic by default but particular apps need a direct route. Confirm how the client defines each mode, then test an app from each side of the rule.
Why might a rule stop working after an app update?
An update can change an executable’s location or replace the process the client uses to identify the app. The app may also start using a helper or service for network activity. Recheck the rule in the VPN client, select the current supported executable or app identity, reconnect, and test the affected function again.
Does an excluded app always bypass the kill switch?
No. Kill-switch behavior differs by client, and some clients block direct connections even for apps listed to bypass the VPN. Read the client’s description of the interaction and test the behavior without relying on assumptions. If the device is managed by an organization, ask its administrator before changing that protection.