WinGet list / Get-WinGetPackage shows incorrect PackageIdentifier and version mapping for multiple installed .NET runtimes (8/9/10)

Relevant area(s)

WinGet CLI

Relevant command(s)

No response

Brief description of your issue

WinGet is expected to identify installed applications by reading local machine metadata (Registry, MSI, Apps & Features entries) and correlate them with package manifests from the configured source.

In this case, multiple .NET runtimes (8.0, 9.0, 10.0) are installed side-by-side on the same machine. However, WinGet does not correctly maintain a 1:1 mapping between installed runtime versions and PackageIdentifiers.

Instead, it incorrectly:

Collapses multiple runtime versions into a single PackageIdentifier, OR
Shows inconsistent version mapping for different runtime IDs

This indicates a failure in WinGet’s local correlation layer, where installed application metadata is not being uniquely mapped to the correct manifest.

Evidence from Environment
Installed runtimes (correct state from dotnet CLI)
Microsoft.NETCore.App 8.0.27
Microsoft.NETCore.App 9.0.16
Microsoft.NETCore.App 10.0.8

✔ This confirms all runtimes are correctly installed side-by-side.

WinGet Behavior (Observed Issue)

Or inconsistent mapping:
Microsoft .NET Runtime 9.0 → Version 10.0.8.36029
Supporting Debug Output

From WinGet debug:

Get-WinGetPackage -Id Microsoft.DotNet.Runtime.9

Microsoft .NET Runtime 9.0 Microsoft.DotNet.Runtime.9 10.0.8.36029
Source: NexGRID

✔ Shows incorrect version association despite correct runtime installation.

Expected Behavior

Each runtime should be independently identified:

Microsoft.DotNet.Runtime.8 → 8.0.27
Microsoft.DotNet.Runtime.9 → 9.0.16
Microsoft.DotNet.Runtime.10 → 10.0.8

No cross-version mapping or identifier reuse should occur.

Steps to reproduce

Install multiple .NET runtimes side-by-side (8.0, 9.0, 10.0).
Run:
winget list Microsoft.DotNet.Runtime
Run:
Get-WinGetPackage -Id Microsoft.DotNet.Runtime.9

Expected behavior

Expected Result

Each runtime should be independently identified and mapped correctly:

Microsoft.DotNet.Runtime.8 → 8.0.27
Microsoft.DotNet.Runtime.9 → 9.0.16
Microsoft.DotNet.Runtime.10 → 10.0.8

No cross-version or shared mapping should occur.

Actual behavior

Actual Result
Multiple runtimes are mapped to the same PackageIdentifier (e.g., Microsoft.DotNet.Runtime.8)
Version shown for a runtime may not match actual installed version
Example:
Microsoft .NET Runtime 9.0 → Version 10.0.8.36029
Get-WinGetPackage returns incorrect or collapsed mappings.

Environment

winget

Reproduce with side-by-side .NET runtimes 8.0, 9.0, and 10.0, then run winget list Microsoft.DotNet.Runtime and Get-WinGetPackage -Id Microsoft.DotNet.Runtime.9. Trace the WinGet CLI local correlation layer that maps installed metadata to package identifiers and versions. Done means each runtime retains its own identifier and reports the matching installed version without cross-version mapping.