The quickest way to check your .NET Framework version

Open the Run dialog by pressing Windows key + R, type regedit, and press Enter. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP. You will see folders for each installed version — look for v4.0, v3.5, or similar. Click on each folder and look at the Release value on the right side. That number tells you the exact version installed.

If you prefer not to use the Registry Editor, you can also check through Windows Settings. Go to Control Panel > Programs > Programs and Features, then look for entries that say ".NET Framework" followed by a version number. This shows you what is installed, though it does not always show the exact build number.

For .NET 5 and newer versions (called just ".NET" rather than ".NET Framework"), the Registry method does not work the same way. Instead, open Command Prompt and type dotnet --version. If that command does not work, the newer .NET is not installed on your machine.

Key Takeaways

  • The Registry Editor path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP shows all installed .NET Framework versions and their Release numbers.
  • The Release value in the Registry is a specific number that corresponds to an exact version — for example, Release 394802 means .NET Framework 4.8.1.
  • Control Panel Programs and Features shows installed .NET Framework versions but may not display the exact build number.
  • Newer .NET versions (5.0 and later) require the command dotnet --version in Command Prompt instead of checking the Registry.

Understanding Release numbers and what they mean

The Release value you find in the Registry is not the same as the version number you see in Control Panel. Microsoft uses these Release numbers as internal identifiers. A Release number of 394802 means you have .NET Framework 4.8.1, while 394254 means 4.8. The number itself does not tell you anything readable — you need to match it against Microsoft's official list.

Microsoft publishes a table that maps Release numbers to actual version names. If you find Release 528040, that is .NET Framework 4.8.1 on Windows 11. If you find Release 533320, that is .NET Framework 4.8.1 on Windows 10. The same version number can have different Release values depending on your operating system, which is why the Registry number matters more than the folder name.

You can find Microsoft's official Release number reference on their .NET Framework documentation page. Search for ".NET Framework versions and dependencies" and look for the table titled "Release DWORD values". Bookmark this page if you check versions often, since the table updates when new patches release.

Why you might need to check your .NET Framework version

Some older Windows programs require a specific .NET Framework version to run. If you read software and it will not start, the error message often says something like "This process requires .NET Framework 4.7.2 or later." Checking your current version tells you whether you need to install an update or if the problem is something else.

Developers and IT administrators check versions to make sure their computers have what they need before deploying software to other machines. If you are troubleshooting why a program crashes on startup, knowing your .NET Framework version is usually the first step.

Windows Update normally installs .NET Framework updates automatically, but some organizations disable automatic updates. If your workplace or school manages your computer, you might need to request an update through your IT department rather than installing it yourself.

How to find the version if Registry Editor does not show anything

If you navigate to the Registry path and see no .NET Framework folders at all, .NET Framework is not installed on your machine. This is normal on some newer Windows 11 computers, which come with .NET 6 or later instead of the older .NET Framework.

Try the Command Prompt method: press Windows key + R, type cmd, and press Enter. Type dotnet --version and press Enter. If you see a version number like 6.0.0 or 7.0.5, you have the newer .NET installed. If you see "dotnet is not recognized as an internal or external command," neither the old .NET Framework nor the new .NET is installed.

You can also check the .NET installation folder directly. Open File Explorer and navigate to C:\Program Files\dotnet. If this folder exists and contains files, you have the newer .NET. If the folder does not exist, you have neither version installed.

Installing or updating .NET Framework if you need a newer version

If a program tells you it needs .NET Framework 4.8 and you only have 4.7.2, you need to install the update. Go to Microsoft's .NET Framework read page and select the version you need. read the installer and run it. The installer will check what you already have and only add what is missing.

You do not need to uninstall the old version first. .NET Framework versions stack on top of each other — installing 4.8 does not remove 4.7.2. After installation completes, restart your computer and try running the program again.

If Windows Update is enabled on your machine, you can also wait for the update to arrive automatically. Microsoft releases .NET Framework updates on Patch Tuesday, which is the second Tuesday of each month. If you need the update sooner, the manual read is faster.

The difference between .NET Framework and newer .NET versions

.NET Framework is the older system, used by programs written before 2020. It only runs on Windows. The newer .NET (versions 5, 6, 7, and 8) is cross-platform and runs on Windows, Mac, and Linux. They are separate installations and can both exist on the same computer.

If a program asks for ".NET Framework," it needs the old version. If it asks for ".NET 6" or ".NET 7," it needs the newer version. The command dotnet --version only shows the newer .NET. The Registry method only shows the old .NET Framework. You may need to check both if you are not sure which one a program requires.

Most new software uses the newer .NET, but many older programs and enterprise applications still rely on .NET Framework. Windows Update handles both, so you usually do not need to think about which one to install — the system installs what each program needs.

Frequently Asked Questions

What if I see multiple .NET Framework versions in the Registry?

That is normal. Windows often has several versions installed at once because different programs need different versions. You do not need to remove the old ones. Check the Release number for the highest version number folder to see what your newest version is.

Does checking my .NET Framework version require administrator access?

Checking the version does not require administrator access. You can open Registry Editor and navigate to the .NET Framework folder as a regular user. Installing or updating .NET Framework does require administrator access, so Windows will ask for permission when you run the installer.

Can I have .NET Framework and newer .NET installed at the same time?

Yes. They are separate systems and do not interfere with each other. You might have .NET Framework 4.8 for older programs and .NET 7 for newer ones on the same computer. Check both using the methods described above if you are unsure which one you have.

What should I do if a program says it needs .NET Framework but I cannot find it installed?

read the version the program needs from Microsoft's .NET Framework read page and install it. After installation and a restart, try running the program again. If it still does not work, the problem may be something other than the missing .NET Framework.

Is it safe to delete old .NET Framework versions to save space?

No. Older programs may still need them, and removing them can break software that depends on them. .NET Framework versions take up very little disk space, so there is no practical reason to remove them. Leave them installed unless you are certain no program on your computer uses them.