ASPiKreator doesn't install on Windows 11 Arm but I can compile x64 plugins!

[DrWig]

Trying out Windows 11 Arm on Mac (VM). ASPiKreator installer goes through the motions and does install the uninstaller. However, the .exe is nowhere to be seen..... I'll paste the log in a mo.

[DrWig]

2025-02-27 14:49:54.603 Log opened. (Time zone: UTC+00:00)
2025-02-27 14:49:54.603 Setup version: Inno Setup version 6.2.2
2025-02-27 14:49:54.603 Original Setup EXE: C:\Users\bruce\Documents\ASPiK\ASPiK-1.9.3\ASPiKreator\Windows\ASPiKreator Installer.exe
2025-02-27 14:49:54.603 Setup command line: /SL5="$B0520,3778035,832512,C:\Users\bruce\Documents\ASPiK\ASPiK-1.9.3\ASPiKreator\Windows\ASPiKreator Installer.exe" /SPAWNWND=$D06DC /NOTIFYWND=$250576
2025-02-27 14:49:54.603 Compatibility mode: Yes (Installer)
2025-02-27 14:49:54.603 Windows version: 10.0.26100 (NT platform: Yes)
2025-02-27 14:49:54.605 64-bit Windows: Yes
2025-02-27 14:49:54.605 Processor architecture: ARM64
2025-02-27 14:49:54.605 User privileges: Administrative
2025-02-27 14:49:54.610 Administrative install mode: Yes
2025-02-27 14:49:54.610 Install mode root key: HKEY_LOCAL_MACHINE
2025-02-27 14:49:54.610 64-bit install mode: No
2025-02-27 14:49:54.613 Created temporary directory: C:\Users\bruce\AppData\Local\Temp\is-H79VD.tmp
2025-02-27 14:50:02.703 Found 0 files to register with RestartManager.
2025-02-27 14:50:02.716 Starting the installation process.
2025-02-27 14:50:02.724 Creating directory: C:\Program Files (x86)\ASPiKreator
2025-02-27 14:50:02.726 Directory for uninstall files: C:\Program Files (x86)\ASPiKreator
2025-02-27 14:50:02.726 Creating new uninstall log: C:\Program Files (x86)\ASPiKreator\unins000.dat
2025-02-27 14:50:02.732 -- File entry --
2025-02-27 14:50:02.732 Dest filename: C:\Program Files (x86)\ASPiKreator\unins000.exe
2025-02-27 14:50:02.739 Time stamp of our file: 2025-02-27 14:49:50.373
2025-02-27 14:50:02.739 Installing the file.
2025-02-27 14:50:02.759 Successfully installed the file.
2025-02-27 14:50:02.761 -- Icon entry --
2025-02-27 14:50:02.761 Dest filename: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ASPiKreator\Un-install ASPiKreator.lnk
2025-02-27 14:50:02.763 Creating directory: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ASPiKreator
2025-02-27 14:50:02.772 Creating the icon.
2025-02-27 14:50:02.791 Successfully created the icon.
2025-02-27 14:50:02.800 Saving uninstall information.
2025-02-27 14:50:02.800 Creating new uninstall key: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\ASPiKreator_is1
2025-02-27 14:50:02.800 Writing uninstall key values.
2025-02-27 14:50:02.800 Detected previous non administrative install? No
2025-02-27 14:50:02.800 Detected previous administrative 64-bit install? No
2025-02-27 14:50:02.804 Installation process succeeded.
2025-02-27 14:50:02.806 Need to restart Windows? No
2025-02-27 14:50:04.107 Deinitializing Setup.

[DrWig]

Although the uninstaller does exist, it seems to be the wrong file name, too:

Directory of C:\Program Files (x86)\ASPiKreator

27/02/2025 14:50

.
27/02/2025 14:50 ..
27/02/2025 14:50 2,753 InstallationLogFile.log
27/02/2025 14:50 4,193 unins000.dat
27/02/2025 14:49 3,223,613 unins000.exe
3 File(s) 3,230,559 bytes
2 Dir(s) 23,341,649,920 bytes free

[DrWig]

Copying the .exe from another machine doesn't work, either (app runs, but doesn't copy the project into the specified folder). However, I can manually create a project using the template project from the SDK, and it looks like I can get Windows 11 ARM to compile for x64 if I use the following cmake command:
cmake -G"Visual Studio 17 2022" -A"x64" ../
(my Uni are making me have only one machine, so I need to get the windows stuff up and working on a Mac!)

[DrWig]

I can also report that when building for x64 on Win11 Arm, Reaper (Arm beta) recognises and runs the plugin fine. When compiling the plugin for ARM, the validator reports success and it all builds, but Reaper doesn't recognise it as a plugin...

[DrWig]

I'm now seeing Arm laptops out in the wild (students), and this issue applies to them, too, so it's not just a VM issue.