|

Fix “You Must Install .NET To Run This Application” (2026)

Windows shows “You must install .NET to run this application” when a program needs a .NET runtime that your PC does not have.

A close cousin, “You must install or update .NET to run this application,” means .NET is present but the version, or the 32-bit or 64-bit build, is wrong.

The fix comes from Microsoft’s own app-launch troubleshooting page: read the message, install the matching runtime, and check where Windows is looking for it.

Quick answer: what the message tells you to do

What the message saysWhat it meansWhat to do
You must install .NET to run this application, with “.NET location: Not found”No .NET runtime was found for this appInstall the runtime that matches the Architecture and Host version shown
You must install or update .NET to run this application, with a Framework line.NET exists, but not the framework version or build the app asked forInstall the runtime that contains the named framework
Runtime is installed but the app still failsWindows may be looking in the wrong place, or the architecture does not matchCheck the DOTNET_ROOT variable and install the matching architecture

Read the message before you download anything

The error window is the instruction sheet. Microsoft says to note the Host version and the Architecture it shows.

Here is the layout of the first message, as Microsoft documents it for Windows.

You must install .NET to run this application. App: C:\repos\myapp\myapp.exe Architecture: x64 Host version: 7.0.0 .NET location: Not found

The App line names the program that failed, the Architecture line says whether it needs the x64 or another build, and the Host version tells you which .NET release to look for.

Install the missing .NET runtime

Microsoft’s steps for the “must install .NET” message are short.

  1. Write down the Host version and Architecture from the error window.
  2. Open the .NET downloads page, or use the download link inside the error message, and select the matching version.
  3. Under .NET Runtime, choose the download that matches the architecture and run the Installer.
  4. Start the app again.

Microsoft also describes a Binaries download, which you extract into the “.NET location” shown in the error, but the installer is the simpler route for most people.

If the message says “install or update” and names a framework

In this version of the error, the message gives the required framework name, its version and architecture, then lists the frameworks Windows did find.

Microsoft’s example asks for Microsoft.NETCore.App version 5.0.15 while only 6.0.2 is installed.

The answer is to install a runtime download that contains the missing framework, and the table below shows which download holds which framework.

Runtime downloadFrameworks it includes
.NET RuntimeMicrosoft.NETCore.App
.NET Desktop RuntimeMicrosoft.NETCore.App and Microsoft.WindowsDesktop.App
ASP.NET Core RuntimeMicrosoft.NETCore.App and Microsoft.AspNetCore.App

For a normal Windows desktop program, the framework named in the error tells you which row you need.

Match the architecture: x64, x86 or ARM64

The runtime must be built for the same architecture as the app. The error reports the app’s architecture, for example x64.

Installers are listed per architecture on the download page, so pick the one that equals the Architecture line.

A 32-bit app on a 64-bit PC needs the x86 runtime, and Microsoft’s page points those apps to the DOTNET_ROOT_X86 variable.

Installing the x64 runtime does not satisfy an x86 app, so you may need both on one PC.

Check the DOTNET_ROOT environment variable

If the variable is set, .NET skips the default install location, so a wrong value breaks the launch even when .NET is installed.

Microsoft lists three common problems: the variable points to an old install, it is set when it should not be, or it does not match the architecture of the app.

  1. Open Windows Terminal or PowerShell.
  2. Run echo $env:DOTNET_ROOT.
  3. If a path prints, confirm that the folder exists and holds the .NET version you need.
  4. If nothing prints, .NET uses the default install location and this is not your problem.

The common location in Microsoft’s article for Windows is %ProgramFiles%\dotnet.

Where Windows looks for .NET

When an app starts through its own launcher file, Microsoft says .NET checks three places in order and uses the first one that holds an installation.

OrderLocation checked
1Folders under DOTNET_ROOT, if the variable is set
2The global install location stored in the registry under HKLM\SOFTWARE\dotnet\Setup\InstalledVersions
3The default folder, %ProgramFiles%\dotnet (or %ProgramFiles(x86)%\dotnet for 32-bit apps on 64-bit Windows)

Only the first location with an installation is searched, so a runtime in a different folder is ignored unless DOTNET_ROOT points to it.

See which runtimes you already have

Microsoft’s launch article links to a separate page on detecting installed versions.

The standard command is dotnet --list-runtimes, run in a terminal window, which lists every installed runtime with its version and path.

Compare that list with the Host version or Framework line in your error to see what is missing.

The roll-forward option and its risk

By default, an app needs the same major version it was built for, but it can use a higher minor or patch version.

Microsoft says you can let an app run on a newer installed framework with the --roll-forward option or the DOTNET_ROLL_FORWARD environment variable.

The company warns that this runs the app on a version it was not designed for, which can cause unintended behavior.

For most home users, installing the exact runtime named in the error is the safer choice.

Private installs and the dotnet-install script

Microsoft describes a dotnet-install script for quick installs without administrator rights, mostly for build servers and temporary setups.

That kind of install does not behave like the standard installer, so an app must be pointed at it with DOTNET_ROOT or launched through the matching dotnet host.

If you only want a program to open, skip this and use the normal Installer from the downloads page.

If the error comes back after installing

  1. Compare the Architecture line again, because an x64 runtime does not help an x86 app.
  2. Check that the Host version or framework version in the error is installed in the list from dotnet --list-runtimes.
  3. Check DOTNET_ROOT, as shown above.
  4. Restart the PC and open the app again.
  5. Contact the app’s maker with the full text of the error window.

If a different startup error appears instead, our guide to error 0xC0000099 covers a separate cause of apps failing to open.

If a feature install fails with a Windows Update code, see our fix for error 0x800f081f.

Source

This guide follows Microsoft’s Troubleshoot app launch failures page for .NET.

The .NET downloads page is the official place to get the runtime installers.

Leave a Reply

Your email address will not be published. Required fields are marked *