· Troubleshooting · 8 min read

v2rayN Crashes on Startup: Check .NET Runtime, Folder Permissions, and Config Files

Does v2rayN close right after you open it? Check the .NET Desktop Runtime, folder write access, and config files in order. Includes Android crash troubleshooting.

At a glance

On Windows, first check whether the v2rayN process has actually exited. Then use startup logs to tell a missing runtime from a folder write failure or unreadable config. If crashes began after an upgrade, keep the old folder and launch the same build from a clean new folder. On Android, determine whether the app itself closes or the VPN service stops after you tap Connect.

Check whether v2rayN has actually exited

A disappearing window doesn't necessarily mean the process crashed. Expand the Windows notification area and right-click the v2rayN icon to reopen the main window. You can also press Ctrl + Shift + Esc and check whether v2rayN.exe is still running under the Task Manager's Details tab. If the process is still running but the interface is unresponsive, record it as a frozen UI rather than repeatedly reinstalling runtimes.

Process statusStartup logsRuntime architectureFolder permissionsIsolate the config

Check the .NET Desktop Runtime and app architecture

For Windows builds that depend on the system .NET installation, check the framework name, version, and architecture in the error. If a WPF build requires Microsoft.WindowsDesktop.App, having Microsoft.NETCore.App installed doesn't mean the desktop framework is installed too. Self-contained builds include their own runtime; if extraction was incomplete, extract the full package again instead of adding DLLs to Windows one by one.

dotnet --list-runtimes

Run the command above in PowerShell. If the error requires x64 Microsoft.WindowsDesktop.App 8.0.0, check that the x64 runtimes include a compatible 8.0 desktop framework—don't dismiss the error just because some .NET entry appears in the list. The version here only illustrates how to read an error; not every v2rayN build requires it. The command lists runtimes visible to the dotnet executable currently being called. If both x86 and x64 are installed, use the architecture and runtime search path shown in the error. If the command isn't found, that alone doesn't prove the system has no runtime installed.

Error: You must install or update .NET to run this application.

Cause: The app can't find a compatible .NET framework. Fix: Install the runtime that matches the prompt's Framework, Architecture, and version, then test the same copy of the app again.

Error: System.UnauthorizedAccessException

Cause: Access to a file or folder was denied. Fix: Check the actual path in the event details. If the app needs to write inside its folder, test the same build in a new folder that your account can write to.

Test folder access and isolate the old config

In the data folder named in the logs, try creating a blank text file with your current account, saving it, then deleting it. If this fails, your account can't complete that operation in that location. If it succeeds, it only confirms that you can write that file; an existing database could still be read-only, locked by another process, or subject to separate access restrictions. Don't change permissions across system folders just to launch the app.

  1. Exit and back up

    Exit from the notification area's right-click menu, then confirm the old process has ended in Task Manager. Back up the old extracted folder and any separately configured data location. Don't copy just one database file while the client is still running. Keep subscription links and node credentials in your local backup.

  2. Extract to a new folder

    Extract the complete package for the same build. For example, enter %LOCALAPPDATA% in File Explorer's address bar, then create a v2rayN-test folder there. Don't run the app by double-clicking it inside the archive, or extract the new package over the old folder.

  3. Test a clean launch

    Don't copy any old data. Run v2rayN.exe from the new folder and test with a standard user account. If the current build reads user data from a shared location, changing the program folder doesn't make this a clean launch. Check the actual data path in the logs, back it up, then temporarily move the data aside.

  4. Restore data in batches

    Once the clean launch works, reimport the original subscription URL first, then restore custom settings. Exit and reopen the app after each batch. If the issue returns after a particular batch, narrow the investigation to that data. Don't copy the old version's config, database, and core into the new folder all at once.

Android app crashes vs. VPN service stops

v2rayNG uses the Xray core, while v2flyNG uses the v2fly core. Neither Android client depends on the Windows .NET Desktop Runtime. Note whether the issue occurs when tapping the app icon, importing a config, or tapping Connect. That will help you decide whether to investigate app startup or VPN authorization.

v2rayN startup crash FAQ

Why does v2rayN still say the runtime is missing after I installed .NET?

Check the framework name, version, and architecture required by the error dialog. Make sure you haven't installed only the standard runtime, or an x86 desktop runtime when launching an x64 build. After installing the right runtime, launch the app directly from its extracted folder to avoid confusion from an old shortcut.

It only opens when I run it as administrator. Do I need to keep doing that?

Test the same build with a standard account in a folder you can write to. If it launches, prioritize moving the data folder or fixing permissions on the specific path. Launching the regular interface and granting the system permissions required for TUN are separate issues; don't use permanent elevation to work around everyday write-access problems.

What should I include when reporting a crash that also happens on a clean launch?

Include your OS version, package filename, app architecture, reproduction time, and the first relevant exception. Note whether you tested the same build in a new folder. Before sharing logs, redact subscription URLs, access tokens, node credentials, and local paths containing your username. Don't upload the entire config folder.

Download and install clients