Using System.Diagnostics.Process object to execute program causes : DOTNET

I have failed to find anything in regards to this online so I am going to
try and see if someone here may know how to get around this.

I am creating a manager application that executes an external program. I
need to be able to monitor this program for crashes and restart it if needed.

The problem: When running an application, if it generates an error window.
This error window doesnt terminate the process but halts execution. Is there
a way to redirect these errors somewhere else, or possibly remove them
completely? They require user input, and even if I run my program as a
windows service, it still generates an error window that requires user input
and to the CLR the process is still running and responding fine.

I have not yet found a gracefull workaround other than to enum all the
windows which doesnt necessarly work 100% of the time depending on what
window is displayed (debuggin, drwatson, std windows error, error reporting
window etc).

Any help on this matter would be much appriciated.