Setting up v2rayN on Windows for the first time? Choose the package for your system architecture and extract all its files. Then import a subscription, select a node, and enable the system proxy. To troubleshoot, check each layer in order: can the interface open, can the core listen, can the node connect, and is the app using the proxy? This keeps runtime, port, and subscription issues separate.
WPF or Desktop: Which Edition Should You Choose?
WPF and Desktop refer to two client interfaces, not two node protocols. WPF uses Windows' WPF interface framework; the Desktop edition described here uses a cross-platform interface framework. With the same client version, whether a node works mainly depends on the core in use and its version, the node settings, and network conditions. Don't assume the Desktop package includes a core or runtime just because of its name.
WPF edition
RecommendedThe classic Windows interface. Choose this edition if you're familiar with WPF or following a WPF guide to find the tray icon or settings menus. If a framework-dependent package reports a missing runtime, check that the Windows Desktop Runtime version and architecture match the requirements.
Best for: Windows users who prefer the classic interface and familiar controls.
Desktop edition
Uses a cross-platform interface, so its settings and window layout may differ slightly from the WPF edition. Choose the Windows package when downloading. Check the package notes to see whether it includes a runtime or the required core.
Best for: Users who prefer the Desktop interface or want a more consistent layout across desktop platforms.
Before downloading, go to Windows Settings → System → About and check System type. Choose x64 or arm64 as listed on the download page. When switching editions to troubleshoot, close the old process and extract the new package to a separate folder. Don't overwrite one edition's files with the other's or run both clients at once; they may compete for the same local port.
Extract the Files, Import a Subscription, and Enable the System Proxy
These steps use the common Chinese-language interface in v2rayN 7.x. Menu labels may vary between builds. For example, an update option may show “via proxy” in parentheses. Check whether you're updating the current group or all groups, and whether the update connects directly or through a proxy.
-
Extract All Files
Choose the package for your system architecture. If you downloaded an archive, use “Extract All” to unpack it into a separate folder you can write to. Don't run the program from the archive preview or drag only the main executable to your desktop. While troubleshooting for the first time, keep all files together in the same folder and leave startup on boot disabled.
-
Launch the Main Program
Open
v2rayN.exefrom the extracted folder and check that the main window appears. If the window closes but the icon remains in the taskbar notification area, open the existing window from the tray. A visible interface confirms that the client has started; check the logs after selecting a node to see whether the required core is available. -
Add a Subscription Group
Go to “Subscription Group” → “Subscription Group Settings,” add an entry, enter a name and the complete subscription URL, then save. If you have only a single
vmess://orvless://link, copy it and use “Import from clipboard” in the main window. Don't paste a single link into the subscription URL field. -
Update the Subscription and Select a Node
Switch to the new group, then choose “Update current subscription (without proxy)” from “Subscription Group” to avoid relying on a proxy that isn't configured yet. Once nodes appear, right-click one and choose “Set as active server.” Confirm the active selection changed, then check the logs for core startup or listener errors.
-
Enable the System Proxy
Right-click the tray icon and choose “Set system proxy” → “Automatically configure system proxy.” In Windows, go to Settings → Network & Internet → Proxy and check the current settings. Then use a browser that follows the system proxy to open a site you can normally reach reliably. For the first test, leave TUN disabled so its settings don't complicate troubleshooting.
Local Ports and Windows System Proxy Settings
The system proxy points to a proxy endpoint on your computer, not the node server's address or port. In v2rayN 7.x builds using a mixed inbound, the common default listening port is 10808. Existing settings, other versions, and different inbound configurations may use another port. Check the local listener settings under “Settings” → “Parameter Settings” and the startup logs first, then compare the port numbers in Windows and the app.
v2rayN local endpoint
- Listen address
127.0.0.1(local machine)- Listen port
10808(example; check your current settings)- Inbound type
- A mixed inbound accepts both HTTP proxy and SOCKS requests. Separate inbounds use different ports.
For local use only, you don't need to enable “Allow connections from the LAN.”
Windows proxy settings
- Address
127.0.0.1- Port
- Use the current inbound that supports HTTP proxy
- Applies to
- Apps that use the Windows system proxy settings
If an app has its own proxy settings, check its address, port, and proxy type as well.
If a browser works but another app on the same computer doesn't use the proxy, that doesn't mean the node is broken. Check whether the app follows the system proxy or has its own HTTP or SOCKS settings. Before closing v2rayN, choose “Clear system proxy” from the tray, then exit. If your organization or school configured a proxy before, restore those original settings after exiting. Don't leave the system proxy pointing to a port that's no longer listening.
Check for Port Conflicts in PowerShell
If the logs show address already in use or a similar bind error, first check which process is listening on the port. The examples below use 10808; replace it with your actual port if you've changed it. The first command shows the listening address and process ID. The second only tests whether a TCP connection to the local port succeeds.
Get-NetTCPConnection -LocalPort 10808 -State Listen |
Select-Object LocalAddress, LocalPort, OwningProcess
Test-NetConnection -ComputerName 127.0.0.1 -Port 10808
- A listener is present, but its owner is unclear: In Task Manager, open the Details tab and match the PID to
OwningProcess. The core may run as a separate process launched by the client; don't end it just because its name isn'tv2rayN.exe. Close the old client first and check whether the listener disappears. - Another app is using the port: Leave any unfamiliar process running. Check that the alternative port isn't already in use, then change the local proxy port under “Settings” → “Parameter Settings.” Save and restart the core, then choose “Automatically configure system proxy” again and confirm Windows no longer points to the old port.
- Nothing is listening: Return to the client and check the active node and core logs. Resolve any missing core, configuration loading, or bind errors first.
TcpTestSucceeded : Trueonly means that a program accepts connections on the port; it doesn't prove the node is reachable or web traffic is going through the proxy.
Common Setup Problems
The app asks me to install .NET. Which version do I need?
Check the framework name, major version, and architecture shown in the prompt. If the WPF edition reports that Microsoft.WindowsDesktop.App is missing, install the matching Windows Desktop Runtime—not just the base .NET Runtime. Then retry from the original extracted folder. If the package notes say it includes a runtime, make sure you're launching that copy, not a shortcut pointing to an older folder.
I added a subscription group, but no nodes appear. Why?
Saving a group only stores its URL; it doesn't update the subscription. Switch to that group and choose “Update current subscription (without proxy),” then check the logs for a timeout, HTTP error, or parsing failure. Use “Update via proxy” for comparison only if you already have a known-working node. If the response is a login page or says the URL has expired, ask the provider to confirm the subscription URL and its validity period.
Nodes appear in the list, but web pages won't load after I enable the system proxy. Why?
First check that you've selected “Set as active server,” then review the core logs, local listener, and Windows proxy port. If the local endpoint is working but the logs show a remote connection timeout, try a known-working node on the same network for comparison. For certificate- or time-related errors, check the Windows date, time, and time zone, then review the node settings. Don't disable certificate validation to silence the warning.
I closed the window, but the port is still in use when I reopen the app. Why?
Closing the window may only minimize v2rayN to the notification area. Expand the tray, find the running v2rayN instance, choose “Clear system proxy,” then select “Exit” to close it. If the port is still listening, use the PID method above to identify the process. In particular, check whether another copy of v2rayN in a different folder starts with Windows.