Hardware ID changes after upgrading VMP from version 3.8.2 to VMP3.8.6

[paituo]

1. Using version 3.8.2 of the shell adding tool, the generated hardware ID (hwid) is as follows:

1111111.png (4.86 KiB) Viewed 1437 times

CPU：0x90,0xb5,0xf2,0x84
HWID：kLXyhHl1FGE/07DSOu6xFw==
HOST：0x79,0x75,0x14,0x61
NET：0x3a,0xee,0xb1,0x17
HDD：0x3f,0xd3,0xb0,0xd2

2. Using version 3.8.6 of the shell adding tool, the generated hardware ID (hwid) is as follows:

222222.png (5.15 KiB) Viewed 1437 times

HWID：DHWpQXl1FGE/07DSOu6xFw==
CPU：0xc,0x75,0xa9,0x41
HOST：0x79,0x75,0x14,0x61
NET：0x3a,0xee,0xb1,0x17
HDD：0x3f,0xd3,0xb0,0xd2

3. Files with different versions of the unified program after shelling:


4. Conclusion:
In summary, after replacing the VMP version, the CPU field in the hardware ID (hwid) generated by the same computer will be different.

[Admin]

VMProtect 3.8.6 supports CPUID with enabled Hyper-V. Previous versions generate different CPUID (with/without Hyper-V) on the same computer.

[paituo]

VMProtect 3.8.6 supports CPUID with enabled Hyper-V. Previous versions generate different CPUID (with/without Hyper-V) on the same computer.

The change in hardware ID will result in all previous authorizations given to customers becoming invalid.
Customers must provide new machine codes and replace each authorization one by one. This workload is too large,
and it is uncertain whether customers have engaged in deceiving another computer's hardware ID to obtain more authorized hardware.

Can CPUID that supports Hyper-V or compatibility with old hardware ID rules
be determined through selection during VMProtect processing?

[Admin]

The change in hardware ID will result in all previous authorizations given to customers becoming invalid.

The latest version supports serial numbers generated by previous versions because it also uses old CPUID for checking a serial number (HWID doesn't show "deprecated" CPUID):

Code: Select all

HardwareID::HardwareID() 
{
...
	// old methods
	GetCPU(1);
	GetHDD(1);
	start_block_ = block_count_;
	// new methods, we'll return HWID starting from this DWORD
	GetCPU(2); 
	GetMachineName();
	GetHDD(2);
	GetMacAddresses();
}

Anyway, you shouldn't compare HWIDs by value for your internal use.

[Jules90]

There is a possible issue in Vmware 16.2.4.28481 with Vmprotect 3.8.6. sdk functions using license tied HWID, more investigations needed, will return with more info's if bug confirmed.