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>