Hi Marius,
When you say CMD.EXE 'hangs', does that mean that the window never
appears?  If so, I suspect that the process is running ok but it's not
running on the visible desktop.  Try this as a test:

1)  Open your service in the control panel
2)  Change the service to "Log on as:  Local System Account"
3)  Check "Allow service to interact with desktop"
4)  Run the test again

Another thing to try is to have your service write its output to a
file, and then check to see if that file exists when your test is
complete.

Hope this helps,
John

What's the command line you are passing to cmd.exe? Are you using the \C
option?

Also, remember that each user can have specific actions run when cmd.exe
starts.  See HKEY_CURRENT_USER\Software\Microsoft\Command Processor\Autorun.
...which could affect whether cmd.exe prompts the user from some input,
making it seem like it hangs.

Hi !

Just a thought. I am not familar with the process properties in .Net 2.0
[what looks you are using].
Each started process needs some desktop and you are possibly on the way
to start the new process in the same desktop, as the starter has. In
case of the started process users identity do has less rights than the
starter, it cannot access the startes desktop/winstation.

I found this starting processes with WMI, while I was logged on onto the
console as an admin, I tried to start a visible process with less
rights, which always fails for the mentioned reason. I used sysinternals
winobj then to modify the security attributes on the consiole users
dektop and this helped.

For process in .Net 2.0, I don't know.
As I said, just a thought.

Best regards,
Manfred