Hi Mark,

IMO, it does not resolve this specific "0002:0005" loader issue. Because something "blocked" the Windows API LoadLibrary action on this machine, the LSUNPACK decompression function was not available and the setup.exe did not continue with the "support file" processing. So your own (unsigned) DLLs could not trigger any false-positive action.

But you are absolutely right. Unsigned "support file" DLLs are definitely candidates for a false-positive nightmare. I have added your compiler warning idea to the ToDo list. BTW, perhaps we can add an option to automatically code-sign the support file(s). Thank you for your suggestion.

Friedrich