Before setting up a Windows VPN, understand the difference between the client, subscription and proxy mode: the client runs the connection, the subscription provides route settings, and proxy mode determines which apps use those routes. Installing the client alone does not activate it. First verify your browser and target apps, then configure startup.

This guide follows the actual setup sequence. Button names vary by client, so the steps refer to common menu options rather than assuming every app has the same interface. If a label differs, follow the client instructions provided in your account panel. Don’t download installers from unverified sources just to match this guide.

Before you begin: Check the client source and network

Disconnect any existing proxy and make sure you can access regular websites. If your local network is down, fix the connection first. Computers managed by an employer or school may restrict software installation, proxy changes or virtual network adapters. Follow your organization’s device and network policies.

After signing in through the VPNBody client portal, download the Windows client and get your subscription. You can create an account with a username and password—no email address required. Downloading the client and getting route settings are separate steps; available routes and traffic depend on your plan status in the portal.

  • ✅ Make sure the download link comes from the account panel or a project release page it explicitly links to.
  • ✅ Keep your account credentials safe, and add the subscription link only to your own client.
  • ✅ Quit other apps that control the system proxy to prevent conflicting settings.
  • ❌ Don’t share your full subscription link in public chats, online converters or unredacted screenshots.

Install the client: Choose the right architecture and check that it launches

  1. Check your system type. Open Windows Settings, go to System, then About, and check your system type. Choose the processor architecture specified on the release page. Don’t rely on “Windows” in the filename alone.
  2. Download and save the file. Use the link provided in your account panel. Follow the setup wizard for an installer. For a portable version, extract all files to a dedicated folder before launching it; don’t run it from the archive preview.
  3. Check security warnings. If Windows displays a security warning, verify the download source, publisher and any checksums or verification details on the release page. If you can’t confirm them, stop. Disabling system protection is not an installation step.
  4. Launch it for the first time. Open the app and confirm that its main window appears and its icon shows in the taskbar notification area. Closing the window may only minimize the app to the tray. To exit completely, use the tray menu’s Exit option.

System proxy features and virtual network adapters have different permission requirements. Elevate privileges only when the client documentation explicitly says to. Don’t run all network apps as an administrator long-term just to “make the connection more stable.” If enabling a virtual adapter prompts you to install a driver, verify the program’s source first.

If the main window opens, the installation check is complete. An empty route list usually means you haven’t imported a configuration yet; it doesn’t mean the installation failed. Continue with the subscription setup rather than reinstalling the client.

Import your subscription: Add routes to the client

A subscription link retrieves route settings and usually contains access credentials. It isn’t a regular information page or a webpage you should keep open in a browser. When copying the link, avoid adding spaces, quotation marks or line breaks. Don’t submit the full URL to untrusted sites for troubleshooting.

  1. Copy the compatible subscription from your account panel. If the options are grouped by client, choose the format for your app. For one-click import, make sure the link opens the correct client.
  2. Add a remote configuration in the client. Look for an option such as Configuration, Subscription or Subscription management. Choose import from URL, paste the link and save.
  3. Update and activate it. Wait for the update to finish, then check that a configuration name, routes or policy groups appear. Some clients require you to select the configuration to make it active.
  4. Check the result. If parsing fails, check the format and whether your client supports it. If the download times out, check whether your current network can reach the subscription URL before changing protocol settings.

Shadowsocks, VMess, Trojan, VLESS, Hysteria2 and TUIC are different proxy protocols, and not every client or core supports them all. Seeing a protocol name in a file doesn’t mean your current app can run it. Follow the service’s compatibility notes. Don’t try to create a “universal configuration” by changing ports, transport settings or certificate options yourself.

Choose a route: Pick a region, then check your traffic mode

After choosing a route in the current policy group, check that the proxy is enabled and review the routing rules. Beginners often assume that “route selected” means “all apps are connected.” The client may not control the system proxy, or only requests matching specific rules may use the route.

These settings control different parts of the connection and aren’t interchangeable
Setting What it does What to keep in mind
System proxy Routes traffic from apps that follow Windows proxy settings through the local proxy Apps that ignore this setting may still connect directly
Rule mode Chooses a policy, such as proxy or direct, based on domains, addresses or other rules Rules may send different websites through different routes
Global proxy policy Applies the selected proxy policy to traffic entering the client Doesn’t mean every app is covered; it depends on how traffic enters the client
Virtual network adapter mode Uses a virtual network interface to capture traffic from a broader range of apps Depends on permissions, routing and DNS settings, and may have exclusions

