Windows Desktop Runtime question

Tombar · Feb 5, 2024

I was trying to find out what this is and came across this article

What is Microsoft Windows Desktop Runtime?

In this guide, we have explained what is Microsoft Windows Desktop Runtime and how you can check the current version on your PC.

windowsreport.com

When i tried the methods given to check the version, the cmd and powershell ones didn't work - they don;t like s at the end
The registry one gave me Netsetup under Microsoft, not under Software as stated.
On checking the versions, I have two v 4 - see screenshot. The upper one is version 4.8.09032 and the lower one 4.0.00
Is this normal? If not, what do i do about it?

pseymour · Feb 5, 2024

That article is full of inaccurate things.

The NDP registry key that it refers to is for the .NET Framework. The Windows Desktop Runtime that you are asking about is part of .NET. While they sound the same and have a lot in common, they are not the same thing.

Here are some proper ways to detect .NET, which relates to the Windows Desktop Runtime.

Check installed .NET versions on Windows, Linux, and macOS - .NET

Learn how to list which versions of .NET are installed on your computer. This includes the .NET runtime and SDK.

learn.microsoft.com

Here are some proper ways to detect .NET Framework, which is an ancestor of modern .NET.

Determine which .NET Framework versions are installed - .NET Framework

Use code, regedit.exe, or PowerShell to detect which versions of .NET Framework are installed on a machine by querying the Windows registry. Or, check Control Panel.

learn.microsoft.com

With regard to your screenshot and the registry keys, they are perfectly normal.
Edit: If you look at the v4.0 registry key (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4.0), you'll see the default value is "deprecated." It's there for legacy reasons.

Tombar · Feb 5, 2024

Thanks, pseymour. Maybe I'm not as stupid as I was beginning to think! I'll use your links, but it's good to know the registry keys are normal

pseymour · Feb 5, 2024

Not stupid at all. It's a little difficult to keep straight: .NET Framework, .NET Core, .NET Standard, just plain old .NET.

garlin · Feb 5, 2024

Not to mention, UWP (or Store) desktop apps depend on a different set of .NET libraries unrelated to those previously listed. These are solely for UWP apps, and aren't shared with Win32 apps. Windows Update will silently update these .NET packages for you.

C:\Windows\System32>powershell "Get-AppxPackage *NET.Native* | Select PackageFullName"

PackageFullName
---------------
Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x64__8wekyb3d8bbwe
Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x64__8wekyb3d8bbwe
Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x86__8wekyb3d8bbwe
Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x86__8wekyb3d8bbwe