v2rayN Crashes on Startup: Fix .NET Runtime, Permissions, and Configuration Issues

Troubleshoot v2rayN crashes by checking the .NET Desktop Runtime, extraction path and folder permissions, security software, and config files. Includes Android fixes.

At a glance

If v2rayN disappears as soon as you double-click it, first check whether the process actually exited. Then review any startup message or the Windows event log for runtime details. If there’s no clear error, launch a fresh copy of the same version from a writable folder under your account—without importing subscriptions or copying old settings. This helps separate app issues from problems with the old folder or configuration while preserving your original data for rollback. On Android, an app that returns to the home screen is a different issue from a VPN connection that drops; troubleshoot them separately.

Check whether the process exited, then review startup logs

No window after a double-click doesn’t necessarily mean the app crashed. First expand the hidden icons in the taskbar’s notification area, then press Ctrl + Shift + Esc to open Task Manager and look for v2rayN.exe under Details. If the process is still running and its tray icon opens the main window, the window was hidden—you don’t need to reinstall the runtime. If the main window works but an error appears only when you select a node or start the core, check the core logs instead of treating it as a desktop app crash.

After confirming the process has exited, note the time you double-clicked it. Press Win + R, enter eventvwr.msc, then open Windows Logs → Application. Use Filter Current Log on the right to narrow the results, then find entries for v2rayN.exe around that time. Don’t rely only on the most recent error in the list: other apps may have logged errors in the same minute.

1000
Common Application Error event IDs
1026
Common .NET Runtime event IDs
8.0
Example runtime major version—follow the prompt

Event 1000 can help identify the faulting application and module. If event 1026 appears at the same time, check the exception type, affected path, and exception details as well. A faulting module name alone isn’t enough to identify the cause. No matching event doesn’t mean nothing went wrong: if Windows displayed a runtime prompt, follow the framework name, version, and architecture shown there first.

Install the .NET Desktop Runtime specified in the startup prompt

Install the runtime required by the app—not simply the newest one available. For example, if the prompt specifies Microsoft.WindowsDesktop.App, 8.0.0, and x64, install Microsoft .NET 8.0 Desktop Runtime (x64), choosing the latest servicing release available in that series. The regular .NET Runtime does not include the Desktop Runtime framework, and another major version is not a direct substitute. If the prompt specifies arm64, choose the architecture required by the app package rather than relying on whether Windows is 64-bit.

Run dotnet --list-runtimes in a terminal to check whether the required framework and version appear in the output. If the command isn’t recognized, first check the installation records under Settings → Apps → Installed apps; a failed command alone doesn’t prove the runtime is missing. The dotnet command may also use a different architecture from the app. If the package is explicitly labeled self-contained, it usually includes its own runtime, so first check that all files were extracted and that you downloaded the right package architecture.

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

Cause: The app couldn’t find a framework that meets its requirements. Fix: Install the runtime that matches the framework, version, and architecture in the prompt, then try again from the same folder.

Error: System.UnauthorizedAccessException

Cause: If the exception points to a configuration or log path the app was trying to write to, the process may not have permission to write there. Fix: Extract a fresh copy of the same version to a local folder your account can write to, then launch it without elevated permissions.

Error: System.Text.Json.JsonException

Cause: A JSON file the app reads may be truncated, malformed, or contain a field type the current version doesn’t expect. Fix: Use the log to identify the file, back up the relevant data, then test with an empty configuration. Don’t overwrite the original file.

Check the extraction path, write permissions, and security history

