Before setting up a Windows VPN, check whether your provider gave you system VPN connection details or a client subscription. The first uses Windows' built-in VPN settings; the second usually requires a compatible client. Follow the steps below to install, import, connect, verify, and enable auto-start. A client showing “Connected” doesn't mean setup is complete.
Know the difference between Windows VPN and subscription clients
Windows Settings → Network & Internet → VPN is for creating VPN connections supported by Windows. You'll need connection details from your provider, including the connection type, server address, and authentication information. It isn't a place to import arbitrary subscription links. Pasting one into “Server name or address” usually won't create a working connection.
A subscription client reads a configuration with routes, authentication details, and rules, then forwards traffic through a local proxy or virtual network adapter. Protocols such as Shadowsocks, VMess, Trojan, and VLESS require a compatible client; Hysteria2 and TUIC have their own implementation requirements. Don't assume software supports every protocol just because it says “VPN.” This guide doesn't claim that VPN73 supports any particular protocol.
| What you received | Where to use it | What to check |
|---|---|---|
| System VPN connection details | VPN in Windows Settings | Do the connection type, authentication method, and server address match? |
| Subscription link or configuration file | A compatible client specified by the provider | Are the configuration format, protocol, and client version compatible? |
| Imported, but apps still can't connect | Client proxy and routing settings | Does the app follow system proxy settings? Does it need virtual network adapter mode? |
Get and install the client
The VPN73 Windows client is available after you log in. Open the client downloads page in the dashboard and choose the installer for your version of Windows. No email address is required to create an account; use a username and password. You'll also need to log in to access your subscription. Avoid downloading lookalike programs from unofficial search results.
- Check your system type in Windows under Settings → System → About, then choose the matching version on the downloads page.
- After downloading, verify where the file came from. If Windows shows a security warning, check the source and publisher before proceeding. Don't disable system security features just to continue the installation.
- Follow the installation wizard. If it asks for administrator access, confirm that the request comes from the client you just downloaded and that the permission is needed to install network components.
- When you first open the app, locate its main window, settings, and taskbar notification area icon. Closing the window may not quit the app, so check whether it's still running in the background.
Menu names vary by version, so the steps below refer to features rather than assuming every client has the same buttons. Until a basic proxy connection works, avoid enabling virtual network adapter mode, auto-connect, and complex rules all at once. Otherwise, it can be hard to tell which setting caused a problem.
Import the subscription and check the configuration
A subscription link isn't a regular bookmark. It often contains credentials needed to retrieve route configurations, so treat it like a password. Log in to the dashboard, copy the subscription for your client, and add it through the client's “Subscription,” “Configuration,” or “Import” menu. If the dashboard offers a dedicated import button, follow the prompt to open the link in the client.
If adding it manually, give the configuration a clear local name, paste the complete address, and update it. A successful import means the configuration loads, routes appear in the list, and there are no parsing errors. It doesn't mean every route will connect or that your system is already using the proxy.
- ✅ Check that the subscription link is complete and contains no extra spaces, line breaks, or explanatory text.
- ✅ Make sure the active configuration is the one you just imported, not a sample included with the installation.
- ✅ Confirm the subscription updated successfully, then select a route and connect.
- ❌ Don't paste your subscription link into public chats, screenshots, or online conversion tools.
If you see “Unable to parse,” check the configuration format and client compatibility first. For “Download failed,” check your local connection, make sure the address is complete, and review the subscription status in the dashboard. Don't keep trying conversion services from unverified sources. If your credentials have been exposed, reset the subscription if the dashboard allows it, then update your local configuration.
Choose a route and routing mode
Choose an exit region based on where the site you're accessing is available, then check how consistently it responds. A nearby location doesn't necessarily mean a shorter network path, and a client connectivity test doesn't reflect the full website experience. VPN73 covers 90+ countries with 210+ routes. Check your account and current route list for available options.
IEPL, relay, and direct routes describe how traffic is routed, not which application protocol is used. IEPL typically involves a dedicated international transmission segment; a relay routes traffic from an entry point to an exit; direct routes generally involve fewer relay steps. These labels alone don't determine whether a site is accessible, what kind of exit IP you'll get, or how the route performs at peak times.
Start with the system proxy
When you enable the system proxy, apps that follow Windows proxy settings use the local proxy, but not every desktop app does. Rule mode typically chooses direct or proxied connections by domain or address. Global proxy mode often covers only traffic routed through the proxy, not every protocol on your computer.
Enable virtual network adapter mode only if needed
Virtual network adapter modes such as TUN can route more app traffic through the client, but coverage still depends on routing, exclusions, and DNS settings. They may require administrator access or network components and can conflict with corporate VPNs or other proxy software. If your browser works but a particular app doesn't, consider this mode after checking the client's instructions.
Keep the provider's default rules at first, and don't enable system proxies in multiple clients at once. If local network devices, company resources, or printers stop working, check for rules that allow direct connections to the local network. For corporate networks, follow your organization's access requirements instead of overriding managed settings.
Check your exit IP, website access, and DNS
Test the connection along the path you'll actually use. First note your exit IP with the client disconnected, then connect and check for a change on the IP lookup page. Finally, visit the website you need. Run the check in the browser you plan to use, since browsers, command-line tools, and other apps may take different proxy routes.
- Check whether the exit region matches your selected route. If it hasn't changed, confirm that the client is forwarding traffic and that your browser uses the system proxy or a separate proxy extension.
- Visit the site and try a real task, such as signing in and loading a page. Opening the homepage alone doesn't prove that subsequent requests will work.
- Check the client logs for rule matches and connection errors. Distinguish between direct connections, proxied traffic, authentication failures, and DNS lookup failures.
- If the target app still has problems, check its own proxy settings and then consider virtual network adapter mode instead of reinstalling Windows.
A DNS check looks at which resolver handles domain lookups and whether that matches your expectations. Browser encrypted DNS, the Windows resolver, and the client's DNS settings may all be involved. An IP lookup shows the exit used for that request; on its own, it can't prove that DNS queries weren't sent over your local network.
When using a trusted DNS test, interpret the results alongside the client documentation. A resolver appearing in another region doesn't automatically mean there's a leak; public resolvers may use distributed exits. Focus on whether domain lookups that should go through the proxy are bypassing the expected route. Test again after making changes, keeping browser cache and existing connections in mind.
Set up auto-start and auto-connect
Auto-start, connect on launch, and restore system proxy are separate features. Auto-start usually means the client opens after you sign in to Windows; it doesn't establish a connection before sign-in. Test a manual connection first, then enable automation so you know which settings should be restored after a restart.
First, enable the client's “Start with system” option. Then check Windows Settings → Apps → Startup or the Startup Apps list in Task Manager. If the client can connect on launch, confirm the default configuration and route. If it can restore the system proxy, check whether it also resets the proxy when you quit.
After setup, restart and sign in. Confirm that the client opens, the subscription loads, and the proxy is configured as expected, then visit a website. Network modes that require administrator access may be affected by permission prompts; adding a shortcut doesn't guarantee automatic startup. Without clear documentation, don't use Task Scheduler to bypass permission prompts.
On laptops, also check what happens after waking from sleep or switching networks. The client may still be running even if its old connection is no longer valid; reconnect and verify if needed. There's no need to keep the client running when shutting down just to “preserve” the connection.
Common issues and recovery after quitting
Connected, but websites won't load
First check whether the client reports a connection error, then confirm the active configuration and rules. If regular websites won't open either, temporarily turn off the system proxy to test your local connection. Once the local connection works, re-enable the proxy and check settings one at a time. Don't change routes, DNS, rules, and TUN mode all at once, or you won't know what helped.
No internet after quitting the client
If the client closes unexpectedly, Windows may be left pointing to a local proxy address even though the proxy is no longer running. Reopen the client and turn off the proxy normally. If the connection still doesn't recover, check the manual proxy settings under Windows Settings → Network & Internet → Proxy. On a managed device, don't remove settings yourself; ask your administrator.
Subscription updates, but the website won't let you in
Check the platform's regional policies, account status, and error message. Switching exit locations doesn't guarantee you'll get around platform restrictions, and frequent region changes may trigger extra checks. If you believe the route is at fault, note when it happened, the exit region, and the error, then report it through the dashboard support ticket. Don't include your full subscription credentials.
Check billing terms when choosing a service. VPN73 monthly subscriptions reset their data allowance each month on the activation date. Data add-ons remain available until used and never expire. A 30-day money-back guarantee is available. Check the plan page for current prices and allowances rather than relying on the client's connection status to estimate your balance.