Setting up a Windows VPN involves more than installing an app. You also need to route the right apps through the right servers and restore your preferred settings after a restart. Follow the steps in order—install, import, connect, verify, then configure startup—and confirm each one works before moving on. This makes it easier to pinpoint issues without changing several settings at once.
Before you install: check your usage and choose a client
Choose a data plan based on how often you use the service. VPNSize monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB; data resets monthly on the activation date. Data packs cost ¥158/300GB, ¥358/1000GB, or ¥658/3000GB, and never expire. A monthly plan may suit frequent use, while a data pack can work well for occasional use. Choose based on your usage rather than your PC specs alone.
VPNSize does not require an email address; sign up with a username and password. In your account dashboard, visit the client download page for the current Windows installation options and instructions. Third-party clients may change their interfaces and supported features, so this guide uses general feature names rather than assuming a particular button is available in every version.
- ✅ Check your system type in Windows Settings and download the installer that matches your device architecture.
- ✅ Make sure the file comes from the source provided in your dashboard and verify the publisher. If the source or signature looks unusual, stop and check before installing.
- ✅ Keep your account credentials handy, along with the subscription link or import option from your dashboard. Don’t share the link in public chats or screenshots.
- ✅ Pause other proxy or VPN clients and note your existing proxy settings to avoid multiple apps taking control of your network at once.
A subscription link may contain credentials that grant access to your configuration, so protect it like a password. If you contact support, share an error message with sensitive details redacted instead of sending your full configuration.
Install the client and import your subscription
Installing a client and purchasing data are separate steps, and installation alone does not establish a connection. Windows’ built-in VPN settings do not natively handle every proxy subscription. Protocols such as Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC require a compatible client or core. Their presence in the broader ecosystem does not mean VPNSize currently supports all of them; check your dashboard for the available configurations.
- Install and launch the client. Follow the instructions for your download source and review any permission prompts the first time you open it. A standard system proxy and a virtual network adapter may require different permissions, so there’s no need to run every app as an administrator from the outset.
- Get your subscription. Find the subscription option in your account dashboard. If there’s a specific import option for your client, follow those instructions rather than choosing a configuration format for a different app.
- Import the configuration. Paste the link into the client’s subscription or configuration manager, save it, and update the subscription. Some clients can open an import link from a browser; if prompted, make sure it opens the intended app.
- Check the import. Make sure the configuration is enabled and the server list opens. If you can see a subscription name but no servers, check the update result before repeatedly trying to connect.
If the client reports an unsupported format, first check that you copied the full link and that the client supports the subscription format and protocols. A subscription URL is usually for fetching configuration, not opening a regular webpage; seeing text in a browser doesn’t necessarily mean something is wrong. Avoid processing subscription links with unknown online converters, which could expose your credentials to another service.
Connection mode: system proxy or virtual network adapter
A client showing “Running” often means only that its local proxy core has started. Whether app traffic passes through it depends on the system proxy, the app’s own settings, or virtual network adapter mode. Understand what each mode affects before choosing one; enabling every option at once makes results harder to verify.
| Mode | Scope | What to keep in mind |
|---|---|---|
| System proxy | For apps that follow Windows proxy settings | Not all apps follow these settings. A working browser doesn’t mean every app is routed successfully. |
| In-app proxy | Set a proxy address and type in a specific app | Must match the client’s local listening settings. Don’t copy an unfamiliar port number. |
| Virtual network adapter mode | Routes traffic that matches the configuration through a virtual network interface | May require a driver or administrator permissions; routing, split tunneling, and DNS settings still apply. |
For your first test, try the mode recommended in your client’s documentation. If your browser works with the system proxy but a particular app behaves differently, check whether that app supports system proxy settings. If needed, enable the virtual network adapter as described in the client documentation. It does not guarantee that all traffic will use the same exit: routing and rules may still send some requests directly.
Rule-based mode typically routes traffic directly or through a proxy based on domains, addresses, or other criteria. Global proxy mode typically sends traffic within its scope to the selected proxy. Global mode doesn’t mean every connection on your PC is captured, and rule-based mode doesn’t guarantee that every site is classified correctly. Test the apps you actually use rather than relying on mode names, especially for sensitive tasks.
Choosing a server: start with your target region
First check whether the service you’re accessing requires an exit in a particular region, then choose an available server there. VPNSize covers 90+ countries with 150+ servers, but that coverage does not mean a particular platform will always accept an exit from a given location. Check your dashboard for current server and region details. Platforms may also consider your account region, payment location, and other signals.
A direct connection generally connects your client straight to an overseas server; a relay routes traffic through an intermediate node; IEPL usually refers to an international Ethernet private line. These terms describe different routes and transport methods, but they don’t tell you the actual speed or prove that a particular VPNSize server uses a specific network design. Base your assessment only on information explicitly shown in the dashboard.
After choosing a server, test response times, sustained loading, and connection stability with the actual websites or apps you need. A client’s latency test reflects specific test conditions, not download bandwidth. When comparing servers, keep the target page and other settings the same so you can tell whether any difference comes from the server or your local network.
Check your exit IP, DNS, and split tunneling
A connection icon is only a starting point. To verify the setup, check that your exit changes, your apps work, and requests are routed as expected. Before testing, disconnect the client and note your original network details. Recheck them in the same environment after connecting so you don’t mistake a cached result or an old page for your current status.
- Check your exit IP. Open the network test page and compare your public IP and region before and after connecting. In rule-based mode, make sure the test request itself is routed through the proxy.
- Test the target app. Make a real request in the app you need to use. If the browser works but the app behaves the same as before, check the traffic-routing scope and the app’s proxy settings.
- Review the client’s connection logs. If the client shows connection details or rule matches, check whether the target domain used a direct connection or the proxy, and confirm that the exit is the one you expect.
- Check the DNS path. Use a trusted test tool alongside the client’s DNS settings to see whether DNS requests follow the expected route. Don’t rely only on the exit IP shown by a website.
A DNS leak generally means that name lookups which should use a protected route are still going to an unexpected resolver. Secure DNS in your browser, system DNS, and DNS handling by the client can all operate at the same time, so interpret test results in light of those settings. An unfamiliar local resolver is worth investigating, but its name alone doesn’t prove that all connections are failing.
If your device has both IPv4 and IPv6 connectivity, check that the client handles traffic for both as expected. Prefer the complete configuration recommended in the client documentation; don’t disable system features just to make a test result look better.
The target app can complete requests, the exit meets your requirements, routing matches your expectations, and the DNS path has been checked. A changed tray icon or a “Connected” status alone isn’t enough to verify the setup.
Start on boot: distinguish startup from connection
Verify the connection manually before configuring startup. Launching the client when you sign in to Windows, connecting automatically after launch, and enabling the system proxy are usually separate options. Turning on one doesn’t mean the others will take effect. Many desktop clients start after a user signs in, not as soon as the computer is powered on.
- In the client settings, find “Start with system” or a similar option and enable it if needed.
- Check the default configuration, server, and connect-on-startup options so the client doesn’t launch without a server selected.
- Check Windows Startup apps or Task Manager to make sure the client hasn’t been disabled. Avoid creating duplicate startup entries.
- Restart and sign in. Once the network is available, check the client, proxy settings, and exit, then test your target app.
Virtual network adapters may depend on services, drivers, or elevated permissions, so their startup behavior can differ from a standard system proxy. Use the client’s official settings and don’t disable system protections to get around a permissions prompt. Recheck the connection after waking from sleep or switching networks, not just after a restart.
Common issues: a troubleshooting checklist
Subscription update fails: Check your account and configuration status, copy the link again from your dashboard, and review client compatibility and the error message. Reinstalling shouldn’t be your first move; it usually won’t fix an expired link or unsupported format.
Connected, but webpages won’t load: First make sure your basic network works with the client disconnected. Then check your system clock, proxy mode, and selected server, changing only one thing at a time. If one site fails but others work, check the rules, DNS, and the site’s status before resetting your entire network.
No internet after closing the client: Check whether Windows still points to a local proxy. Turn off the system proxy before closing the client normally; after an unexpected shutdown, review Windows proxy settings. Work or school devices may use a managed proxy, so don’t remove settings without checking first.
Unstable speeds: Rule out weak Wi-Fi, background downloads, and network changes before comparing other servers. VPNSize has no device limit, but multiple devices still share your account data and may compete for local bandwidth. No device limit does not mean each device gets a separate data allowance.
If the issue persists, use the support portal to share the client name, error message, selected region, and steps to reproduce the issue, with subscription credentials redacted. VPNSize offers a 14-day no-questions-asked refund. See the applicable terms for details, and don’t expose your full configuration while troubleshooting.