A complete Windows VPN setup guide: install a client, then configure startup at login
Follow five steps: install a client, import your subscription, choose a route, verify the connection, and configure startup. Each step explains where to click and what to look for, so beginners can set everything up with confidence.
Before setting up a VPN on Windows, check whether you have a subscription link or connection details for Windows' built-in VPN. Import a subscription link into a compatible client; don't enter it in Windows' Add a VPN window. Connect manually and test the apps you need before configuring startup. If something goes wrong after a restart, you can tell whether the client failed to launch or connect.
Install the client: check your configuration type
Windows Settings → Network & Internet → VPN is for connections where an administrator or provider has supplied the details required by Windows' built-in VPN client. A proxy subscription is usually a link that a client uses to load its configuration, not a VPN server address. If your provider gave you a subscription link, check the service dashboard or the Windows setup guide to confirm which client and subscription format to use.
- Go to Settings → System → About and check the processor architecture under System type. If the download page offers x64 and Arm64 versions, choose the one that matches your system.
- Download the installer from the client's official website or the link provided in your service dashboard. Before running it, right-click the file and open Properties to check its digital signature and publisher. If you can't verify the source or publisher, stop and confirm first. On a work computer, follow your administrator's instructions.
- Launch the client and look for a page labeled Configuration, Subscription, or Profiles. Keep it disconnected for now, and check that Windows can access websites normally so you don't mistake a local network issue for a failed installation.
Import your subscription: make sure the configuration is enabled
Copy the subscription link for your client from the service dashboard. In the client, choose Import from URL or New subscription, paste the link, then save or update it. If the import succeeds, the subscription should appear in the configuration list. Some clients also require you to select Use or Set as current before the subscription's routes appear on the node page.
If you get a format error, check whether the dashboard offers different links for different client versions, then make sure you haven't missed anything or copied extra spaces. If the client can't fetch the subscription, check your local connection, system clock, and whether the link has been regenerated. If routes appear but a specific one reports an unsupported configuration, check that the client's core supports its protocol and transport options. Being able to read a subscription doesn't mean the client can run every configuration in it.
Choose a route and proxy mode
Choose a route on the Nodes or Proxy Groups page, then check that your routing rules actually refer to that group. Selecting a node doesn't mean every app will use it: rule-based mode sends requests direct, through a designated proxy group, or via another policy depending on the match. For testing, stick with one route and use the app you actually need to check whether pages, downloads, and persistent connections work reliably. The client's latency test only shows how quickly a test destination responded at that moment; it can't replace testing the app itself.
| Method | When to use it | What to check |
|---|---|---|
| System proxy | Start by testing a browser or app that uses the Windows proxy settings. | Apps that ignore the system proxy may still use your regular network connection. |
| In-app proxy | Set a local proxy only in apps that let you configure one manually. | The proxy type and port must match the listener settings provided by the client. |
| Virtual network adapter (TUN) | Use this when an app ignores the system proxy and your client can route traffic through a virtual network adapter. | Grant permission as prompted by the client, then check that the target app and local network access both work as expected. |
The traffic capture method determines which requests enter the client; routing rules determine where they go afterward. Even with TUN enabled, requests set to go direct by a rule may keep the same public exit IP. When troubleshooting, change only one thing at a time—a capture method, rule, or route—and repeat the same test.
Verify the connection: check your exit IP and target app
- Before connecting, open my IP in the same browser and note your current public IP address. Compare it before and after on the same network and page; don't switch Wi-Fi in between.
- Enable your chosen traffic capture mode and refresh the page. If the detection page is meant to use the proxy under your rules, its public IP should match the selected exit route. If the page matches a direct-connection rule, an unchanged IP is expected. If your client keeps connection logs, check which policy was applied to the domain.
- Open the app you actually want to use and try the request again. If the browser's exit IP has changed but the app still fails, first check whether the app's traffic goes through the client and whether it has its own proxy settings. Then check which policy matches the app's domain. Don't assume the whole computer is connected just because the browser works.
An exit IP check won't show where DNS queries are routed. To check DNS resolution, review the client's DNS settings and logs, and see whether your browser has its own secure DNS enabled. A changed public IP doesn't mean all DNS queries use the same route. Likewise, a local DNS resolution explicitly allowed by your rules isn't proof of a leak just because of a test result.
Success criteria: A connected status in the client is only the starting point. The setup is working when the target app completes a real task and the exit IP or connection logs match your expectations.
Launch at startup: configure launch and connection separately
First, look in the client's settings for an option such as Launch at startup or Launch when I sign in. If you can't find one, check whether the client appears under Windows Settings → Apps → Startup. Startup usually means launching after you sign in to the desktop, not connecting before sign-in. Enabling startup alone may leave the client in the system tray without turning on the system proxy.
If you want the client to reconnect after sign-in, look for a separate option such as Connect on launch, Restore previous connection, or Enable system proxy on launch. These options do different things; if the client only supports automatic launch, connect manually. After saving your settings, restart Windows and wait for the network connection. Then check the current configuration, route, and traffic capture status from the system tray, and repeat your target-app test.
- ✅ Client icon missing from the system tray: check Windows startup apps and the client's startup settings.
- ✅ Client launched but didn't connect: first confirm that manual connection works, then check the auto-connect option. If the client starts before the network is ready, see whether it can retry.
- ✅ Websites stop loading after closing the client: check Settings → Network & Internet → Proxy for a local port that points to a stopped client. Revert only proxy changes you made for this setup, and leave any work or school settings intact.