Hi zoey,
If the process to be closed has an event handler that requires user final interaction, this can indeed block (dialog "do you want to save your file", etc.).
In my opinion, the problem is more the method used.
Personally, I've created a dedicated method that applies the Close() command and tests for correct closure, several times (in order to send the Close() command back to potentially open child dialogs) and as a last resort ends with the Terminate() command to guarantee closure (with an ultimate test for correct closure).
For the exact reason of no closure of your process, it's more the process to be closed that contains it... Are there any logs to trace what happens when it receives the close message?
