Check your .NET Framework version in Command Prompt with one line

Open Command Prompt and run reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP" to see all .NET Framework versions installed on your computer. This command reads your Windows registry — the database where Windows stores system information — and displays every version present. The output shows version numbers like 4.8, 4.7.2, or 3.5, each with a Release value that confirms the exact build.

If you need only the .NET Framework 4.x versions (the most common modern ones), use reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" instead. This narrows the results to just the latest generation and is faster if you do not care about older versions.

Both commands work on Windows 7 through Windows 11 and do not require administrator rights, though running Command Prompt as administrator can prevent permission errors on locked systems.

Key Takeaways

  • The registry query command reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP" shows all .NET Framework versions your computer has installed.
  • Look for the Release value in the output — this number confirms the exact build and patch level of each version.
  • If you only need .NET Framework 4.x information, use the shorter path ending in \v4\Full to skip older versions.
  • You do not need administrator rights to run these commands, but opening Command Prompt as administrator prevents access errors on some systems.
  • The registry method works on all Windows versions from Windows 7 onward and shows information that the graphical Control Panel sometimes misses.

Step-by-step: Running the registry query command

Press Windows key + R to open the Run dialog. Type cmd and press Enter. Command Prompt opens as a black window with a blinking cursor.

At the cursor, type or paste this command exactly: reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP" and press Enter. Windows reads the registry and displays the results on screen. Each .NET Framework version appears as a separate entry with indented information below it.

Scroll up in the Command Prompt window if the output is longer than one screen. Look for entries labeled with version numbers like v3.5, v4.0.30319, or v4.8. Under each one, you will see a Release value — a number like 394802 or 533320 that identifies the exact patch level.

Understanding the Release value and what it means

The Release value is a number that pinpoints which exact build of .NET Framework you have. Different Release values mean different patch updates, even within the same version number. For example, .NET Framework 4.8 has Release values ranging from 528040 to 533320 depending on which Windows update you installed.

Microsoft publishes a reference table that maps Release values to version names. If you see Release 533320 under v4.8, that means you have .NET Framework 4.8.1 with the latest updates. Release 528040 under the same version means you have an older .NET Framework 4.8 build that needs Windows updates.

You do not usually need to memorize these numbers. Most software only cares whether you have version 4.5 or later, not the exact Release value. But if a program says it needs a specific .NET Framework version and you want to confirm you have it, the Release value is the definitive answer.

What to do if the command returns nothing or an error

If Command Prompt says "The system was unable to find the specified registry key", your computer may not have any .NET Framework versions installed at all. This is rare on Windows 10 and 11, which include .NET Framework 3.5 and 4.x by default, but can happen on fresh Windows 7 installations or heavily stripped systems.

If you get an "Access Denied" error, close Command Prompt and open it again by right-clicking on cmd.exe and selecting "Run as administrator". This gives the command permission to read the registry. On work computers with restricted accounts, you may not have permission even as administrator — in that case, contact your IT department.

If the command runs but shows no v4 entries, try the older version path: reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5". This checks for .NET Framework 3.5, which some older programs still need. If that also returns nothing, .NET Framework is not installed and you will need to download it from Microsoft.

Alternative: Using PowerShell for a cleaner display

If you prefer a simpler output, PowerShell can show the same information in a more readable format. Press Windows key + X and select "Windows PowerShell (Admin)" or "Terminal (Admin)" depending on your Windows version. Type this command: Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' | Select-Object PSChildName and press Enter.

PowerShell lists each installed version on its own line without the extra registry details. This method is faster if you only need to know which versions are present, not the Release values. Both Command Prompt and PowerShell read the same registry data, so the versions they report are identical.

PowerShell requires administrator rights on most systems, while Command Prompt can often run without them. If you are on a restricted work computer, Command Prompt may be your only option.

Why you might need to know your .NET Framework version

Software installers sometimes check your .NET Framework version before letting you install. If the program says you need .NET Framework 4.7.2 or later and you are not sure what you have, the registry query tells you instantly. You can then decide whether to download a newer version or find a different program that works with what you have.

Some programs crash or behave strangely because they expect a specific .NET Framework version. Knowing what you have installed helps you troubleshoot. If you have version 4.5 but the program needs 4.8, updating .NET Framework may fix the problem.

Network administrators and IT support staff often ask for your .NET Framework version when you report a technical issue. Having the exact Release value from the registry query gives them precise information instead of a guess.

Frequently Asked Questions

Can I have multiple .NET Framework versions installed at the same time?

Yes. .NET Framework versions can coexist on the same computer. Version 3.5 and version 4.x can both be present, and different 4.x versions (like 4.7.2 and 4.8) can run side by side. The registry query shows all of them, so you can see the complete picture of what is installed.

What is the difference between .NET Framework and .NET Core?

.NET Framework is the older system that runs on Windows only. .NET Core (now called just ".NET") is the newer cross-platform version that runs on Windows, Mac, and Linux. The registry query only shows .NET Framework. If you need to check .NET Core, use the command dotnet --version in Command Prompt instead.

Do I need to restart my computer after checking my .NET Framework version?

No. The registry query only reads information — it does not change anything on your system. You can run it as many times as you want without any effect on your computer.

Is it safe to run the registry query command?

Yes. The reg query command only reads the registry. It does not modify, delete, or change anything. You cannot break your system by running this command. It is one of the safest ways to check system information.

What if I need to update my .NET Framework version?

Once you know which version you have, visit the Microsoft .NET Framework download page and select the version you need. Windows Update can also install .NET Framework updates automatically. After installing, run the registry query again to confirm the new version appears in the list.