v2rayN for Windows: Setup Guide

1. Choosing Between the Desktop and WPF Editions

v2rayN manages servers, subscriptions, routing, and local proxy access; the selected core handles the actual connection. The desktop edition uses a cross-platform interface, while the WPF edition retains the classic Windows interface. The difference does not come down to one supporting VLESS and the other not: protocol support also depends on the selected core and its version, as well as compatible server settings.

In Windows 11, open Settings → System → About and check System type. Most Intel and AMD PCs use x64; ARM devices should not treat x64 and ARM64 as interchangeable native architectures. If the download page does not offer a compatible build, check the release's system requirements instead of repeatedly trying to run an incompatible program.

2. Installation Folder and Runtime Requirements

Choose a Windows package from the download page. Depending on the release, you may get an installer or an archive. Follow the installer's steps, or fully extract the archive and run v2rayN.exe from its folder. Do not launch the main program from the archive preview: only the executable may be temporarily extracted, leaving dependencies and core folders unavailable.

1. Choose a folder

   You can put a portable build in a user-writable folder such as D:\Tools\v2rayN. Avoid temporary and protected system folders; the app needs to save settings, logs, and subscription data.

2. Extract all files

   Keep the folder structure intact. If you are using an installer, complete the installation; the folder containing the installer is not the app's data folder.

3. Check dependencies

   If startup prompts you to install .NET, note the framework name, major version, and architecture shown. For a WPF package, install the requested Desktop Runtime. Installing only the SDK or a runtime for another major version may not resolve the issue.

4. First launch

   Start the app as a standard user first. Open Settings → Options to check the basic configuration, then review the main window's log. Make sure the interface is not open while the proxy core has failed to start.

3. Importing a Subscription and Choosing a Server

Subscription URLs often contain access credentials, so treat them like passwords. Do not include the full URL in public screenshots. If opening it displays a long string of text, that does not necessarily mean the URL is invalid: the client needs to parse the subscription response, not display a regular webpage. Check the subscription itself if it returns a login page, error page, or expiration notice.

1. Add a subscription group

   In the main window, open Subscription Group → Subscription Group Settings and choose the add option. Enter a recognizable name and the subscription URL, then save. Depending on the interface version, the add option may appear as “Add” or a plus sign.

2. Update the subscription

   Return to the Subscription Group menu. For the first update, choose Update all subscriptions (without proxy). If the interface has a separate Update via proxy option, leave it off and first check whether the subscription is reachable directly.

3. Check the result

   Check the log for the update result, then switch to the relevant group. If the update succeeds but the list is empty, clear the search box and server filters, and make sure you have not selected a different group.

4. Set an active server

   Select a server in the list, right-click, and choose Set as active server. Wait for the core to load the configuration before testing the connection. Clicking a row alone may not change the active server.

If the subscription is only reachable through a proxy, first connect to a working server, then choose Update all subscriptions (via proxy). This option cannot establish the first connection by itself. After importing VLESS, VMess, or other servers, keep the subscription's transport, TLS, SNI, and other settings unless there is a specific reason to change them. Avoid changing multiple fields just to see what happens.

4. Windows Proxy Settings and Local Ports

After setting an active server, use the system tray menu and choose System proxy → Set system proxy. If your version lists these commands directly in the tray menu, select the matching option. The system proxy setting tells apps that honor Windows proxy settings to send requests to the local proxy port; it does not automatically route every program through the proxy.

The ports above are examples for troubleshooting, not fixed defaults for every version. Open Settings → Options to check the current local listening port and listener type. Newer configurations may offer a mixed port that accepts both HTTP and SOCKS traffic. Some older configurations use separate ports; do not assume an adjacent port number is an HTTP listener based on an old guide.

curl.exe --proxy http://127.0.0.1:10808 --connect-timeout 15 -I https://www.microsoft.com/

Use this command only if the port accepts HTTP proxy traffic. Receiving an HTTP response header confirms that this request used the specified proxy; it does not mean every site or route is working. If the test says it cannot connect to the proxy, check the local listener. If the remote handshake fails, check the server. Start with a routing ruleset you understand; do not edit DNS and custom routes at the same time during your first test.

5. When to Enable TUN Mode

Consider TUN mode only if your browser works through the system proxy but an app that ignores system proxy settings still cannot connect. TUN uses a virtual network interface to capture traffic covered by its configuration and involves routing and DNS. A working system proxy does not guarantee that TUN permissions, drivers, or network adapters are ready.

• Save a baseline first: Note the working server, system proxy status, and routing rules so you have a clear point to roll back to.
• Then address permissions: Use the TUN mode switch in the main window. If your version requests elevated permissions, restart or grant permission as prompted. There is no need to run the app as an administrator for ordinary proxy use.
• Watch the startup log: Confirm that the core used by TUN starts successfully. Look for permission errors, interface creation failures, and routing errors; do not rely on the switch's color alone.
• Isolate network conflicts: Other VPNs or virtual network adapter software may affect routing. During troubleshooting, use only one traffic-capture solution at a time. On a managed device, follow your organization's network policies.
• Roll back immediately if something breaks: Turn off TUN and test the system proxy again. If that restores connectivity, check TUN's DNS, routing, and network adapter settings first; do not delete all your subscriptions.

Whether to keep the system proxy enabled as well depends on your configuration and use case; do not assume both must always be on. When troubleshooting for the first time, test each method separately. If an explicit proxy request succeeds but access fails under TUN, investigate the traffic-capture path instead of repeatedly switching the same server.

6. Troubleshooting Startup, Ports, and Web Access

Troubleshoot in this order: main program → core → local port → server connection → app settings. A visible window only confirms that the interface started; a latency result does not prove that your browser is using the proxy. Save a section of the log from the time of failure and investigate the specific error. This is more useful than reinstalling the client, changing ports, and switching routes all at once.

netstat -ano -p tcp | findstr LISTENING | findstr ":10808 "

The final column in the command output is the PID. If there is no output, check that the port is correct and the core actually started. For an expired certificate, name mismatch, or TLS handshake failure, check the Windows clock and verify the subscription's SNI, server address, and transport settings. Do not treat “skip certificate verification” as a general fix. HTTP proxy protocol and HTTPS encryption to the destination are separate layers; do not change the local listener type just because a webpage uses HTTPS.

7. What to Keep Before Updating or Migrating

Once everything works, you can consider convenience settings such as launching at startup and automatically updating subscriptions. Before updating, close v2rayN and its core, then back up the actual data folder. Its location can vary by installation method, so do not infer it from the executable's path. When moving between the desktop and WPF editions, reimport your subscription and check routing and ports. Do not overwrite the entire folder until you have confirmed that the configurations are compatible.

• Subscription details: Keep your group names and trusted subscription URLs. Do not share backup files publicly.
• Local settings: Record the listening port, system proxy mode, routing rules, and whether TUN is enabled.
• Manual configuration: Back up self-hosted servers and custom rules separately. Reimporting a subscription will not restore them.
• Test again after updating: Check that the core starts, the subscription updates, and a one-off proxy request succeeds. Then test TUN and startup behavior.

Once these checks are complete, everyday use mostly involves updating subscriptions, choosing an active server, and checking the proxy status. If something goes wrong, follow the same troubleshooting order to distinguish installation issues from network problems and roll back to the last working configuration.