v2rayN Crashes on Startup, v2rayNG Won’t Open: Runtime and Permissions Troubleshooting

Common causes of startup crashes, ranked by frequency: missing .NET Desktop Runtime, antivirus blocking the core, folder write permissions, Android VPN access, and battery optimization—with fixes for each.

At a glance

First pinpoint when the problem occurs: on launch, when you connect, or after the screen locks. Whether v2rayN closes as soon as you double-click it, its core fails to start, or v2rayNG disconnects after connecting, check the relevant logs, runtimes, file permissions, and system settings. Don’t start by wiping your configuration or reinstalling.

First, distinguish an app crash from a core failure or background disconnect

A disappearing window doesn’t always mean the process crashed. On Windows, check the hidden icons in the notification area, then use Task Manager to see whether v2rayN is still running. If you can reopen the main window from the system tray, this isn’t a startup crash. On Android, distinguish between returning to the home screen while the VPN stays connected and the VPN actually stopping. Check the system VPN page instead of relying on the app’s presence in Recents.

When it happensCheck firstLeave these alone for now
The main window never appears after double-clicking, and the process exitsRuntime prompts, application event logsSubscriptions, routing rules
The main window opens, but an error appears when you connectCore files, write permissions, local ports, or VPN permissionSystem power plan
Works in the foreground but disconnects after the screen locksAndroid battery restrictions, and whether it also disconnects with the screen onClient installer

Use the first specific error to guide your troubleshooting

Note the time, reproduce the issue once, and save only the first specific error from that failed attempt. Later “startup failed” messages usually describe the result, not the cause. Change one thing at a time and repeat the same steps to see whether the change helped.

v2rayN crashes when opened: check the .NET Desktop Runtime

Start by checking which package you installed and what the error says; not all versions use the same deployment model. If a WPF package that depends on a shared runtime reports that Microsoft.WindowsDesktop.App is missing, install the .NET Desktop Runtime for the required architecture and major version. Installing only the base .NET Runtime or ASP.NET Core Runtime won’t provide this desktop component. A self-contained package shouldn’t be assumed to need a runtime just because nothing happens when you double-click it.

Time of launchExact errorComponent checkOne fix at a timeRetest under the same conditions
  1. If a dialog reports a missing component, note the framework name, version, and architecture. For example, if it lists Microsoft.WindowsDesktop.App, 8.0.0, and x64, check for the x64 .NET 8 Desktop Runtime and use the latest available servicing release in that series. This example doesn’t mean every v2rayN package requires .NET 8.
  2. Run the command below in Windows Terminal to see whether the corresponding framework is listed. The output shows the runtimes visible to dotnet in that terminal; if you installed runtimes for different architectures, one list may not show everything on your PC. You can also check the runtime name and architecture under Settings → Apps → Installed apps.
  3. If there’s no dialog, open Event Viewer → Windows Logs → Application and look for .NET Runtime or Application Error at the time you noted. Check the application name and exception details. Without evidence of a missing runtime, don’t install multiple major versions at random.
dotnet --list-runtimes

v2rayN opens, but the core won’t start: check for blocks, folder issues, and port conflicts

Check the client log for the core path, configuration path, or listening address. The interface opening only confirms that the UI is running; it doesn’t mean the core executable is present, can write its configuration, or can bind to a local port.

Error: The system cannot find the file specified.

Cause: If the error points to a core file, it may not have been fully extracted, may have been moved, or may have been quarantined. Fix: Check the path in the log, then look for a matching entry under Windows Security → Virus & threat protection → Protection history.

Error: Access is denied.

Cause: If the error occurs while writing the configuration, your account may not have write access to that folder, or a security policy may be blocking the write. Fix: Back up your configuration, then test a fully extracted portable package in a local folder your standard user account can write to. Check the permissions or security history for the original path.

Error: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Cause: Another process may already be using the address and port the core is trying to listen on. Fix: Use the port in the log to identify the process. Close any duplicate client you no longer need, or change the relevant local listening port in v2rayN under Settings → Parameter Settings.

If Protection history shows a quarantine, verify the detected file, threat name, and package source first. Don’t disable protection across your whole PC just to test the launch, and don’t restore files from an unknown source. On a work- or school-managed PC, keep the record and contact your administrator if application control policies are in place. You also don’t need to run the app as administrator long-term to troubleshoot folder access: fully extract the portable package to a local folder writable by your user account. For an installed version, use the installer to repair it rather than moving the program folder.

10808
Example: check a local listening port against your current configuration
10048
Windows socket address already in use error code
netstat -ano | findstr ":10808"

Replace the port in the command with the actual value from the log. For a TCP conflict, confirm that the matching line shows the local address, port, and LISTENING state, then use the PID in the last column to identify the process under Details in Task Manager. A match on a remote port alone doesn’t indicate a local listening conflict. If you change the local port, update any browser or other tool that still uses the old one.

v2rayNG won’t connect: check Android VPN permission

If v2rayNG opens but returns to a disconnected state when you tap Connect, first check whether Android allows it to establish a VPN. The system VPN confirmation prompt is not the subscription import screen. Settings paths vary by device maker; if you can’t find the menu, search for “VPN” in Android Settings.

  1. With the app open in the foreground, tap Connect and confirm the Android VPN request after checking which app is requesting access. If you tapped Cancel, return to the app and try again. Importing a node successfully doesn’t grant VPN permission.
  2. Usually, only one VPN can be active per user or profile. Check existing connections under Settings → Network & internet → VPN. You can disconnect an old VPN you manage and try again. If an always-on VPN or device management policy is active, check what it’s for before changing it; don’t override your organization’s policy.
  3. If the app won’t even open, VPN permission isn’t the first thing to investigate. Note your Android version, v2rayNG version, package architecture, and whether you recently upgraded. If the issue occurs only when you select a particular configuration and tap Connect, compare it with one that used to work to determine whether the problem is that configuration or the app as a whole.

v2rayNG disconnects when the screen locks: check battery optimization

Battery optimization can explain why a connection works in the foreground but drops after you switch apps or lock the screen. It doesn’t explain every startup failure. On the same network, compare a foreground session with one while the screen is locked. If it disconnects with the screen on too, check the connection error in the log, then see whether the network is switching between Wi-Fi and mobile data.

Before reinstalling, clearing data, or asking for help

I installed .NET, so why does v2rayN still close as soon as I open it?

Check the framework and architecture in the startup prompt again. For example, if an x64 package requires Microsoft.WindowsDesktop.App, seeing only Microsoft.NETCore.App or having the Desktop Runtime installed for a different architecture doesn’t confirm that the dependency is met. If the prompt disappears but the app still exits, check the application events at the new timestamp instead of relying on the earlier diagnosis.

It started crashing after an upgrade. Can I test it in a new folder first?

Yes. For the portable version, keep the old folder and configuration. Extract the full package for the same version into a new writable folder without copying the old configuration, then check whether the app opens with a clean setup. If it does, restore settings one at a time. Don’t mix old and new core files in the same folder, or it’ll be difficult to identify what caused the difference.

What’s the difference between clearing cache and clearing storage on Android?

Under App info → Storage & cache, clearing cache usually removes only temporary data. Clearing storage resets the app and may delete subscriptions, nodes, and preferences. If the app opens, use its export feature to back up your data first and make sure the backup can be read. Without a backup, don’t start by clearing storage.

What should I include when asking for help with logs?

Include your OS version, client version, package type, when the issue occurred, what triggered it, and the first error. Remove subscription URLs, node credentials, full share links, and account names exposed in file paths. If the issue started only after locking the screen or updating, mention what changed.

Download v2rayNChoose a platform and package