Manual mapping protected DLL causes "Initialization error 4"

Issues related to VMProtect
Requi
Posts: 8
Joined: Mon May 15, 2017 9:14 pm

Manual mapping protected DLL causes "Initialization error 4"

Postby Requi » Mon Jun 03, 2019 10:29 pm

Hello,

mapping our protected DLL manually into a process causes this error. It happens if the following options are enabled:
Imports Protection
Debugger Check
Packer

Those were the options we've tested and which caused that error. Do we have to do anything specific for VMP to load properly?

Admin
Site Admin
Posts: 1676
Joined: Mon Aug 21, 2006 8:19 pm
Location: Russia, E-burg
Contact:

Re: Manual mapping protected DLL causes "Initialization error 4"

Postby Admin » Sun Jun 09, 2019 6:48 am

It seems your code for manuall mapping has a bug. Does Windows load the protected DLL?

Requi
Posts: 8
Joined: Mon May 15, 2017 9:14 pm

Re: Manual mapping protected DLL causes "Initialization error 4"

Postby Requi » Fri Jun 14, 2019 10:14 pm

Yes Windows loads it fine. Another mapper also works. We're not sending the full PE headers from the server to the client. Only what's required for the mapping. Could that be an issue?

Requi
Posts: 8
Joined: Mon May 15, 2017 9:14 pm

Re: Manual mapping protected DLL causes "Initialization error 4"

Postby Requi » Sun Jun 23, 2019 1:10 pm

What does "Initialization error 4" mean? What couldn't get initialized? We'd love to continue using VMP, but with that it's not possible.

Admin
Site Admin
Posts: 1676
Joined: Mon Aug 21, 2006 8:19 pm
Location: Russia, E-burg
Contact:

Re: Manual mapping protected DLL causes "Initialization error 4"

Postby Admin » Sun Jun 23, 2019 2:16 pm

It means that a loader section/PE header is corrupted.