Windows VPN Setup from Scratch: Install the Client and Enable Auto-Start

Install the client, import your subscription, choose a route, verify the connection, and set the client to launch at startup with this step-by-step Windows guide.

To set up a VPN on Windows, install the client, import your subscription, choose a route, test your target apps, then configure startup. Before enabling auto-connect, check whether your browser or desktop apps actually use the selected route. That makes issues after a restart easier to diagnose.

Install the Windows client

  1. Open the 2LVPN client portal and follow the instructions in your user dashboard to get the Windows client. An existing proxy client may not work out of the box, so first check which subscription formats and connection protocols it supports.
  2. If the download page offers different processor architectures, check “System type” under Windows “Settings → System → About” and choose the matching installer. Verify the download source and publisher before installing. If you see a warning you can’t verify, consult the user guide first. Don’t disable system protection just to install the client.
  3. Open the client, but leave auto-start off for now. If you already use another proxy or VPN and can manage it yourself, disconnect it before testing the new client. Don’t change work-managed connections, security policies, or security software settings on your own.

Windows Settings also has a “VPN” section. It’s for adding VPN connections supported by Windows, not for importing subscriptions in general. If the service provides a client subscription URL, import it in the specified client. Don’t paste the full link into Windows’ “Server name or address” field.

Get and import your subscription

Get your subscription link from the user dashboard. In the client, look for an option such as “Subscriptions,” “Profiles,” or “Import from URL,” paste the full address, and update it. Menu names vary between clients. After importing, confirm the refreshed profile is active, then check that the route list is populated.

A subscription is how the client retrieves route configuration; it isn’t the protocol used to connect. Shadowsocks, Trojan, and VLESS are different connection protocols. A client that accepts subscription URLs may still be unable to parse the format provided by the service or connect to every route in it. If you get a format error, check the dashboard for the subscription format supported by your client. If the request fails or is unauthorized, first make sure your regular internet connection works, then check that the link is still valid in the dashboard. Reinstalling the client repeatedly won’t help.

Choose a route and how to handle traffic

Choose a region based on what you need, then test it with the app you plan to use. If a region has multiple routes, compare how well pages open, files load, or calls hold up on the same network. The client’s latency test is a useful reference, but it doesn’t replace testing in the app: it measures the response from a specific test target, not download speed, and doesn’t tell you whether an app supports that exit region.

Choosing a route is only part of the setup; you also need to decide how traffic reaches the client. “System proxy” and “TUN” are traffic-handling modes. “Rule-based routing” determines whether requests already handled by the client connect directly, use a proxy, or follow other rules. Enabling TUN doesn’t mean every request will use a proxy route.

Traffic handling modes in the Windows client
Mode Best for What to check when testing
System proxy Primarily browsing, or apps that use the Windows proxy settings. Some apps ignore the system proxy or use their own settings. If it works in your browser, that doesn’t mean it will work in other apps.
TUN (virtual network adapter) Desktop apps that don’t use the system proxy, when the client can route their traffic through a virtual network adapter. May require elevated permissions or a background service. Actual coverage still depends on routing, traffic rules, and how the client is implemented.

If you only need a browser, start with the system proxy. If the browser works but your target app doesn’t, check whether the app has its own proxy settings before trying TUN. Change one setting at a time so you can tell whether the route or the traffic-handling mode made a difference.

Verify the connection and troubleshoot browser-app differences

  1. Establish a baseline. Before connecting, check your public IP using the same browser and make sure regular websites load. If your local connection is already down, restore it first. On public Wi-Fi, complete any sign-in step to get online.
  2. Test a request that should use the proxy. After connecting, refresh the IP check in the same browser and open the service you want to use. In rule mode, the IP-check site may be set to connect directly, so seeing your original IP doesn’t necessarily mean the connection failed. If connection logs are available, check which rules matched the IP-check domain and the target service domain.
  3. Test the target app separately. For a desktop app, quit and reopen it, then try an action that needs an internet connection. A change in your browser’s exit IP only tells you how that browser request was routed. If the client provides connection logs, check whether the target request appears and whether it used the proxy or connected directly.

A changed exit IP doesn’t prove that DNS queries took the same route. Browser secure DNS, system resolver settings, and the client’s DNS handling may differ. If you need to check, run a DNS test in the browser you’re using and compare the results with the client’s DNS settings and logs. The result shows which resolver handled the test domain, not the DNS queries from every app on your computer.

If websites still won’t load after disconnecting, check whether the client changed the system proxy without restoring it. You can also check Windows “Settings → Network & Internet → Proxy.” Restore only settings changed by your own client, and leave existing corporate proxy settings intact. If the issue happens only with TUN enabled, turn TUN off in the client, quit it, and test your regular connection again. Then follow the troubleshooting guide step by step.

How to tell it’s working: The setup is working when the target app completes the task you need and its traffic follows the expected route. A connected icon in the system tray only means the client has entered a connected state.

Set up launch at startup and auto-connect

After testing manually, enable “Launch at startup” or “Start when I sign in” in the client. You can also check registered startup apps under Windows “Settings → Apps → Startup.” Startup usually happens after you sign in to Windows; it doesn’t establish a connection before the desktop loads.

Launching the client, restoring the last profile, and connecting automatically are separate actions. To connect as soon as you sign in, make sure the client has an auto-connect option and that your default profile, route, and traffic-handling mode are set. If there’s no such option, use startup launch simply to avoid opening the client manually. If you connect only when needed or often use public networks with sign-in pages, keep startup launch enabled but auto-connect off to make troubleshooting easier.

After restarting and signing in, use this checklist to verify the setup. Don’t rely on the system tray icon alone:

  • ✅ Without opening the client manually, confirm it has started and that the active profile is the one that worked before the restart.
  • ✅ If auto-connect is enabled, wait for the system to get online, then run the target app’s connection test again.
  • ❌ If the client starts but doesn’t connect, don’t add another startup entry. Connect manually first. If that works, check auto-connect, profile restoration, or the permissions TUN requires.
Use for free