We simply just kill the dllhost.exe associated with it and everything is happy again.<BR><BR>Since the process is running under the ambiguous dllhost.exe COM Surrogate, I'm curious on whether anyone ...