v2rayN Crashes on Startup? Fix Missing .NET Desktop Runtime and Folder Permission Issues

Fix v2rayN when it won't open or closes on startup. Check .NET Desktop Runtime versions, folder permissions, antivirus blocks, and corrupted settings; includes v2rayNG troubleshooting.

At a glance

For cases where v2rayN opens to no window on Windows, exits immediately after an update, or launches normally but errors when starting the core. First determine whether the desktop app or the core is exiting, then narrow down the cause with runtime checks, Event Viewer, and a clean folder. Back up your settings before attempting recovery.

First, identify whether v2rayN or the core is closing

No window after double-clicking doesn't always mean the app crashed. Check 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 the tray menu opens the main window, check whether the app is set to start minimized before reinstalling any runtimes.

Tray statusProcess statusEvent logClean folderRestore settings

Install the .NET Desktop Runtime required by the error

For WPF packages that rely on a separately installed runtime, the startup prompt's Framework, Version, and Architecture are more useful than the Windows version. If it requires Microsoft.WindowsDesktop.App 8.0.0 with x64 architecture, install the latest patch of Microsoft's .NET 8 Desktop Runtime for x64. Seeing only Microsoft.NETCore.App doesn't mean the desktop framework is installed. A newer major version also isn't guaranteed to satisfy an older app's requirement.

where.exe dotnet
dotnet --list-runtimes

Run these two lines in Command Prompt. The first shows the host paths that can be found; the second lists the runtimes visible to the current host. After installation, check for Microsoft.WindowsDesktop.App with the required major version, then restart the client. If runtimes for multiple architectures are installed, this output doesn't show the status of other architectures; match the architecture specified in the error. If the package is explicitly marked as self-contained, first check that it was fully extracted instead of assuming every startup failure is a runtime issue.

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

Cause and fix: The startup host couldn't find a compatible framework. Expand the prompt and install the runtime matching its framework name, version, and app architecture. For Microsoft.WindowsDesktop.App, choose the Desktop Runtime.

Error: Access to the path is denied.

Cause and fix: The app was denied access to a path. Check the exception details to identify whether it's the app folder, a settings file, or another location, then review your account permissions and security software logs. Don't change permissions across an entire drive based on this message alone.

Check the extracted folder, permissions, and security blocks

Launching the app directly from an archive preview or extracting only the executable can leave out required files. Upgrading by extracting over an old folder can also mix files from different versions. Test the complete package in a new, empty folder first to distinguish package, folder, and old-settings issues.

  1. Close the old process

    Right-click the tray icon and select Exit, then confirm in Task Manager that the existing instance has closed. If it's still running, the new launch may hand the request to the old instance, making the test results unclear.

  2. Extract all files

    In File Explorer, right-click the archive, select Extract All, and extract it to a new folder under your user account, such as %LOCALAPPDATA%\v2rayN-test. Don't merge it with the old folder or test write access under Program Files.

  3. Check that the folder is writable

    Using a standard account, create and delete an empty text file in the new folder. If that fails, right-click the folder, open Properties → Security, and check whether your account has write permission. For organization-managed devices, ask your administrator to check the policy.

  4. Check protection history

    Open Windows Security → Virus & threat protection → Protection history, then compare events with the launch time and file path. If Controlled folder access blocked a write, try running the app from a user folder where writing is allowed. If a file was quarantined after a threat detection, verify its source and the reason for detection; don't restore it or disable protection without checking.

  5. Start with a clean configuration

    Launch the app from the new folder with standard permissions. Don't import subscriptions or enable TUN yet. If the window opens, test closing and reopening the app before moving your data.

Crashes after an update: isolate old settings and restore them in batches

If a clean folder works but the old folder with the same version doesn't, check for leftover files, permission issues, and old settings. Overwriting settings immediately makes it harder to compare. Before migrating, note both the old and new versions so you can pair the original version with its original data if you need to roll back.

Common questions and v2rayNG crashes

Why does it still say a runtime is missing when .NET 8 is installed?

Check whether the message specifically names Microsoft.WindowsDesktop.App, then check the app architecture. If the error requires x64 but only the x86 runtime is installed, add the matching Desktop Runtime for x64. If the prompt requires a different major version, follow that requirement.

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

First move it to a folder your standard account can write to and try again, then compare the path in the event details. Whether the main window needs to write to a particular folder and whether TUN requires elevated permissions are separate issues. Once it starts with standard permissions, address permissions based on the features you actually need.

Does v2rayNG on Android also need a runtime if it closes as soon as I open it?

No Windows .NET Desktop Runtime is needed. On Android, go to Settings → Apps → v2rayNG, open App info, tap Force stop, then reopen the app. If it still crashes after an update, check that the package matches your device architecture and Android version. If the app opens, back up your subscriptions before considering clearing data. Clearing storage deletes local settings and shouldn't be your first step.

v2rayNG opens normally, but fails when I tap Connect. How can I tell what's wrong?

First check whether you've approved the VPN connection request on Android, then check the system's VPN settings for another active connection or an Always-on VPN. If the app is still open, review its connection log. If it points to a configuration parsing issue, test against a known-working configuration instead of clearing all subscriptions.

Download the client