Sep 15, 2026 · Platform Guide · About 8 min read

How to Install v2rayN on Windows: WPF vs. Desktop, System Proxy, and Startup

Choose the right v2rayN package for Windows, extract it, import a subscription, configure the system proxy, and enable startup at sign-in—with practical tips for avoiding common setup issues.

At a glance

For your first v2rayN setup on Windows, choose a package for your system architecture, extract it to a permanent folder, then import a subscription and select a node. Test with a browser that follows the Windows system proxy, and enable startup at sign-in only after it works. If the app stops responding after a package change, or the tray icon appears but you can't get online, follow these steps to pinpoint whether the issue is startup, the node, or proxy routing.

Choosing between the WPF and desktop versions

In Windows, open Settings → System → About and check System type. For an x64-based processor, choose the Windows x64 package. For an ARM-based processor, look for the Windows ARM64 package on the release page. Don't rely on “64-bit operating system” alone: x64 and ARM64 are both 64-bit, but they use different architectures.

Two interface packages for Windows

WPF version

  • Uses a Windows-specific WPF interface. If your guide's screenshots are from the WPF version, choosing the same package makes it easier to follow along.
  • If the package requires a separate .NET Desktop Runtime, install the major version and architecture specified in the release notes. The standard .NET Runtime is not a substitute for the desktop runtime.

Desktop version

  • Uses a cross-platform desktop interface. Make sure the download is marked for Windows and matches your system architecture.
  • Some buttons may be in different places than in the WPF version. Look for settings by name, such as “Subscription groups” or “System proxy,” rather than relying on locations shown in older screenshots.

WPF and desktop refer to the interface build, not the node protocol. Check the architecture, runtime requirements, and whether the core is included before choosing an interface.

Extract the files, import a subscription, and select a node

You must fully extract the archive before running the app; don't launch the main program from the archive preview. The steps below use the common v2rayN 7.x interface. Menu names may vary slightly between versions.

  1. Extract the entire archive

    Right-click the archive and choose “Extract All.” Extract it to a writable folder in your user profile that you won't move, such as Apps\v2rayN. Don't extract only v2rayN.exe or put the files in a temporary folder. Configuration and startup paths depend on the folder location.

  2. Run the main program

    Run v2rayN.exe from the extracted folder. If no window appears, check the taskbar notification area for a tray icon. If a runtime prompt appears, note the framework and architecture it names, then install what the current package requires. Repeatedly trying to run the app as an administrator won't fix a missing runtime.

  3. Add a subscription

    Open “Subscription groups” → “Subscription group settings,” add a group, and enter a recognizable name and the subscription URL. Save it, return to the main window, and select the group. Then choose “Update current subscription” from “Subscription groups.” If there's only one group, you can also choose “Update all subscriptions.” For the first update, if no working proxy is available, use the update option that doesn't go through a proxy.

  4. Set an active node

    In the updated list, right-click a node and choose “Set as active server.” Clicking a row usually only selects it; it doesn't make the node active. Check the logs for core startup errors, then enable the system proxy from the tray menu. Seeing nodes in the list only confirms that the subscription was retrieved or imported—not that a node works.

Turn the Windows system proxy on or off

Right-click the v2rayN icon in the notification area and open “System proxy.” For your first test, choose “Set system proxy” and leave TUN off. The Windows system proxy affects apps that follow system proxy settings; it doesn't route traffic for the entire computer. Apps with their own proxy settings may behave differently during testing.

First test

Tray menu option
System proxy → Set system proxy
Where to check in Windows
Settings → Network & internet → Proxy
Test with
A browser that uses the system proxy

Check that the manual proxy address and port match the client's active listener, then open a familiar website.

Test with a direct connection

Tray menu option
System proxy → Clear system proxy
Check in Windows
“Use a proxy server” no longer points to the local client
How to compare
Open the same website again in the same browser

If your organization configured a proxy, note the original settings first and restore them afterward as instructed by your administrator.

“Do not change system proxy” preserves the current settings; it doesn't turn the proxy off. If a local proxy address was set earlier, choosing this option and exiting may leave your browser trying to connect to a local port that is no longer running. When you're done using the proxy, clear the system proxy set by the client before exiting from the tray.

127.0.0.1
A loopback address on your computer, not a remote node address
10808
Common local port setting; use the value configured in the client
10809
HTTP port used in some older configurations; don't copy it into a newer setup

Open Settings → Parameter settings to check the local listener configuration. Some versions use a mixed inbound listener that accepts both HTTP and SOCKS traffic on one port; others use separate ports. When checking the Windows proxy settings, use a local listener port that supports HTTP—not the server port shown in the node details.

Enable startup at sign-in and verify it works

First confirm that the app starts manually and the proxy works. Then open Settings → Parameter settings, enable “Start automatically on boot” on the v2rayN settings page, and save. Startup usually means the app runs after you sign in to Windows; it doesn't run at the sign-in screen. Startup only launches the app—it doesn't confirm that the system proxy is active.

Common first-time setup issues

The subscription is saved, but why is the node list empty?

Go to “Subscription groups” → “Subscription group settings” and check for extra spaces in the URL and disabled updates for the group. Saving the URL only creates the group—you still need to update it. Check the logs to see whether the request timed out, the server refused the connection, or the response couldn't be parsed. If access is denied, first confirm that the subscription is valid; changing the core won't fix an access issue with the URL.

The speed test shows a result, but why won't my browser load anything?

First check which row was tested, then confirm that it's the active server. A connectivity test and a browser request don't follow the same path. Once you've selected the right node, make sure the browser follows the Windows system proxy, then check that the port set in Windows matches v2rayN's HTTP or mixed listener.

The log says a port is already in use. Should I change it?

Check which listening address and port are named in the error. Make sure v2rayN running from the old folder has been exited from the tray, then launch the current version. If another program that needs the port is using it, change the local listening port in “Parameter settings.” Restart the client, reapply the system proxy, and check whether Windows still has the old port configured.

I switched to the desktop version. Why didn't my old settings carry over?

Starting the app from a new folder doesn't make it read data from the old folder. Exit both instances, back up the old version's data, then follow the migration instructions for the current version. If you only need your nodes, create the subscription group again in the new version and update it, then restore routing and startup settings as needed. Don't overwrite all the program files in the new folder with files from the old version just to restore the node list.

Download the client