A terminal server session that is shadowed is incorrectly disconnected when the terminal server session that is shadowing stops shadowing on a computer that is running Windows Vista or Windows Server 2008

Article translations Article translations
Article ID: 976110 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • The Group Policy Set compression algorithm for RDP data is enabled on a terminal server that is running Windows Server 2008, Windows Server 2008 R2, or Windows Server 2003. The algorithm is set to the Optimized to use less network bandwidth option or set to the Optimize to use less memory option.

    Note By default, these settings are set on a terminal server that is running Windows Server 2008 R2.
  • A user connects to the terminal server that is running Windows Server 2008 or Windows Server 2008 R2 by using Remote Desktop Connection (RDC) client version 6.0 or 6.1. Or, a user connects to a terminal server that is running Windows Server 2003 by using RDC 6.0.6001.xxxxx on Windows XP Service Pack 3 (SP3) or by using RDC 6.1.7600.xxxxx on Windows 7.
  • You connect to the same terminal server session by using Remote Desktop Connection (RDC) client version 6.0, 6.1, or 7.0. You remotely control from this terminal server session the terminal server session that was previously made. Then you end the remote control action.

    Note The remote control action is also known as a "Shadowing" action.
In this scenario, the terminal server session that is shadowed is incorrectly disconnected. Additionally, the user receives the following error message:
Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again
When you use RDC client 7.0 to shadow a terminal server session, you can end shadowing successfully and return to your own session. When you use RDC client 6.0 or 6.1 to shadow a terminal server session, your session is disconnected together with the same error message.

CAUSE

When shadowing ends, the RDC client 6.0 or 6.1 clients do not reset compression or decompression context. This behavior causes the shadowed terminal server session to disconnect because the compression context is incorrectly affected.

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 Web site:
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, your computer must be running one of the following Windows operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
Additionally, RDP 6.0 or 6.1 must be installed.

For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Installation instructions

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

File information

The English (United States) 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 Vista and Windows Server 2008 file information notes


Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both of these operating systems, select the hotfix that is listed under "Windows Vista" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.0.600 0 . 20xxxWindows VistaRTMLDR
    6.0.600 1 . 22xxxWindows Vista and Windows Server 2008SP1LDR
    6.0.600 2 . 22xxxWindows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • 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 2008 and for Windows Vista" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Aaclient.dll6.0.6001.22564136,19216-Nov-200914:07x86
Aaclient.mofNot Applicable1,09701-Apr-200918:53Not Applicable
Mstscax.dll6.0.6001.225642,067,96816-Nov-200914:11x86
Mstscax.mofNot Applicable1,96701-Apr-200918:54Not Applicable
Tsgqec.dll6.0.6001.2256453,24816-Nov-200914:12x86
Aaclient.dll6.0.6002.22268136,19216-Nov-200913:58x86
Aaclient.mofNot Applicable1,09703-Apr-200920:41Not Applicable
Mstscax.dll6.0.6002.222682,066,94416-Nov-200914:01x86
Mstscax.mofNot Applicable1,96703-Apr-200920:42Not Applicable
Tsgqec.dll6.0.6002.2226853,24816-Nov-200914:03x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Aaclient.dll6.0.6001.22564151,55216-Nov-200914:44x64
Aaclient.mofNot Applicable1,09701-Apr-200915:54Not Applicable
Mstscax.dll6.0.6001.225642,424,83216-Nov-200914:48x64
Mstscax.mofNot Applicable1,96701-Apr-200915:55Not Applicable
Tsgqec.dll6.0.6001.2256445,05616-Nov-200914:50x64
Aaclient.dll6.0.6002.22268151,55216-Nov-200913:57x64
Aaclient.mofNot Applicable1,09703-Apr-200920:39Not Applicable
Mstscax.dll6.0.6002.222682,424,83216-Nov-200913:59x64
Mstscax.mofNot Applicable1,96703-Apr-200920:40Not Applicable
Tsgqec.dll6.0.6002.2226845,05616-Nov-200914:01x64
For all supported IA-64-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Aaclient.dll6.0.6001.22564298,49616-Nov-200916:28IA-64
Aaclient.mofNot Applicable1,09701-Apr-200915:54Not Applicable
Mstscax.dll6.0.6001.225644,935,16816-Nov-200916:32IA-64
Mstscax.mofNot Applicable1,96701-Apr-200915:56Not Applicable
Tsgqec.dll6.0.6001.2256480,38416-Nov-200916:34IA-64
Aaclient.dll6.0.6002.22268298,49616-Nov-200913:50IA-64
Aaclient.mofNot Applicable1,09703-Apr-200920:39Not Applicable
Mstscax.dll6.0.6002.222684,935,16816-Nov-200913:53IA-64
Mstscax.mofNot Applicable1,96703-Apr-200920:40Not Applicable
Tsgqec.dll6.0.6002.2226880,38416-Nov-200913:55IA-64

