After all the debate that went on in the comments, I think that it’s better to summarize my positions in a “real” answer. First of all, it’s still not clear why you need to load a dll in DllMain with LoadLibrary. This is definitely a bad idea, since your DllMain is running inside another call … Read more
It sounds like you want each instance of the DLL to have separate data segments. That’s the only reason I can think of for the question. The only way to achieve this is to make sure that each time you call LoadLibrary, the DLL has a different filename. Copy the DLL to a temporary file … Read more
Windows dll error 126 can have many root causes. The most useful methods I have found to debug this are: Use dependency walker to look for any obvious problems (which you have already done) Use the sysinternals utility Process Monitor https://docs.microsoft.com/en-us/sysinternals/downloads/procmon from Microsoft to trace all file access while your dll is trying to load. … Read more
You can only load a 32bit DLL into a 64 bit process when you are loading the dll as a datafile. You can’t execute the code. (http://support.microsoft.com/kb/282423) Microsoft recommends that you use interprocess COM to use 32 bit code with a 64 bit application. Here’s an article explaining the process.