I am running Windows 11 ARM64 in a Parallels Desktop virtual machine on an Apple M3 Mac.
When attempting to upgrade VeraCrypt using the official ARM64 MSI installer (VeraCrypt_Setup_arm64_1.26.31.msi), Windows Installer immediately rejects the package with error 1633:
This installation package is not supported
by this processor type.
Contact your product vendor.
Environment:
Host: Apple M3, macOS
Virtualization: Parallels Desktop
Guest OS: Windows 11 ARM64
Windows Installer: 5.0.26100.9711
PowerShell process architecture: Arm64
VeraCrypt version: 1.26.31
MSI inspection:
Template Summary: arm64;1033
ProductVersion: 1.26.31
All 730 components have the 64-bit attribute set.
The MSI digital signature is accepted.
Interesting observation:
The x64 MSI installer (VeraCrypt_Setup_x64_1.26.31.msi) installs successfully on the same Windows ARM64 system.
Furthermore, the installed VeraCrypt kernel driver is running and has been independently verified as a native ARM64 PE binary:
This suggests that VeraCrypt can deploy its native ARM64 driver successfully through the x64 installer, while the dedicated ARM64 MSI is rejected before installation begins.
Question:
Is this a known issue with the ARM64 MSI package in version 1.26.31, or could it be related to Windows Installer's interpretation of the MSI platform metadata?
I can provide the verbose Windows Installer log, which confirms error 1633.
Hello,
I am running Windows 11 ARM64 in a Parallels Desktop virtual machine on an Apple M3 Mac.
When attempting to upgrade VeraCrypt using the official ARM64 MSI installer (VeraCrypt_Setup_arm64_1.26.31.msi), Windows Installer immediately rejects the package with error 1633:
This installation package is not supported
by this processor type.
Contact your product vendor.
Environment:
Host: Apple M3, macOS
Virtualization: Parallels Desktop
Guest OS: Windows 11 ARM64
Windows Installer: 5.0.26100.9711
PowerShell process architecture: Arm64
VeraCrypt version: 1.26.31
MSI inspection:
Template Summary: arm64;1033
ProductVersion: 1.26.31
All 730 components have the 64-bit attribute set.
The MSI digital signature is accepted.
Interesting observation:
The x64 MSI installer (VeraCrypt_Setup_x64_1.26.31.msi) installs successfully on the same Windows ARM64 system.
Furthermore, the installed VeraCrypt kernel driver is running and has been independently verified as a native ARM64 PE binary:
Driver: C:\Windows\System32\drivers\veracrypt.sys
State: Running
Architecture: ARM64 (PE Machine 0xAA64)
FileVersion: 1.26.31
This suggests that VeraCrypt can deploy its native ARM64 driver successfully through the x64 installer, while the dedicated ARM64 MSI is rejected before installation begins.
Question:
Is this a known issue with the ARM64 MSI package in version 1.26.31, or could it be related to Windows Installer's interpretation of the MSI platform metadata?
I can provide the verbose Windows Installer log, which confirms error 1633.
Thank you for your assistance.