Slow Initialize on EC2 (Windows Server)

VMProtect
1

We are using VMProtect 3.8.9 version.
Initialize takes too long when running VMProtect on an EC2 instance. (c7i.2xlarge)
It takes 30 seconds to 1 minute or more to pop up UI.
(It is same to run VMProtect itself without opening a project.)

After execution, the Task Manager shows that the VMProtect process occupies 100% of one CPU core in the background, and after more than 30 seconds, the UI pops up and reduces CPU occupancy. (Console versions also take a long time to run.)
Instance performance is sufficient, so it’s not a performance issue.

For your information, the same Initialize delay occurred in the 3.9.6 version demo,
When using version 3.5, initialization was completed within 5 seconds without delay.

Could you tell me the cause of bottleneck when initializing in EC2 environment?
Also, what steps should we take to address this?

2

I have no idea what happens in EC2.

3

I found the root cause of the issue — it was related to compatibility with AWS’s 7th-generation instance architecture (c7/m7 series).
After switching to a 6th-generation instance (c6 series), VMProtect started working normally again.