Hello,
Thank you, we are trying to pinpoint the threads which are active when the exception occurs.
But we made another interesting observation with a test host: The exception is NOT thrown at the moment the module is unloaded, but only afterwards, as soon as the host application loses focus. Does this help to isolate the cause of the error?