Extract the entire portable archive. Pulling out only the main executable or launching it from the archive preview can leave it unable to find files in the same folder. A fresh folder helps isolate variables such as permissions, sync services, and leftover files. A shorter path is simply easier to check; a path containing non-Latin characters doesn’t necessarily cause crashes.

  1. Keep the old folder intact

    If the tray icon is still there, exit from its menu first, then make sure v2rayN.exe is no longer running in Task Manager. Note the old version and package type, and leave the old folder untouched. When testing the same version, don’t extract it over the old folder.

  2. Extract the entire archive

    Open %LOCALAPPDATA% in File Explorer and create a v2rayN-test folder. For a ZIP package, right-click it, select Extract All, and extract its contents into the new folder, preserving the folder structure. Don’t use Program Files, a network drive, or a folder currently being synced for this test.

  3. Check write access

    Create a blank text file in the folder containing the main executable, then delete it. If you get an access denied message, try a local folder you can write to. This only checks your account’s basic write access; it doesn’t rule out security software blocking the app itself.

  4. Check security history

    Open Windows Security → Virus & threat protection → Protection history and compare the time, file name, and path of any blocks. If there’s a matching entry, keep the alert details and verify the package source. Don’t turn off protection or add the entire folder to exclusions. Ask your administrator to review policy alerts on a managed device.

  5. Try launching without elevated permissions

    Double-click the main executable in the new folder. Don’t use an old shortcut or import data. If the window opens, close and relaunch the app to check that it can save and reload its settings. If it still exits, capture the new log and compare it with the error from the old folder.

Back up settings and isolate upgrade-related issues

If a fresh folder starts on the same version and under the same account but the old one doesn’t, focus on the old folder’s permissions, leftover files, or user data. That result alone doesn’t prove the configuration is corrupt. For a portable version, close the app and back up the entire old folder, especially guiConfigs if it exists. If the version stores data elsewhere, use the logs or release notes to find and back up that location too.

  • Logs point to a specific settings file: For example, if the log identifies guiConfigs\guiNConfig.json, back up the file, close the app, and rename it to guiNConfig.json.bak. Then relaunch and check whether default settings are created. If no new file appears, the error persists, or the log points to another file, close the app and preserve the current state—don’t delete more files in bulk.
  • The app opens with an empty configuration: In the fresh copy, re-enter your subscription or import a known-good client export file, then restart to test it. Restore nodes, subscriptions, and routing settings in batches. If the issue returns after restoring a batch, test only that batch next time instead of copying the entire folder back.
  • Crashes started after an upgrade: If you still have the pre-upgrade app and data, test copies of both in a separate folder. Don’t let the old app read the only copy of data already migrated by the newer version; even if the old app starts, that won’t give you a reliable compatibility test.

Tell an Android app crash from a dropped VPN connection

v2rayNG and v2flyNG don’t use the Windows .NET Desktop Runtime. If tapping the app icon takes you back to the home screen, first check the app installation and data. If the main screen stays open but something goes wrong when you tap Connect or turn off the screen, determine whether the app exited or the VPN session ended.

v2rayNG closes as soon as I open it. Should I clear its data?

Don’t clear data as a first step. Long-press the app icon, open App info, tap Force stop, then go to Storage & cache and tap Clear cache. Return to the home screen and reopen the app. Some Android versions call this menu Storage usage. Don’t tap Clear storage or Clear data: that resets local app data, and any unbacked-up nodes or subscriptions may be lost.

Does a disconnect right after tapping Connect mean the app crashed?

First check whether the app is still open. If Android’s VPN connection request wasn’t approved, tap Connect again and check for the system prompt. If another VPN is already active, search for VPN in Settings and check which connection is in use. If the app returns to the home screen after approval, note whether it happens with every node or only one. Don’t change battery settings yet.

The VPN works with the screen on but drops after the phone is locked. What should I check?

First check that the main screen still opens normally after you unlock the phone. If only the VPN session drops, go to App info → App battery usage and look for an option such as Unrestricted or Allow background usage. Then lock the screen and test again with the same node. Menu names vary by device maker. This addresses background disconnections, not an app that closes when you tap its icon.

The app won’t open after an update. Can I just reinstall it?

First note the app version in App info, then check the Android version and processor architecture required by the package. If Android allows an update from the same source with a matching signature, try updating without removing the app’s data. If you’re asked to uninstall, make sure you have the original subscription URL or a usable backup first. If the app won’t open, don’t assume your local nodes will survive an uninstall.

View downloads