RDS Session does not terminate due to a spawned background process.
Posted by Christopher Flores on 08 May 2015 04:49 AM


Sometimes it may be required to terminate specific open processes once a RemoteDesktopSession is closed. These trailing processes could possibly prevent graceful disconnection from 2X Clients or keep the session in an active state.  This behavior is documented in the following Microsoft article here.

Versions affected

  • RemoteDesktopServices 2008R2+


In order to alleviate such issues which might keep RDS Sessions open, the adding the incriminating process to the SysProcs key on your RDS server should help in allowing a graceful disconnect or logoff from a session.

This may be achieved with the following steps:

  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\SysProcs
  3. Right-click the SysProcs key, point to New, and then click DWORD Value.
  4. Type the name of the process in the Name box, and then press ENTER.
  5. Double-click DWORD created to open the Edit DWORD Value box.
  6. If the DWORD value is anything other than 0, change the value to 0, and then click OK. If the DWORD value is 0, click Cancel


For more information why such a change might be needed, referring to Microsoft's Remote App Session Termination logic can provide a better understanding when to use the information contained within this article. Such documentation may be found here.

(0 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name: