If something goes wrong protected file will usually end its execution with an error or just quit without any error message.

Please see the following documentation:

- Choosing the right version

Windows and .NET applications

- .NET editions notes

Support for non-standard applications

Try turning ON one or all of the following options:

- "Compatibility flag 1" option.
- "Compatibility flag 2" option.
- "Compatibility flag 3" option.
- "Enable smart DLL handling" option.

Try turning OFF one or all of the following options:

- Code, Data or Resource section encryption.

- "Check API hooking" option

- "Rename sections" option

- "Self checking against modifications" option

- "Erase import directory data" option

- "Import directory encryption" option

- "Internal overlay encryption" option (for files with internal overlay)

- "Enable anti-dumping protection" option

Additional tips

- Turn ON "Compatibility flag 1" option for Adobe Photoshop plugins.

- For Borland C++/Delphi 32bit files please try turning off data section encryption.

- For MS Visual C++ MFC projects try using "Use MFC in a static library" option instead of "Use MFC in a shared DLL".

- For ActiveX (COM) DLL try turning off "Rename sections" option.

- For Visual FoxPro 9.0 turn off "Erase import directory data" option.

- EX4J Applications: Turn OFF AOM (Advanced overlay management) option.

- Protecting a DLL with "Check program filename" option set could sometimes trigger false virus warning. Turn this option OFF if you encounter such problem.

- If debugger is active in memory unload it before running protected application.

If protected file still refuses to run please send it to us at with detailed error report so we can make further analyzing and testing.

Knowledge base