Quote Originally Posted by linder View Post
Yes, I see. Definitely the "Access denied" error I mentioned.

1. setup.exe starts
2. setup writes LSUNPACK decompression library into the temporary Windows folder (SUCCESS!)
3. setup uses the LoadLibrary Windows API to load the successfully created LSUNPACK library (FAILS!). This load process fails with ERROR_ACCESS_DENIDED in your case.

So "something" on this machine locks the component in the temporary Windows folder. It's a typical "false-postive".

Friedrich

Dev was not signing these dlls prior to yesterday. That has been corrected. Will be interesting to see if that resolves it. Might be worth adding a warning to your compile-time process that unsigned dynamically loaded dlls could fail to load at runtime. Not that we would know<g>