Initialization Error 1 on Manually Mapped Module

VMProtect
1

Hello there,

I have an active VMProtect Ultimate license.
I am trying to load my module protected with VMProtect using my manual mapper library. When the module loads, VMProtect produces “Initialization Error 1”. This does not happen to non-protected modules. This happens on any module protected by VMProtect, even a dummy DLL. I have played around with the Memory Protection, Import Protection, Resource Protection, Packing, and Debugger settings. Changing any of these settings does not change the outcome. No matter what, initialization error 1 is prompted.

I have also attempted to preserve all PE headers instead of erasing them, this does not change anything.

I am testing this on my local machine and can reproduce it easily.

2

“Initialization error 1” means that VirtualProtect has returned an error while working the vmprotect loader.

3

Is there anymore information you can provide so I can attempt to prevent this from happening?

To be clear, I use VirtualProtect in my own code in the module being loaded and it works fine without error.