Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a problem on a Windows Terminal Server (2003 R2): after having launched a particular application and disconnected from TSE, the session is left on the server with the 'Down' state.

I'm not able to kill that session and the only process remaining is csrss.exe (which I can't kill).

The application is the Cygwin X server. I don't know what is done by the application to trigger that problem.

What can cause a 'Down' state? How to investigate why a session is left in this state? What tools would you recommend? I have seen nothing related in the event viewer.

share|improve this question
up vote 0 down vote accepted

Have a look at the following Citrix forum thread Down Sessions: caused by NX Client as that mentions a problem and solution with Cygwin.

According to this Tech Republic article Terminal Services Manager under Windows Server 2003 a down session state is:

Down—This state indicates that the session could not be initialized or terminated.

As far as I can tell this is can be caused by application crashing or not terminating properly.

There also appear to be hotfixes available relating to csrss.exe not responding as per another Citrix forum thread.

share|improve this answer
This might be worth contacting Microsoft support about. – Sim Oct 27 '09 at 3:13
math, how did you fix the problem in the end? – Sim Oct 31 '09 at 3:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.