How to Check .NET Framework Version on Windows 10: A Step-by-Step Guide

Windows 10 can have several .NET technologies present, so first distinguish the classic .NET Framework from modern .NET releases. If an application specifically asks for .NET Framework 4.x, Microsoft’s documented Registry release value is a reliable way to identify the installed 4.x version.

Check .NET Framework 4.x with PowerShell

  1. Open PowerShell.
  2. Run Get-ItemPropertyValue ‘HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full’ -Name Release.
  3. Note the numeric Release value.
  4. Compare it with Microsoft’s current .NET Framework version table.

The Release number maps to a .NET Framework 4.x version. Do not guess the version from the number; use Microsoft’s mapping because multiple Windows releases can report different minimum values.

Older .NET Framework versions are listed separately

Legacy 2.0–3.5 components use different Registry keys and Windows Features. If old software specifically requires .NET Framework 3.5, open Turn Windows features on or off and check whether the .NET Framework 3.5 feature is enabled.

Modern .NET uses a different command

If the application asks for .NET 6, .NET 8, or another modern .NET release, the .NET Framework Registry key is the wrong place to look. When the .NET command-line host is installed, dotnet –list-runtimes and dotnet –list-sdks show installed modern runtimes and SDKs.

Do not install every .NET version “just in case”

Follow the application’s documented prerequisite. Windows components and applications can depend on specific runtime families, and installing unrelated developer SDKs does not fix a program that needs a particular Framework feature.

Check Windows Features when software reports a missing component

If a legacy application reports that .NET Framework 3.5 is missing, do not assume the newest .NET runtime replaces it. Windows can maintain different runtime families side by side. Use Windows Features or the application’s documented installer path, and obtain offline packages only from Microsoft when they are genuinely required.

Windows 10 support note

Windows 10 reached its standard free-support endpoint on October 14, 2025, which matters when maintaining the system described here. Runtime support also has its own lifecycle. For a secure development or application environment, verify both the operating system and the required .NET product remain supported.

Get Our Free Newsletter

How-to guides and tech deals

You may opt out at any time.
Read our Privacy Policy