Hi @olivercern Can you check the reported issue with InstallShield 2018, looks like this issue has been fixed in IS2018 (Refer IS 2018 release note @ https://helpnet.flexerasoftware.com/installshield24helplib/rn/ReleaseNotes.htm#isreleasenotes_2630790174_1049156). Hope you have mentioned about updating the project from IS2015 to IS2015 SP2. If you are updated to IS2015 SP2 and want to continue with IS2015 SP2 then you can call win32 API "SetDllDirectory" to add the SUPPORT DLL to your search path in your script. For more info on "SetDllDirectory", you can refer https://docs.microsoft.com/en-us/windows/desktop/api/winbase/nf-winbase-setdlldirectorya Better solution will be migrating to InstallShield 2018 directly from IS 2015, then your script functions will work without any changes. Second solution, continue with IS2015 SP2 and modify the script function to call the win32 function "SettDllDirectory(SUPPORTDIR)" before calling the "UseDLL" functions, and safer side call "SetDllDirectory" with and empty string after the "UseDLL" call to avoid the DLL preloading attack as mentioned in the release note.
... View more