v2rayN for Windows: Installation, Setup, and WPF vs. Desktop

Install v2rayN on Windows, import a subscription, and compare the WPF and Desktop builds. Fix common issues like missing runtimes, antivirus blocks, and non-English paths.

At a glance

Choose a package for your Windows architecture first, then pick WPF or Desktop. During initial setup, verify three things separately: whether the subscription fetches nodes, whether the core starts, and whether your browser uses the system proxy. When something fails, troubleshoot that step before changing the UI, node, and routing settings all at once.

WPF or Desktop: Check Your Architecture, Then Choose a UI

Open Windows Settings → System → About, then check System type under Device specifications. Choose the Windows x64 package for an x64-based system. For an ARM-based system, choose the matching Windows ARM64 package if available. Both may be labeled 64-bit, so don’t rely on that alone. WPF and Desktop are UI variants, not proxy protocols. Whether a subscription works depends on its node configuration and the core actually running.

The Two Windows UI Variants

WPF
  • Uses Windows’ WPF UI framework and may suit users who prefer the familiar Windows-style interface.
  • If the package you chose requires a separate runtime, Microsoft.WindowsDesktop.App in the startup prompt refers to the .NET Desktop Runtime.
Desktop
  • Uses the Avalonia UI framework. Even if you’ve seen the same interface on another platform, choose the Windows package here.
  • The menus may differ from WPF. Check the release notes to see whether the package includes a runtime and core; the word “Desktop” alone doesn’t tell you.

If your current version works, there’s no need to switch UI variants just to import a subscription. For a first install, choose a package that matches your architecture and clearly documents its dependencies.

Extract, Launch, and Import a Subscription

These steps use the common Windows UI in v2rayN 7.x. Menus may move between minor releases. If you can’t find a toolbar button, look for the same command in a menu. Don’t add a subscription URL in Windows network settings.

  1. Extract All Files

    For a ZIP download, right-click it in File Explorer and choose “Extract All.” Extract it to a dedicated folder your account can write to, such as Tools\v2rayN in your user folder. Don’t run the app from the ZIP preview or extract only the main executable; keep the core and other bundled files in their original folder structure.

  2. Launch the App

    Run v2rayN.exe from the extracted folder. If you don’t see the main window, check the hidden icons in the notification area. You don’t need to enable TUN to import a subscription or test the standard system proxy, and running as administrator is not a general fix for startup problems.

  3. Add a Subscription

    In the main window, go to Subscription Group → Subscription Group Settings and click Add. Enter a recognizable name and the full subscription URL, then save. Subscription URLs often contain access credentials, so keep the query parameters when copying. Redact the entire URL before sharing a screenshot.

  4. Fetch Nodes

    From the Subscription Group menu, select Update All Subscriptions (without proxy), then switch to the group you just created to view its nodes. Saving the URL only creates the group; it doesn’t fetch the subscription. If a direct connection times out and you already have a verified working proxy, try the corresponding update option that uses a proxy.

  5. Select a Node

    Right-click a node in the list and choose Set as active server. Confirm that the main window shows the node you selected, then check the logs for core startup or listen errors. Seeing a node in the list doesn’t mean it’s active or working.

Check the Local Port and System Proxy

First confirm that the core is listening locally, then configure your browser to use the system proxy. The ports below are common troubleshooting examples, not fixed values for every 7.x release. Check the local listener settings under Settings → Parameter Settings and the startup log for the actual values.

10808
Common local proxy port; may be a mixed listener
10809
HTTP port used by some separate-listener configurations

Local Listener Check

Address
127.0.0.1
Port
Use the client settings and startup log as the source of truth
Before You Test
The core is running, and the port accepts HTTP proxy requests

A mixed port accepts both HTTP and SOCKS requests. Don’t enter a SOCKS-only port as an HTTP proxy.

Check the System Proxy

In the Client
Notification area icon → System Proxy → Set system proxy
In Windows
Settings → Network & internet → Proxy
Test in
A browser configured to use the system proxy

The system proxy controls which apps hand requests to the client. Routing rules determine which outbound the core uses for requests it receives.

To test the local proxy separately from your browser settings, specify the proxy in PowerShell. The example below applies only if you’ve confirmed that 10808 accepts HTTP proxy requests; replace the port if your listener uses a different one.

curl.exe --noproxy "" --proxy http://127.0.0.1:10808 --connect-timeout 5 --max-time 15 -I https://example.com/

Troubleshoot Startup, Subscription, and Browser Connection Issues

A .NET install prompt appears on launch. Which one do I need?

Choose a runtime that matches the framework name, version, and architecture in the prompt. For example, if it lists Microsoft.WindowsDesktop.App, version 8.0, and x64, install the matching .NET 8 Desktop Runtime x64, not just the standard .NET Runtime. You can check with dotnet --list-runtimes. If multiple runtime architectures are installed, confirm the command lists the architecture the app needs.

The app is there. Why does the log say the core is missing?

First check whether the release package includes the required core and was fully extracted. Then open Windows Security → Virus & threat protection → Protection history and look for an entry matching the startup time and file path. Don’t disable protection or exclude the entire folder just to launch the app. If the source or alert is unclear, stop running it and get a trusted release package. For managed devices, contact your administrator.

The folder path contains non-English characters. Why can’t the app find a file?

Exit the client from the notification area, then fully extract the same package into a dedicated folder that’s writable by your user, has a short path, and contains no non-English characters. Check the full path, not just the final folder name. Test from the new folder without mixing or overwriting the old one. Non-English characters in a path don’t automatically cause a failure; investigate path parsing, path length, or permissions only if the same steps work after moving the files.

Subscription updates keep timing out. Should I change the core?

Start with the subscription update log. A failed subscription fetch is different from a failed node connection. For a timeout, check whether your current network can reach the subscription service and whether the selected update method depends on a proxy that isn’t available yet. For 401 or 403 responses, check whether the subscription has expired or its access permissions have changed. If the log reports a certificate error, verify the Windows date, time, and time zone. Don’t disable certificate validation.

Why does my browser lose its connection when I close the client?

If Windows still points to a local proxy that has stopped listening, the browser will keep trying to connect to an unavailable endpoint. Restart the client, select Clear system proxy from the notification area’s System Proxy menu, then exit normally and check the result on Windows’ Proxy settings page. If you were using a work proxy, restore its original settings rather than turning off every proxy option.

Download the client