We’ve been testing with ARM64 devices and have run across patch content that is becoming relevant to the ARM64 device which has the ARM64 version of the application installed however the result is the upgrade content changes the app architecture from the Native ARM64 version to the x64 version which then requires emulation.
An example in the BigFix updates for Windows Applications Extended site is:
ID: 5602501
Name: Update: Microsoft Visual Studio Code x64 v1.109.3 - Windows (x64)
All of the relevance contained in this version is satisfied by both an x64 as well as an ARM64 device:
//Relevance of the Upgrade content:
Q: windows of operating system
A: True
T: 2.000 ms
Q: x64 of operating system
A: True
T: 5.000 ms
Q: version of operating system > "6.3"
A: True
T: 5.000 ms
Q: exists keys whose(value "DisplayName" of it as string starts with "Microsoft Visual Studio Code") of keys "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" of (x64 registries)
A: True
T: 5.000 ms
Q: not exists (it as string as version) whose(it >= "1.109.3") of values "DisplayVersion" of keys whose(value "DisplayName" of it as string starts with "Microsoft Visual Studio Code") of keys "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" of (x64 registries)
A: True
T: 7.000 ms
//===================================================
//Additional questions to the endpoint
Q: architecture of operating system
A: ARM64
T: 7.000 ms
Q: architecture of operating system = "ARM64"
A: True
T: 10.000 ms
Have there been thoughts to both support the ARM64 native apps (where available) in the updates sites and in those cases adding a check for the architecture of the OS to help prevent non-native applications from being installed?