STATUS

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

WORKAROUND

Workaround for Windows Server 2008 or for Windows Server 2008 R2

To work around this issue, disable the Set compression algorithm for RDP data policy on terminal servers.

To disable this policy on terminal servers that are running Windows Server 2008, follow these steps:
  1. Open the Local Group Policy Editor, and then locate the following policy:
    Computer Configuration\Administrative Templates\Windows Component\Terminal Services\Terminal Server\Remote Session Environment\Set compression algorithm for RDP data
  2. Set the value for this policy to Balances memory usage and network bandwidth.
  3. Refresh the Group Policy settings to apply the settings.
To disable this policy on terminal servers that are running Windows Server 2008 R2, follow these steps:
  1. Open the Local Group Policy Editor, and then locate the following policy:
    Computer Configuration\Administrative Templates\Windows Component\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment\Set compression algorithm for RDP data
  2. Set the value of Set compression algorithm for RDP data to Do not use an RDP compression algorithm.
  3. Refresh Group Policy settings to apply the settings.

Workaround for Windows XP Service Pack 3 or for Windows 7

To work around this issue, click to clear the Desktop Composition check box on the Experience tab in the Remote Desktop Connection dialog box of the RDC client.

MORE INFORMATION

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 Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
X86_078d4c8b24d675e125121cac41dc2676_31bf3856ad364e35_6.0.6002.22268_none_986637fe4f223ce6.manifestNot Applicable72217-Nov-200910:32Not Applicable
X86_9e9ed2f1c9a43fc59e36d7d81baf1bc9_31bf3856ad364e35_6.0.6001.22564_none_810b92c99d5de0e9.manifestNot Applicable72217-Nov-200910:32Not Applicable
X86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.0.6001.22564_none_303acdbfdef2d7e5.manifestNot Applicable235,76216-Nov-200917:36Not Applicable
X86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.0.6002.22268_none_322540cfdc159265.manifestNot Applicable235,76216-Nov-200916:02Not Applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.0.6001.22564_none_8c5969439750491b.manifestNot Applicable235,82816-Nov-200919:01Not Applicable
Amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.0.6002.22268_none_8e43dc539473039b.manifestNot Applicable235,82816-Nov-200918:43Not Applicable
X86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.0.6001.22564_none_303acdbfdef2d7e5.manifestNot Applicable235,76216-Nov-200917:36Not Applicable
X86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.0.6002.22268_none_322540cfdc159265.manifestNot Applicable235,76216-Nov-200916:02Not Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_2ba7744cc4ec1d79f9a302c893b9defc_31bf3856ad364e35_6.0.6002.22268_none_614dff7c349559a2.manifestNot Applicable1,09017-Nov-200910:32Not Applicable
Ia64_d654faf7adc91f1680cf644484491454_31bf3856ad364e35_6.0.6001.22564_none_95ff1a49dfba2eaf.manifestNot Applicable1,09017-Nov-200910:32Not Applicable
Ia64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.0.6001.22564_none_303c71b5def0e0e1.manifestNot Applicable235,79517-Nov-200902:14Not Applicable
Ia64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_6.0.6002.22268_none_3226e4c5dc139b61.manifestNot Applicable235,79516-Nov-200915:18Not Applicable

Properties

Article ID: 976110 - Last Review: April 6, 2010 - Revision: 2.0
APPLIES TO
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 Standard without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Web Server 2008
  • Windows HPC Server 2008
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Starter
  • Windows Vista Ultimate
Keywords: 
kbqfe kbhotfixserver kbsurveynew kbautohotfix kbexpertiseinter kbexpertiseadvanced kbbug kbfix KB976110

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com