For everyday use, start with rule mode and the system proxy as recommended by your client, then test the apps you need. Consider a virtual adapter only if an app ignores the system proxy and the client documentation recommends it. Avoid changing several modes at once, or it will be hard to tell which setting made a difference.

Choose a region based on the service you want to use, not just a speed-test ranking. A latency test measures the round-trip time for a particular test request; it doesn’t measure download speed or guarantee performance for video calls or streaming. When comparing routes, keep the network, app and destination the same, and check actual loading and connection stability.

Verify the connection: Check your route, apps and DNS separately

Open the IP check page to see your browser’s current exit information, then try the service you actually need. If your browser is using the proxy, the exit address will usually change with the selected route. But the result reflects only that request; it doesn’t prove that all traffic from your PC takes the same path.

  • Test the app you need. Try your collaboration app, browser or another app you actually use. If only the browser works, check whether the app follows the system proxy and whether the client’s connection log shows its requests.
  • Check the routing result. In the client’s connections or logs view, see which rule matched the target domain and which policy was used. Logs may contain visited domains, so redact them before sharing.
  • Check the DNS path. DNS translates domain names into addresses. Using a proxy doesn’t automatically route every DNS query through it. System settings, client DNS, secure DNS in your browser and routing rules can all affect the path.

Seeing resolvers in different regions in a DNS test doesn’t necessarily prove there’s a leak. Public DNS services may use distributed infrastructure, and geolocation data can be inaccurate. Check the result against your intended setup: are queries that should be protected by the proxy still being sent to resolvers on your local network?

If you suspect a DNS issue, first check the client documentation for DNS and virtual adapter settings. Then see whether your browser has enabled a separate DNS method. Don’t enter an unfamiliar DNS address just to remove a name from a test result, and don’t disable certificate checks to fix a website that won’t load.

Configure startup: Set launch and auto-connect separately

Once you’ve confirmed that a manual connection works, open the client settings and look for an option such as “Launch at startup” or “Start after sign-in.” For desktop clients, startup usually means launching after you sign in to Windows; it doesn’t mean the connection starts before you sign in.

Then check for separate options such as “Enable system proxy on startup,” “Auto-connect” or “Restore last configuration.” Launching the app, loading a configuration and routing traffic automatically are different things. Enabling one doesn’t mean the others are set up. Use the options available in your client.

  1. Keep the configuration and policy you’ve verified, then enable the client’s startup option.
  2. In Windows Settings, check Apps > Startup, or open the Startup apps page in Task Manager, and make sure the client isn’t disabled.
  3. Restart and sign in. Check the tray icon, active configuration and proxy setting, then test the target app again.
  4. If the client launches more than once, check whether both its built-in startup option and a manually added shortcut are enabled. Keep only the one you need.

If you briefly lose internet access after signing in, wait for the local network to connect, then check whether the client recovers. Repeatedly restarting the client isn’t a long-term fix. Before replacing or removing it, turn off the system proxy in the client, then quit and uninstall it to avoid leaving Windows with proxy settings that point to a local app that’s no longer running.

Common issues: Troubleshoot each step in turn

Subscription update fails, but regular websites load

Check that the link is complete and that your account and plan are in good standing. Then work out whether the issue is a failed fetch or a parsing error. A failed fetch usually points to an unreachable URL or access restrictions; a parsing error more often means a format or client-core compatibility issue. When contacting support, include the client name, system type and a redacted error message—not the full subscription link.

The client says it’s connected, but a website won’t load

Check whether the request appears in the client. If there’s no record, check the system proxy or the app’s own settings. If it appears, check the matched rule, selected route and DNS. The platform may also restrict access based on account region or exit policy, so don’t assume every error is caused by the client installation.

The browser loses internet access after I quit the client

Open Network & internet in Windows Settings and check the Proxy page. If a manual proxy set by the client is still enabled after the local app has quit, use the client to turn it off or restore the previous settings. If your organization manages the proxy, contact your administrator before making changes.

If setup isn’t complete, return to the getting started guide to check the download link. When you’re ready to compare plans, see plan pricing and traffic rules. Get the connection and verification working before enabling startup, and you can use the same troubleshooting steps if you later switch devices or clients.