Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. RDP virtual static channels don't work and an operation stalls in Windows Server 2012

RDP virtual static channels don't work and an operation stalls in Windows Server 2012

View products that this article applies to.

Symptoms

On a Windows Server 2012-based computer that has the Remote Desktop Services (RDS) role installed, the following issues occur.

Issue 1

Assume 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.

Notes
  • 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 2

Consider 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.
In this scenario, the operation that opens the static virtual channel stalls for 10 seconds when the system tries to open the nonexistent virtual channel again.

↑ Back to the top

Cause

Cause of Issue 1

This issue occurs because of a race condition that occurs when the system cannot open a static virtual channel.

Cause of Issue 2

This issue occurs because the channel is not closed when the channel receives an error when the virtual channel is created.

↑ Back to the top

Resolution

Hotfix information


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:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2012.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 file information notes

Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2012

File nameFile versionFile sizeDateTimePlatform
Rdpcorets.dll6.2.9200.164993,246,59213-Jan-201323:24x64
Rdpudd.dll6.2.9200.16434235,52012-Oct-201205:50x64
Rdpvideominiport.sys6.2.9200.1643427,88012-Oct-201208:08x64
Rfxvmt.dll6.2.9200.1643436,35212-Oct-201206:14x64
Rdpcorets.dll6.2.9200.206063,246,08013-Jan-201323:21x64
Rdpudd.dll6.2.9200.16384235,52026-Jul-201202:30x64
Rdpvideominiport.sys6.2.9200.1638427,88826-Jul-201203:17x64
Rfxvmt.dll6.2.9200.1638436,35226-Jul-201203:07x64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about the static virtual channel, go to the following Microsoft website:
General information about static and dynamic virtual channels
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File nameAmd64_3f7edad328636aff622707828a6e41af_31bf3856ad364e35_6.2.9200.20607_none_dd2aafee74d49dfc.manifest
File versionNot applicable
File size729
Date (UTC)14-Jan-2013
Time (UTC)18:36
PlatformNot applicable
File nameAmd64_d42324a2d55189f4b91da8bf9b44c405_31bf3856ad364e35_6.2.9200.16500_none_cc71fe0a6f8a71fe.manifest
File versionNot applicable
File size729
Date (UTC)14-Jan-2013
Time (UTC)18:36
PlatformNot applicable
File nameAmd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.2.9200.16500_none_88aa540c915617f2.manifest
File versionNot applicable
File size13,555
Date (UTC)14-Jan-2013
Time (UTC)18:37
PlatformNot applicable
File nameAmd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.2.9200.20607_none_893af2ddaa6d691d.manifest
File versionNot applicable
File size13,555
Date (UTC)14-Jan-2013
Time (UTC)18:37
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2802311
Revision : 1
Created on : 1/7/2017
Published on : 3/19/2013
Exists online : False
Views : 148