v2rayN for Windows: Complete Setup Guide for the Desktop and WPF Editions

Compare the v2rayN Desktop and WPF editions, then follow the Windows setup steps for downloading, extracting, importing a subscription, and enabling system proxy or TUN. Includes antivirus troubleshooting.

At a glance

Setting up v2rayN on Windows for the first time? Choose a package that matches your system architecture, then pick the Desktop or classic WPF edition. After importing your subscription, test the local proxy explicitly before enabling the system proxy. Try TUN only if an app ignores proxy settings and needs its traffic routed through a virtual network adapter. This order also helps troubleshoot startup failures, port conflicts, and browsers that bypass the proxy after switching editions.

Choosing a v2rayN Windows Edition: Desktop vs. WPF

The “Desktop” and “WPF” labels on the download page refer mainly to the interface and release package, not to different proxy protocols. WPF uses a Windows UI framework. Whether a connection works depends primarily on compatibility between the core, node protocol, and transport settings. Don’t keep switching editions to fix a single connection failure, and don’t assume WPF is guaranteed to work with older Windows versions.

How to Choose Between the Two Editions

Desktop Edition: A Good Starting Point
  • If you don’t need the classic interface, choose the Desktop release that matches your system architecture.
  • Following a tutorial? Check which release series it covers first; button locations may differ from the classic interface.
WPF Edition: Keep the Classic Windows Interface
  • Choose the WPF release if you’re familiar with the classic menus and tray controls, or if you’re following instructions with screenshots of that interface.
  • When switching editions, close the old process and keep the application and configuration in separate folders. Verify that your subscription and routing work before deleting the old directory.

In Windows, go to Settings → System → About and check System type. Choose x64 or ARM64 accordingly. The download page shows which interface editions are available for each architecture.

“64-bit operating system” isn’t enough to choose a package; check the processor type too. For a first-time setup, prefer a release that includes the core over a minimal package. Before choosing a minimal package, read its release notes to see which runtimes or core files you’ll need to provide separately.

From Extraction to Subscription Import: Five Steps

These instructions use the common Chinese-language v2rayN 7.x interface. Depending on the minor version, the add control may appear as a plus sign in the group bar or in a menu. Look for the action name rather than trying to match its exact position in a screenshot.

  1. Extract or Install

    Choose a Windows release from the download center. Extract the entire archive to a dedicated folder you can write to, such as Apps\v2rayN under your user directory. Don’t launch the program from the archive utility’s preview window. If you downloaded an installer, follow its setup wizard instead of treating it as an archive.

  2. Launch and Check the Logs

    Open the v2rayN main program and check the message pane for core startup failures, missing files, or port binding errors. If Windows explicitly reports a missing desktop runtime, install the runtime for the matching architecture as described in the release notes. Repeatedly running as administrator won’t fix a missing dependency.

  3. Add a Subscription Group

    Open Subscription Group → Subscription Group Settings and select Add, or use the plus sign in the group bar. Enter a name that identifies the source, paste the subscription URL into the URL field, and save. A subscription URL usually fetches multiple configurations when updated. If you only have a single share link, copy it and choose Server → Import batch URLs from clipboard instead; don’t paste it into the subscription URL field.

  4. Update the Subscription

    Select the group you just created, then choose Subscription Group → Update current subscription (without proxy). Check the message pane, then confirm that nodes appear in the group. Retry with Update current subscription (through proxy) only if you already have a verified working proxy.

  5. Select a Node and Test It

    Select the server you want to use from the group list, then right-click and choose Set as active server. If the list shows latency results, don’t treat them as proof that every app can connect. Next, use the port the client is actually listening on to send a request and verify that the core, node, and routing can handle it.

System Proxy and TUN: Test the Local Port Before Changing Traffic Routing

Open Settings → Parameter Settings and check the local listening port under Core Basic Settings. The values below are common examples for reading a configuration, not settings you’re expected to enter manually. A mixed port accepts both HTTP and SOCKS requests. If the interface lists separate inbound ports, use the one that matches your test tool’s protocol.

127.0.0.1
Loopback address for testing on the same computer
10808
Common local mixed inbound port in 7.x
10809
HTTP port in some older dual-inbound configurations

Suppose the client shows 10808 as the mixed port. Keep TUN off and run the following command in PowerShell. If your port is different, replace it with the value shown in the interface. This test connects directly to the local SOCKS inbound, regardless of whether the Windows system proxy is enabled.

curl.exe --proxy socks5h://127.0.0.1:10808 --max-time 15 -I https://example.com

After the local test succeeds, select System Proxy → Automatically configure system proxy from the tray menu. In Windows, go to Settings → Network & Internet → Proxy and check the configured address and port. Then test in a browser window without a proxy extension. The system proxy tells apps that read those settings where to connect; once a request reaches the core, routing rules determine whether it goes direct or through a proxy node.

If only one app bypasses the proxy, first check whether it supports manual HTTP or SOCKS proxy settings. If you do need to route its traffic through a virtual network adapter, select Clear system proxy before enabling TUN in the main window. Grant permission when prompted, then test the app. Whether TUN captures a connection also depends on system routes, exclusions, and other virtual adapters. Check that your local network or work network still works; if not, turn TUN off to restore the previous state and investigate the routes. Don’t change both traffic-routing methods at once.

Common Problems: Subscription Errors, Antivirus Blocks, and Lost Connectivity After Exit

Updated the subscription, but the group is still empty?

Make sure you’re viewing the group you just selected, then check the update log. For a 401 or 403 error, check whether the subscription has expired and whether the full URL was pasted; ask the provider for a new URL if needed. For a timeout, confirm that your current network can reach the subscription service, or update through a verified working proxy. Don’t delete the old group after one failed update; it may still contain working nodes.

The core files disappeared right after extraction?

Open Windows Security → Virus & threat protection → Protection history and check whether the block time, file path, and detection name match this launch. If the detection is unclear, leave the file quarantined and download the same release again from the download center. If it’s blocked again, note the release version, filename, and detection name before reporting the issue. Don’t disable real-time protection or exclude the entire downloads folder just to launch the app.

The browser works, but the terminal still can’t connect?

Run the explicit proxy command from the previous section to check whether the terminal is ignoring the system proxy. If the command works but the same request fails when run directly, check the tool’s own proxy settings. Use a protocol supported by the tool and the matching inbound port. Change settings for the current terminal session or individual tool first; there’s no need to modify the entire system environment.

Why does the browser lose connectivity after v2rayN exits?

Check Windows proxy settings to see whether they still point to a local port that is no longer listening. Before exiting normally, use Clear system proxy in the tray menu; if TUN is enabled, turn it off too. If the app has already exited but Windows still points to its local proxy, restore the value that was in place before launch. On a work-managed device, don’t disable an existing organization proxy.

Download v2rayN