Thank you for the detailed reply, @i_mazlov!

I was unable to determine the root cause of the issue, however I was able to work around it by preloading direct dependencies with a FileExecute call and using the SearchPath Windows function to locate the runtime dependency DLLs and pass the absolute paths to LoadLibrary (I'm aware this is not recommended, but should be fine for this internally used plugin).

I couldn't find anything in the newly added Maxon options that appeared to affect the loading behavior. My only remaining theory is that the new licensing process is indirectly triggering this behavior:
LoadLibrary function returns STATUS_DLL_NOT_FOUND error on impersonate thread in Windows
https://learn.microsoft.com/en-us/troubleshoot/windows-client/setup-upgrade-and-drivers/loadlibrary-function-returns-status-dll-not-found-error-impersonate-thread

Thanks again!
Nick

Thank you for the detailed reply, @i_mazlov!

I was unable to determine the root cause of the issue, however I was able to work around it by preloading direct dependencies with a FileExecute call and using the SearchPath Windows function to locate the runtime dependency DLLs and pass the absolute paths to LoadLibrary (I'm aware this is not recommended, but should be fine for this internally used plugin).

I couldn't find anything in the newly added Maxon options that appeared to affect the loading behavior. My only remaining theory is that the new licensing process is indirectly triggering this behavior:
LoadLibrary function returns STATUS_DLL_NOT_FOUND error on impersonate thread in Windows
https://learn.microsoft.com/en-us/troubleshoot/windows-client/setup-upgrade-and-drivers/loadlibrary-function-returns-status-dll-not-found-error-impersonate-thread

Thanks again!
Nick

I have a custom ZBrush plugin that I have been using successfully with ZBrush 2022 and 2023. The main functionality is contained within a DLL and my ZScript uses the FileExecute command to call into it. My DLL has some directly linked colocated dependencies as well as some dynamically loaded internal and external dependencies.

Starting with 2024, the dependencies are no longer loaded when running FileExecute. If I manually call FileExecute on the direct dependencies themselves first, the plugin is able to load correctly. For the dynamically loaded dependencies, C++ calls to LoadLibrary with a relative path to load the dependency from the system search paths fails. Passing absolute paths does work, but these paths can vary between users. Any information about what has changed with DLL loading in 2024 or advice for how to handle this would be greatly appreciated!