The quickest way to find your .NET Framework version
The fastest method depends on which version you're looking for. If you need to know what's installed right now, 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. Each folder here represents an installed version — look for folders named v2.0.50727, v3.5, v4.0.30319, and so on. The version number in the folder name tells you what's there.
If you prefer not to use the Registry Editor, you can also check through Control Panel. Go to Control Panel > Programs > Programs and Features, then look for entries that say ".NET Framework" followed by a version number. This shows what's installed, though it doesn't always display every version clearly.
For .NET Framework 4.5 and later, there's a third option: check the Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full and look for a value called Release. The number there maps to a specific version — for example, 394802 means .NET Framework 4.8.1, while 528049 means .NET Framework 4.8.2.
Key Takeaways
- The Registry Editor method (regedit) shows all installed versions in one place by displaying folders under the NDP path.
- For .NET Framework 4.5 and later, the Release value in the Registry maps to a specific version number that you can cross-reference.
- Control Panel's Programs and Features list shows installed versions but may not display every variant clearly.
- Different applications may require different .NET Framework versions, so knowing what's installed helps you troubleshoot compatibility problems.
Understanding .NET Framework version numbering
.NET Framework versions follow a pattern that can look confusing at first. Versions 2.0, 3.0, and 3.5 are separate releases. Then version 4.0 arrived, followed by 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, 4.8.1, and 4.8.2. Each one is a distinct release, and some applications need a specific version to run.
The folder names in the Registry use internal version numbers that don't always match the public version name. For instance, .NET Framework 4.5 shows as v4.0.30319 in the folder structure because Microsoft kept the internal version number the same for the 4.x line. This is why checking the Release value is more reliable for the 4.5+ versions — it gives you the actual version number rather than the internal code.
Using the Registry Editor to see all versions at once
The Registry method works on every Windows machine and shows you everything installed in one view. Press Windows key + R, type regedit, and click OK. If Windows asks for permission, click Yes. The Registry Editor window opens.
In the left panel, navigate through the folders: HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > NET Framework Setup > NDP. Each folder you see here represents an installed version. A folder named v2.0.50727 means .NET Framework 2.0 is installed. Folders named v3.5 or v4.0.30319 show those versions are present. If a folder isn't there, that version isn't installed.
For versions 4.5 and later, don't stop at the folder name. Click on the v4.0.30319 folder, then click on the Full subfolder inside it. In the right panel, look for the Release entry. The number next to it tells you the exact version: 394802 is 4.8.1, 528049 is 4.8.2, 533325 is 4.8.2 on Windows 11, and so on.
Checking from the command line
If you prefer typing commands, you can find .NET Framework versions without opening the Registry Editor. Open Command Prompt by pressing Windows key + R, typing cmd, and pressing Enter.
Type this command and press Enter: reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP" /s. The output shows all installed versions. Look for lines that say Install REG_DWORD 0x1 — that means the version listed above it is installed. If you see 0x0, that version is not installed.
For a cleaner view of just the 4.5+ versions, type: reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release. This shows only the Release value, which you can then match to the version number you need.
Matching Release numbers to actual versions
If you found a Release value in the Registry, use this list to find out what version it represents. These numbers are specific to Windows and don't change:
| Release Value | .NET Framework Version |
|---|---|
| 378389 | 4.5 |
| 378675 | 4.5.1 (Windows 8.1) |
| 379893 | 4.5.2 |
| 393295 | 4.6 |
| 393297 | 4.6 (Windows 10) |
| 394254 | 4.6.1 |
| 394802 | 4.8.1 |
| 528049 | 4.8.2 |
| 533325 | 4.8.2 (Windows 11) |
If your Release value doesn't match any of these exactly, it may be a version between major releases or a Windows-specific variant. Search for the exact number online along with ".NET Framework" to find what it represents.
Why you might need to know your .NET Framework version
Applications built with .NET Framework often require a specific version or a minimum version to run. If a program won't start and you see an error message mentioning .NET Framework, checking your installed version helps you understand whether you need to install something else or if there's a different problem.
Some older software needs .NET Framework 2.0 or 3.5, while newer applications require 4.6 or 4.8. If you're missing the version an application needs, you can download and install it from Microsoft's website. Knowing what you already have prevents you from installing versions you don't need and helps you troubleshoot compatibility issues faster.
Frequently Asked Questions
Can I have multiple versions of .NET Framework installed at the same time?
Yes. Versions 2.0, 3.0, and 3.5 can coexist, and versions 4.5 and later can also coexist with each other and with the earlier versions. This is by design — different applications may need different versions, so Windows allows them all to be present.
What's the difference between .NET Framework and .NET Core?
.NET Framework is the older system and runs on Windows only. .NET Core (now called just ".NET") is newer and runs on Windows, Mac, and Linux. They're separate products with different version numbers. This guide covers .NET Framework only — if you're looking for .NET Core or .NET 5+, the version check process is different.
Do I need to uninstall old versions of .NET Framework?
No. Older versions don't hurt anything by sitting there, and removing them can break applications that depend on them. Leave them installed unless you're trying to free up disk space, which is rarely necessary.
Why does the Registry show v4.0.30319 for both 4.5 and 4.8?
Microsoft kept the internal version number the same for the entire 4.x line to maintain compatibility. That's why you must check the Release value to tell 4.5 apart from 4.8 — the folder name alone isn't enough for versions 4.5 and later.