Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Windows 10 / How to Check .Net Framework Version?

October 26, 2018 MiscWindows 10Windows Server 2016

How to Check .Net Framework Version?

On Windows, multiple versions of the .NET Framework can be installed and used simultaneously. When you install a new application developed on .Net on a computer / server, it is sometimes necessary to know in advance which versions and service packs of the .Net Framework are already installed. There are several ways to get a list of installed versions of the .NET Framework.

Contents:
  • List all the .NET Framework installed versions from the command line
  • How to check your .NET Framework version using registry?
  • Checking the .Net Framework version using PowerShell
  • .Net Version Detector utility
  • CLRver.exe tool

List all the .NET Framework installed versions from the command line

All versions of the .NET Framework are installed into the folders:

  • %SystemRoot%\Microsoft.NET\Framework
  • %SystemRoot%\Microsoft.NET\Framework64

Therefore, the easiest way to display the list of .Net installed versions is to open this folder. Each version corresponds to a separate directory with the v characters at the beginning and the version number as the folder name. Alternatively, you can list the .NET Framework directories (versions) from the command prompt like this:

dir %WINDIR%\Microsoft.Net\Framework\v* /O:-N /B

Determine Which .NET Framework Versions Are Installed - cmd

This command will list all installed versions except 4.5, since the .NET Framework 4.5 is installed in the v4.0.xxxxx subdirectory.

How to check your .NET Framework version using registry?

When you install or update any version of the .NET Framework, quite a lot of useful information is written to the system registry.

Run the registry editor (regedit.exe) and go to registry key HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP. This key contains a subkey for each version of .NET installed on the computer. The necessary information is contained in the key with the version number as key name (and for .Net 4.0 and higher in the subkeys Client and Full). We are interested in the following registry parameters:

  • Install — version installation flag (if equal to 1 – this version of .Net is installed on the computer);
  • Install Path — the directory where this .Net version is installed;
  • Release — .Net current release number;
  • Version — full version number of .Net Framework.

.Net version number and release in registry

In this example, you can see that the .NET Framework v2.0.50727, 3.0, 3.5 and 4.0 (release 461808) are installed on the computer.

Tip. For .NET 4.0 and above, if the subkey Full is missing, it means that this version of the Framework is not installed on the computer.

Using the following table, you can establish a correspondence between the release number and the version of the .NET Framework 4.5.

Release Value.NET Framework version
378389.NET Framework 4.5
378675NET Framework 4.5.1 on Windows 8.1 / Windows Server 2012 R2
378758.NET Framework 4.5.1 on Windows 8, Windows 7 SP1, Windows Vista SP2
379893.NET Framework 4.5.2
393273.NET Framework 4.6 on Windows 10
393297.NET Framework 4.6
394254.NET Framework 4.6.1 on Windows 10 November Update
394271.NET Framework 4.6.1
394802.NET Framework 4.6.2 on Windows 10 Anniversary Update
394806.NET Framework 4.6.2
460798.NET Framework 4.7 on Windows 10 Creators Update
460805.NET Framework 4.7
461308.NET Framework 4.7.1 on Windows 10 Fall Creators Update
461310.NET Framework 4.7.1
461808.NET Framework 4.7.2 on Windows 10 April 2018 Update
461814.NET Framework 4.7.2

Checking the .Net Framework version using PowerShell

You can get information about installed versions and releases of the Framework using PowerShell. This information can also be obtained from the registry. For example, to display information about the currently installed .NET 4.x release, use the Get-ItemProperty cmdlet (for more information about managing registry keys from PowerShell read the article):

(Get-ItemProperty ‘HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full’  -Name Release).Release

check .net using powershell

.Net Version Detector utility

There is a third-party freeware utility Asoft .Net Version Detector, which can help you to get a list of installed versions of the .NET Framework in a descriptive and convenient way. You can download this tool from the developer’s website (http://www.asoft.be/prod_netver.html). This tool is portable and doesn’t require installation. In a beautiful window, the utility will display all the .NET versions installed on the computer, as well as the maximum available version at this moment.

It’s quite convenient that you can go to the Microsoft download page for different versions of the .NET Framework right in the program, where you can download the last .NET package for your Windows build.

Asoft .Net Version Detector

CLRver.exe tool

Microsoft Visual Studio includes a separate utility – CLRver.exe, which generates a report of all installed versions of the CLR on the computer. Run the CLRver.exe from the command line and the list of installed dotNet versions on the computer will appear in the cmd console.

CLRver.exe tool

Finally, it’s important to mention that in server operating systems starting from Windows Server 2012, all basic versions of .Net (3.5 and 4.5) are part of the system and are installed as a separate feature (Installing .NET Framework 3.5 in Windows Server 2016/ 2012 R2), and minor ones (4.5.1, 4.5.2, etc.) are installed as separate updates via Windows Update or WSUS.

1 comment
0
Facebook Twitter Google + Pinterest
previous post
WinSxS Folder: Clean Up and Compress in Windows 10 and 8.1
next post
Huge Memory Usage in Non-Paged Pool in Windows

Related Reading

Integrating Windows Updates into Windows 10 Install Image

February 12, 2019

Copying Large Files over an Unreliable Network Using...

February 11, 2019

“The update is not applicable to your computer”:...

February 10, 2019

Fix: Clock Reverts to Wrong Time After Computer...

February 8, 2019

How to Disable Automatic Driver Updates in Windows...

February 6, 2019

1 comment

Martin Wiedmeyer March 21, 2016 - 4:56 pm

You are missing a colon in your posh command for the registry provider.
dir ′HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full′

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • ESXi: Slow Disk Performance on HPE Gen8

    February 15, 2019
  • Integrating Windows Updates into Windows 10 Install Image

    February 12, 2019
  • Copying Large Files over an Unreliable Network Using BITS and PowerShell

    February 11, 2019
  • Fix: Clock Reverts to Wrong Time After Computer (Server) Reboot

    February 8, 2019
  • Fix: BSOD Error 0x0000007B on Boot on Windows 7 and Server 2008 R2

    February 7, 2019
  • How to Disable Automatic Driver Updates in Windows 10?

    February 6, 2019
  • WSUS Windows Update Error 0x80244010: Exceeded max server round trips

    January 31, 2019
  • Configuring SSO (Single Sign-On) Authentication on Windows Server RDS

    January 29, 2019
  • Unable to Start or Connect to Virtual Disk Service in Disk Management

    January 28, 2019
  • How to Inject Drivers into a Windows 10 WIM/ISO Install Image?

    January 15, 2019
woshub.com

Follow us

  • Facebook
  • Twitter
  • RSS
Popular Posts
  • Adobe Flash Player: Application Initialization Error
  • Configuring Kerberos Authentication in Different Browsers
  • Configuring WordPress on Nginx: Full LEMP Guide
  • Fix ‘Access Denied’ Error in Adobe Reader 11
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top