Setting up a Windows VPN takes more than installing an app. Your subscription, server, proxy mode, and actual browsing results all need to work together. Follow these steps to install a client, import your subscription, choose a server, verify the connection, and enable startup. Button names may vary by client; check the download page for client-specific instructions.

Before you begin: check the VPN client and configuration source

Visit the VPN client download page, choose the Windows option, and review the version and installation instructions. VPNUI supports Windows. You can create an account with a username and password—no email address required. Your account login and subscription link serve different purposes: use the former to access the dashboard and the latter to load server configurations in your client. Don’t confuse the two.

Before downloading, check your system type under Windows “Settings → System → About,” then choose the version that matches the download instructions. Installer packages and portable versions work differently. An installer usually guides you through setup; a portable version must first be extracted to a dedicated folder before you run the main program. Don’t launch it from the archive preview, and avoid moving the program folder after configuring startup.

  • ✅ Download the client from the dashboard and verify the file name against the release notes.
  • ✅ Make sure your account has an active subscription or available data, and keep a local backup of your current configuration.
  • ✅ Close other proxy clients temporarily to prevent them from competing to control your system proxy or routes.
  • ❌ Don’t post your subscription link in public forums or submit it to untrusted online conversion tools.

If Windows displays a security warning when you launch the client, verify the download source and publisher before proceeding. Don’t disable your security protection just to complete installation. Standard system proxy mode may not require administrator permissions. TUN mode, service installation, or route control may require authorization—allow it only after confirming the source and that the feature is necessary.

Import your subscription: add servers to the list

Sign in to the dashboard and get the subscription configuration using the method shown there. Some clients retrieve configurations automatically after account login; others require you to import a link or file manually. The steps below cover manual link import. Don’t use the dashboard URL from your browser’s address bar as a subscription link, or combine your username and password to create a configuration URL.

  1. Find the subscription or configuration section in the dashboard and copy the link for your client. If the page offers one-click import, make sure it opens the client you just installed.
  2. Open the client’s “Subscriptions,” “Configuration,” or “Profiles” page. Look for an option such as Add, Import from URL, or a similar command.
  3. Paste the full link, give the configuration a recognizable local name, save it, then update or download the configuration.
  4. Select the imported configuration and make sure it’s enabled. Then open the server or proxy list and check that the servers appear.

Even if you see “Import successful,” check the configuration contents. An empty list may mean the configuration isn’t active, the subscription request failed, there’s an issue with your account, or the link format isn’t supported by the client. Check the update status first, then confirm the recommended import method on the download page. Don’t add the same link repeatedly and create duplicates.

Shadowsocks, VMess, Trojan, and VLESS are different protocols. Hysteria2 and TUIC also require a compatible implementation. A client’s ability to accept subscription links doesn’t mean it can parse every protocol or subscription format. If you see “Unsupported type,” use a compatible client or a format supported by the dashboard instead of changing the protocol name at random.

Subscription links may contain access credentials. When sharing a screenshot for support, hide the full link, account details, and tokens. If a link has been exposed publicly, check whether the dashboard lets you reset it, then update the client configuration.

Choose a server and proxy mode

Open the server list and choose an exit location that matches the target website’s regional requirements, then test the connection. VPNUI offers 100+ countries and 190+ routes, but coverage doesn’t guarantee that a particular site will work through every route. If you don’t need a specific location, start with the client’s test results, then confirm by loading the site itself.

Latency tests in the server list measure response to a specific probe target; they don’t directly indicate download speed or video quality. Labels such as dedicated route, relay, or direct connection aren’t a substitute for testing either. A dedicated route usually describes part of the transmission path; a relay means traffic passes through an intermediate server; direct connection means the client connects to the entry point directly. Check the route details to see whether IEPL is used, where it applies, and how the exit connects to the internet. Don’t draw conclusions from the label alone.

What common modes do and where to check them
Mode or setting What it does What to check
System proxy Provides a local proxy endpoint for apps that follow Windows proxy settings A working browser doesn’t mean every app is using the proxy
Rule-based routing Routes traffic directly or through a proxy based on domains, addresses, or other rules Which rule matched the target site and which exit it uses
Global proxy Sends traffic handled by the client through the selected proxy exit Doesn’t automatically extend system proxy coverage to more apps
TUN mode Uses a virtual network interface to handle IP traffic from more apps Check permissions, routes, and DNS settings, and look for conflicts with other networking software

For your first setup, start with the system proxy and the client’s default rules. This makes issues easier to spot and avoids changing routes, DNS, and rules all at once. If you need to use apps that don’t follow the system proxy, try TUN mode as instructed. Support and service component requirements depend on the client you use.

