System proxy handles traffic only from apps that honor the OS proxy settings. TUN uses a virtual network adapter to capture traffic within its routing scope and can also handle apps that ignore those settings. If you mainly use a browser or other apps that support system proxy, start with “Set system proxy”. Enable TUN as needed when you also want to capture traffic from apps that ignore the OS proxy. Stop other VPNs first, and grant any permissions requested when you enable TUN.
Check the system type in Windows System Information first: choose v2rayN-windows-64.zip for a 64-bit Intel/AMD PC, v2rayN-windows-arm64.zip for an ARM64 device, or v2rayN-windows-86.zip for a 32-bit x86 system. The standard ZIP uses WPF and is a reasonable starting point on Windows. If you want the Avalonia interface, choose a ZIP for the same architecture with -desktop in its name. Prefer the corresponding verified backup on this site’s download page; use that page’s official latest-download link for other architectures or interface variants. Extract all files to a writable folder, retain bin and other subfolders, then run v2rayN.exe.
Open “Subscription group settings”, add a name and the complete subscription URL, save and update that group. Select a returned node as the active profile. If the update fails, inspect the log, URL validity and network access. If it reports success but returns no nodes, check that the response is a node-subscription format supported by v2rayN, not a login or ordinary web page. Separately check the selected core’s protocol support if imported nodes cannot run. On Windows, standard share links can also be pasted with Ctrl+V outside an input field in the main window.
Locate the actual data directory from the app first. Disable system proxy and TUN, exit, then back up the complete data directory and record groups, routes, DNS and the selected core. Portable ZIP builds store data in the extracted folder; installed builds use the system’s user-data directory. Verify subscriptions, browsing and normal networking after stopping before replacing your daily setup.
Confirm the node is active, the core started without errors and the OS proxy points to the client’s actual listening address and port. Enable “Display Log” and make a real request to a known destination to distinguish DNS, routing and node failures. Custom Mihomo profiles also need their own port checks. Verify with a browser that honors system proxy first. If only one app fails, check whether it bypasses that proxy before deciding to test TUN.
Disable TUN and restore the verified system-proxy connection first. Stop other VPNs, then inspect the current core’s startup log, profile loading and required TUN permissions. Address the first configuration, DNS, file or permission error. Retain the original configuration and change one setting at a time, rather than changing the node, DNS and core together. When retesting TUN, check both the destination and a normally direct site; return to the verified setup if access fails.
Check whether the OS proxy still points to v2rayN’s stopped local listener. Reopen the app, select “Clear system proxy”, disable TUN if still enabled and then exit. If the app cannot open, remove the manual proxy pointing to that stopped port in OS network settings. Test a normally direct site to confirm recovery. If it still fails, check other VPNs and the system network connection instead of repeatedly changing nodes.
