Relevant area(s)
WinGet CLI
Relevant command(s)
winget list
Brief description of your issue
The name normalization code currently detects x86 and x64 architectures in package names, but it does not support ARM(64). This can lead to correlation failures for packages that include architecture strings in their ARP entry. While the ability to add an AppsAndFeaturesEntries entry mitigated this, it should not be required.
Steps to reproduce
On an ARM64 device, install a package with arm64 or similar in its ARP name that is not in its manifest name (Microsoft.PowerToys => PowerToys (Preview) arm64) not using winget [or we will catch the ARP entry being added and hide the issue]. Then attempt to list it and see that it is not correlated.
Expected behavior
list can correlate properly against a package installed outside of winget that includes an ARM architecture in its name.
Actual behavior
The package is nor correlated.
Environment
Relevant area(s)
WinGet CLI
Relevant command(s)
winget list
Brief description of your issue
The name normalization code currently detects x86 and x64 architectures in package names, but it does not support ARM(64). This can lead to correlation failures for packages that include architecture strings in their ARP entry. While the ability to add an
AppsAndFeaturesEntriesentry mitigated this, it should not be required.Steps to reproduce
On an ARM64 device, install a package with
arm64or similar in its ARP name that is not in its manifest name (Microsoft.PowerToys =>PowerToys (Preview) arm64) not using winget [or we will catch the ARP entry being added and hide the issue]. Then attempt to list it and see that it is not correlated.Expected behavior
list can correlate properly against a package installed outside of winget that includes an ARM architecture in its name.
Actual behavior
The package is nor correlated.
Environment