Issue 1Assume that you have the Remote Desktop Services (RDS) role installed on a computer that is running Windows Server 2012. You run an application that uses Windows Terminal Server virtual channel APIs (such as the WtsVirtualChannelOpen and WtsVirtualChannelClose APIs) to create and use virtual channels in a Remote Desktop Protocol (RDP) session. In this situation, RDP static virtual channels do not work. Additionally, Virtual channel communication fails in the RDP session if you do not reestablish the connection.
- This issue does not affect other running RDP sessions.
- This issue can appear in different ways. For example, when you schedule several print jobs in a Remote Desktop Protocol session, the print jobs are deleted.
Issue 2Consider the following scenario:
- You have the Remote Desktop Services (RDS) role installed on a Windows Server 2012-based computer.
- You run an application that uses Windows Terminal Server virtual channel APIs (such as the WtsVirtualChannelOpen and WtsVirtualChannelClose APIs) to create and use virtual channels in a Remote Desktop Protocol (RDP) session.
- The application tries to open a static virtual channel by using a channel name that does not exist.
Cause of Issue 1This issue occurs because of a race condition that occurs when the system cannot open a static virtual channel.
Cause of Issue 2This issue occurs because the channel is not closed when the channel receives an error when the virtual channel is created.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must be running Windows Server 2012.
Registry informationTo apply this hotfix, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
ID d'article : 2802311 - Dernière mise à jour : 19 mars 2013 - Révision : 1