Language switch fails in a RD session and shortcut menu is not displayed in a RemoteApp session in Windows 7 SP1 or Windows Server 2008 R2 SP1

Symptoms

In Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1, you experience the following issues.

Issue 1

Consider the following scenario:

  • You have a Windows 7 SP1-based or Windows Server 2008 R2 SP1-based client computer that has multiple languages configured.

  • You create a Remote Desktop (RD) session from the client computer to a Remote Desktop Protocol (RDP) server.

  • You press Alt+Shift or Ctrl+Shift to switch the input language in the RD session.

In this scenario, the language switch fails.

Notes

  • This issue occurs because the Shift key sticks during the language switch.

  • When the Shift key sticks, you also experience the following behavior:

    • You cannot type the password correctly in the RD session.

    • The input language changes during typing.

    • Multiple selections occur on every click.


Issue 2

Consider the following scenario:

  • You have some Microsoft Office applications that are published as RemoteApp applications on a Remote Desktop Session Host (RD Session Host) server.

  • You connect to the RemoteApp applications from a Windows 7 SP1-based or Windows Server 2008 R2 SP1-based client computer by using Remote Desktop Protocol (RDP) 8.0.

  • In an Office application in the RemoteApp session, you press the Alt key, and then you try to use shortcut menu.

In this scenario, the shortcut menu is no longer displayed.

Cause

Cause of Issue 1

This issue occurs because of an incorrect key scan code data is sent to the server.

Cause of Issue 2

This issue occurs because modifier keys are incorrectly synchronized when you switch between windows in the same RemoteApp client process.

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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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 7 SP1 or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

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.

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 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" 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:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.16xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    GDR

    6.2.920 0.20xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • 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 7 and for Windows Server 2008 R2" 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 7

File name

File version

File size

Date

Time

Platform

Aaclient.dll

6.2.9200.16398

269,312

10-May-2013

00:03

x86

Aaclient.mof

Not applicable

930

09-May-2013

22:56

Not applicable

Mstscax.dll

6.2.9200.20711

4,917,760

10-May-2013

00:03

x86

Mstscax.mof

Not applicable

2,055

09-May-2013

22:56

Not applicable

Tsgqec.dll

6.2.9200.16398

37,376

10-May-2013

00:03

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Aaclient.dll

6.2.9200.16398

322,560

09-May-2013

22:55

x64

Aaclient.mof

Not applicable

930

09-May-2013

22:55

Not applicable

Mstscax.dll

6.2.9200.20711

5,774,848

09-May-2013

22:55

x64

Mstscax.mof

Not applicable

2,055

09-May-2013

22:55

Not applicable

Tsgqec.dll

6.2.9200.16398

44,032

09-May-2013

22:55

x64

Aaclient.dll

6.2.9200.16398

269,312

10-May-2013

00:03

x86

Aaclient.mof

Not applicable

930

09-May-2013

22:56

Not applicable

Mstscax.dll

6.2.9200.20711

4,917,760

10-May-2013

00:03

x86

Mstscax.mof

Not applicable

2,055

09-May-2013

22:56

Not applicable

Tsgqec.dll

6.2.9200.16398

37,376

10-May-2013

00:03

x86


Workaround

To work around issue 2, press Alt+Ctrl in the session, then the shortcut menu can be displayed again.

Status

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

More Information

For more information about RDP 8.0, click the following article number to view the article in the Microsoft Knowledge Base:

2592687 Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

X86_4517da6f5cbaf30ed2505db6f35e9461_31bf3856ad364e35_7.1.7601.22321_none_2acefe5a7f57bed5.manifest

File version

Not applicable

File size

722

Date (UTC)

11-May-2013

Time (UTC)

07:43

Platform

Not applicable

File name

X86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.1.7601.22321_none_23e19d74c7f98a39.manifest

File version

Not applicable

File size

142,622

Date (UTC)

10-May-2013

Time (UTC)

05:40

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_dc16b270bec713f2d7b918aefdfbde80_31bf3856ad364e35_7.1.7601.22321_none_7f0a71320425d029.manifest

File version

Not applicable

File size

1,092

Date (UTC)

11-May-2013

Time (UTC)

07:43

Platform

Not applicable

File name

Amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.1.7601.22321_none_800038f88056fb6f.manifest

File version

Not applicable

File size

142,628

Date (UTC)

10-May-2013

Time (UTC)

05:56

Platform

Not applicable

File name

X86_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_7.1.7601.22321_none_23e19d74c7f98a39.manifest

File version

Not applicable

File size

142,622

Date (UTC)

10-May-2013

Time (UTC)

05:40

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×