CommunicationUtilitiesResources.ConnectionTimeoutErrorMessage, this is reported there is chance that we started child process and it crashed, the timeouts should be wired up in a way that crashing the process will report the error of the crash, exit code and error output. This makes the wait shorter, and gives more info to user.

The current message should say the process was still running when the timeout occured.

There is imho related issue to this, about this problem being hard to debug.