Bottom line: First test browser access with the default rules, then troubleshoot specific apps. Global proxy mode is useful for a quick comparison, but it doesn’t guarantee that every program will use the proxy.

Verify the connection: check your exit IP, rules, and DNS

A client showing “Running” only means the app or connection has started. Test it in context: open an international site you normally use and check that it loads fully, then visit an IP lookup page and compare the result with your selected location. The lookup page itself may be set to bypass the proxy under your rules. If the results differ, check the rules before assuming the route is down.

  1. Keep the selected server and visit the target site. Note whether it fails to open, loads incompletely, or won’t let you sign in.
  2. Open the client’s connection log, if available, and check which rule and exit server were used for the target domain.
  3. Temporarily switch to global proxy mode for comparison, then return to your original mode. If global mode works but rule-based routing doesn’t, check your routing rules first.
  4. Test the apps you actually need, not just your browser. An app may have its own proxy settings or ignore the system proxy entirely.

A DNS leak generally means domain lookup requests that you expected to use a specific route are still being sent to an unintended resolver. Enabling the system proxy doesn’t necessarily route every DNS request. Browser encrypted DNS, the client’s DNS strategy, and system settings can also interact. A test page’s reported resolver location is only a clue; a difference between that location and your exit location doesn’t, by itself, prove a leak.

To troubleshoot, note your browser’s “Secure DNS” and the client’s DNS settings. Follow the client documentation to use a consistent DNS strategy, then compare the results. Don’t enter unfamiliar DNS addresses just to make test results look consistent. If a site still reports that your location doesn’t match, also check your account’s region, existing sessions, and cache. A proxy exit can’t guarantee that your account qualifies for a different region.

Enable startup: separate launch from auto-connect

Set up startup only after you’ve successfully verified a manual connection. Check separately whether the app starts when you sign in, loads the last configuration, and restores proxy control. These are different actions: opening the client automatically doesn’t mean the system proxy is enabled, and keeping a server selected doesn’t mean a connection has been established.

  1. Open the client settings and look for “Start at startup,” “Launch at sign-in,” or a similar option. Enable it as instructed. If there are separate options for auto-connect or restoring the proxy, check each one too.
  2. Open Windows “Settings → Apps → Startup,” or the Startup apps page in Task Manager, and check whether the client is disabled. The option names may vary slightly between Windows versions.
  3. Save the configuration and restart your computer. After signing in, wait for the network to come online, then check the system tray icon, active configuration, and proxy status.
  4. Open the target site again to verify access. If the client window opens automatically but the site won’t load, check the connection and proxy status in the client.

Startup usually happens after you sign in; it doesn’t mean the connection is available before the desktop loads. If a portable version has no built-in startup option, you can add a shortcut to the Windows Startup folder. Use only the app intended for regular user startup; don’t copy drivers or service components. If the client already has built-in startup, don’t add a second startup method.

After waking from sleep or switching networks, an old connection may need to be re-established. Wait for the network to recover, then check whether the client reconnects. Startup settings don’t eliminate the need to check after every network change.

Common issues and checks after disconnecting

Connected, but websites won’t load

Disconnect the proxy first and check whether your local network works. Then check for subscription updates, the selected server, routing rules, and system proxy settings. Change one setting at a time so you can identify the cause. If switching servers fixes the issue, keep the error message from the failed attempt. If every server behaves the same way, check the client configuration and local network rather than cycling through locations.

Browser works, but other apps don’t

Check whether the app has its own proxy settings or supports the system proxy. If it does, configure it with the local listening address and port shown by the client; don’t use a port you found at random online. If the app doesn’t support a proxy, consult its documentation about using TUN mode. Also consider company network policies and conflicts with other virtual network software.

Local network stops working after closing the client

Use the client’s disconnect, disable system proxy, or normal exit option first. If the app crashes, Windows may still point to a local proxy that has stopped running. Check the manual proxy setting under “Settings → Network & Internet → Proxy.” Disable it only after confirming the client set it. Don’t change existing proxy settings on a device managed by your organization.

When to update your subscription and when to ask for help

If the server list changes, your configuration expires, or the dashboard prompts you to update, refresh the subscription first and make sure you’ve selected an active server. When asking for help, include the client name and version, error message, what you were doing, and the comparison tests you’ve tried. Hide sensitive configuration details. You can also consult the troubleshooting guide or submit an issue through the dashboard support tickets.

Setup complete when: the subscription updates, the target site loads, apps follow the expected routing rules, your configuration is restored after a restart, and your local network works after a normal shutdown. Once everything checks out, you can leave the client configured to start automatically.