Setting up a Windows VPN for the first time? Install the client, import your subscription, choose a route, and test the connection. Once manual connection works, enable startup. If you can't get online after restarting, you can tell whether the client failed to launch or launched without routing your traffic.
Step 1: Install a Windows Client
Open the client download page in the H6VPN user panel and choose a client for Windows as instructed. This guide uses a subscription-compatible client. Don't enter the subscription URL under “Add a VPN” in Windows Settings—that's a separate setup option.
- If the download page offers versions for different architectures, open “Settings → System → About” in Windows and check “System type” before choosing a version. Don't guess based on the processor brand alone.
- Open the installer provided in the panel and follow the prompts. If Windows displays a permissions prompt, verify the program's source and publisher first. Don't approve it just to continue if the source is unclear. If the computer is managed by your workplace or school, check that installation is allowed.
- Open the client from the Start menu and find the “Subscriptions,” “Profiles,” or “Configuration” page. It's normal for the route list to be empty the first time you open it. Once you can access the configuration page, you can import your subscription without changing your system network settings first.
Step 2: Import and Enable Your Subscription
Sign in to the user panel to get your subscription URL, and choose the format that matches your client as instructed. In the client, open “Subscriptions” or “Configuration,” select “Add” or “Import from URL,” paste the link, and save. If the list doesn't update automatically, select “Update” or “Refresh” next to the subscription and wait for the routes to appear. Then select that profile. Seeing the subscription name doesn't mean the routes have downloaded or the profile is enabled.
If the update fails, first make sure regular websites load with the system proxy off. Then copy the URL from the panel again and check for missing characters, extra spaces, or an incompatible client format. If the update succeeds but no routes appear, check whether the client is still showing an older profile. Avoid changing system DNS and proxy mode at the same time, or it will be hard to tell what caused the issue.
Step 3: Choose a Route and Connection Mode
Open “Proxy” or “Nodes” and select a node from the route group in your current profile. If there are multiple proxy groups, check which one the target app's rules use. For initial troubleshooting, pin a route temporarily if the client allows manual selection; this makes before-and-after results easier to compare. The latency shown in the list reflects only that test and doesn't predict how a particular website or call will perform.
After choosing a route, check whether you also need to select “Connect” or enable “System proxy.” How traffic reaches the client and how the client routes traffic are separate settings. Some clients put these controls on different pages; the table below explains the difference.
| Option | What it does | Common misconception |
|---|---|---|
| System proxy | Sends requests from apps that follow the system proxy settings to the client. | A browser working doesn't mean every desktop app uses the proxy. |
| TUN mode | Routes traffic through a virtual network adapter. Coverage depends on the client configuration. | May require additional permissions. Verify the target app even after enabling it. |
| Rule mode / Global mode | Determines whether requests received by the client are routed according to rules or all sent through the current proxy. | Switching to Global mode won't automatically reroute requests that never reached the client. |
To check browser connectivity, start with the client's system proxy option if available. In Rule mode, some requests going direct is normal. If a desktop app doesn't follow the system proxy, check whether the client supports TUN and whether the app needs its own proxy settings. You don't need to disable the firewall or change network policies managed by your organization.
Step 4: Verify Your Exit IP and Target App
First, turn off client routing and open a public IP lookup site you trust in your browser. Note the IP address, then enable routing and open the same lookup page again. For a fair comparison, use the same network and check the same address type, such as IPv4. A “Connected” status in the client is a clue, not a substitute for checking actual requests.
- ✅ IP address changed: The lookup used a different exit route this time. Next, open the website or app you actually need and try a routine task, such as loading a page or syncing a file.
- ❌ IP address unchanged: Check whether the lookup page matched a direct-connection rule. If the client supports it and your environment allows it, temporarily switch to Global mode for comparison, then restore your original settings.
- ❌ Browser works, desktop app doesn't: Check whether the app follows the system proxy or has its own proxy settings. Don't infer how the app's traffic is routed from browser results alone.
An IP check also can't confirm that DNS queries use the same route. If a domain won't open, check whether the client reports a resolution error and whether the browser has its own secure DNS setting enabled. Browsers and desktop apps may use different DNS routes. Identify the affected app first, then decide whether to adjust its settings.
Manual setup is working when: the target app can handle everyday tasks in the expected mode, and regular network access returns after you disconnect. Route latency or a tray icon alone doesn't count as verification.
Step 5: Configure Startup and Auto-Connect
Open “Settings” or “General” in the client and enable “Launch at startup” or “Start on login.” Then look for options such as “Auto-connect,” “Restore previous state,” or “Set system proxy on startup,” and choose what fits your setup. Most startup items run after you sign in to Windows. A tray icon only shows that the app launched; it doesn't mean traffic is being routed.
- After saving your settings, check the client in “Settings → Apps → Startup” or in Task Manager's startup apps list. If it's listed, make sure it isn't disabled. If it isn't listed, check the client's instructions for enabling startup.
- Restart Windows and sign in. Once your network is available, look for the client in the notification area. Open it, confirm the current profile, route, and routing mode, then test the target app again.
- If the app launches but doesn't connect, check its auto-connect setting and your network status. On public Wi-Fi that requires a web sign-in, complete the network login first, then connect manually to test.
If websites stop loading after you quit the client, try turning off routing inside the client before exiting normally. If that doesn't restore access, open “Settings → Network & Internet → Proxy” and check for a manual proxy left behind by the client. Restore only settings you changed yourself; don't remove proxy settings managed by your organization. To check where to access the panel, see the quick start guide.