HiroyukiYano
Bit poster
Hello,
I have found a reproducible compatibility regression between Parallels Desktop 27.0.0 and 27.0.2 on an Apple Silicon Mac running a Windows 11 ARM virtual machine.
Parallels Desktop 27.0.0 (Build 58628):
Downgrading Parallels Desktop from 27.0.2 back to 27.0.0 immediately changes the reported CPU clock from 3200 MHz back to 3072 MHz. The same application and the same existing license then work normally again.
Upgrading again from 27.0.0 to 27.0.2 changes the reported CPU clock back to 3200 MHz, and the Sentinel LDK "clone detected" error is reproduced.
I compared the VM configuration (config.pvs) between 27.0.0 and 27.0.2. The CPU configuration values are effectively identical. The VM UUID and other major VM identity information are also unchanged.
I also tested disabling Adaptive Hypervisor and disabling "Faster virtual machine" under 27.0.2, but Windows still reports 3200 MHz.
This appears to indicate that Parallels Desktop after 27.0.0 changed some virtual CPU characteristics exposed to the Windows 11 ARM guest. Since Sentinel LDK uses CPU characteristics as part of VM clone detection, this may cause an existing machine-bound license to be treated as cloned.
Technical Report ID: 530372504
Could Parallels please confirm whether the virtual CPU characteristics exposed to Windows 11 ARM changed after Parallels Desktop 27.0.0 (Build 58628)?
Is there a supported setting in Parallels Desktop 27.0.2 that can preserve the same virtual CPU characteristics as 27.0.0 for compatibility with existing machine-bound licenses?
Thank you.
I have found a reproducible compatibility regression between Parallels Desktop 27.0.0 and 27.0.2 on an Apple Silicon Mac running a Windows 11 ARM virtual machine.
Parallels Desktop 27.0.0 (Build 58628):
- Windows reports the virtual CPU as "Apple Silicon"
- ProcessorId: 00000000410F0000
- MaxClockSpeed: 3072 MHz
- CurrentClockSpeed: 3072 MHz
- An application protected by Sentinel LDK with a PC-bound software license starts normally.
- No Sentinel clone detection error is generated.
- Same Windows 11 ARM VM
- Same VM UUID
- Same ProcessorId: 00000000410F0000
- Same number of virtual CPUs (4)
- MaxClockSpeed: 3200 MHz
- CurrentClockSpeed: 3200 MHz
- The same Sentinel LDK protected application can no longer use its existing PC-bound license.
- Sentinel LDK records:
Downgrading Parallels Desktop from 27.0.2 back to 27.0.0 immediately changes the reported CPU clock from 3200 MHz back to 3072 MHz. The same application and the same existing license then work normally again.
Upgrading again from 27.0.0 to 27.0.2 changes the reported CPU clock back to 3200 MHz, and the Sentinel LDK "clone detected" error is reproduced.
I compared the VM configuration (config.pvs) between 27.0.0 and 27.0.2. The CPU configuration values are effectively identical. The VM UUID and other major VM identity information are also unchanged.
I also tested disabling Adaptive Hypervisor and disabling "Faster virtual machine" under 27.0.2, but Windows still reports 3200 MHz.
This appears to indicate that Parallels Desktop after 27.0.0 changed some virtual CPU characteristics exposed to the Windows 11 ARM guest. Since Sentinel LDK uses CPU characteristics as part of VM clone detection, this may cause an existing machine-bound license to be treated as cloned.
Technical Report ID: 530372504
Could Parallels please confirm whether the virtual CPU characteristics exposed to Windows 11 ARM changed after Parallels Desktop 27.0.0 (Build 58628)?
Is there a supported setting in Parallels Desktop 27.0.2 that can preserve the same virtual CPU characteristics as 27.0.0 for compatibility with existing machine-bound licenses?
Thank you.