After signing out from RemoteApp RD WEB, the Remote Desktop connection process does not terminate

Question

We frequently encounter an issue where RemoteApp RD WEB freezes when using RemoteApp. Upon investigation, it was found that on the client terminal side, the Remote Desktop connection process remains in the background in the Task Manager. Although terminating this process using Task Kill allows normal usage, after signing out from RD WEB, while a disconnect notification for Remote Desktop connection appears, the process does not terminate.

Is there a way to terminate the Remote Desktop connection process after signing out? We attempted to enable group policies on both the Remote Desktop server and client terminals, but it was unsuccessful. Your assistance would be greatly appreciated.

Environment: Remote Desktop Server: Windows Server 2019 Client Terminal: Windows 10 Pro Browsers Used: Internet Explorer 11 & Edge

Answer 1

Hello,

 

Thank you for posting in Q&A forum.

Sometime after RDP session end it will generate a new process that considered part of the program and the session will not terminate until that process also terminates.

One scenario that meets this criteria is printing from a 32-bit application on a 64-bit Remote Desktop Session Host. This printing action will spawn splwow64.exe, the 32-bit to 64-bit thunking process for spooler. Splwow64.exe has a 3-minute timeout to prevent the process from being repeatedly respawned during heavy printing, so it does not immediately exit when printing is complete. This can cause the remote session to appear "hung" with a blank background.

For further details, please kindly refer to below Microsoft Official Documentation link:

https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/rd-or-remoteapp-session-not-terminate

 

Hope this answer can help you well.

Best regards，

Jill Zhou