VM Protect too complicated to use

[cornishcharlie]

Hi Guys, I wonder if anyone can help.
I build simple installers that I wish to protect.
I generally build the installers using actual installer, but some are just simply exe installers made from bat files.
I then usually protect them using Install Shield, and issue unlock codes. Unfortunately install shield unlock codes can be exposed using win hex.
I have been advised to use vmprotect, but it just looks too complicated.
With exe shield I applied the protection to the exe file and it produced another exe that was protected, however vmprotect seems to require alteration to the programming code, unfortunately I am no great programmer, and these are just simple installers.

How do I go about applying vmprotect to such simple installers?

[Support]

VMProtect requires you to write some code anyway. You may lock the installer's code to a serial number and ask for such number before installation.
Unless user enters the correct number, he will not be able to execute the installation code (unpacker, decryptor or something like this).

[cornishcharlie]

Thanks for the reply.
I guess I'm going to have to do a bit more study.

I have had protection by exeshield torn apart really easily with winhex, but the good hackers I know back away from vm protect