GetKeyState function does not work when you use the AttachThreadInput function to attach an input processing mechanism to a thread in Windows 7 or in Windows Server 2008 R2

Symptoms

Consider the following scenario:

  • You use the AttachThreadInput function to attach the input processing mechanism of a thread to the input processing mechanism of another thread.

  • You press a key or click a mouse button.

  • When the input notification message (such as WM_KEYDOWN, WM_SYSKEYDOWN, or WM_LBUTTONDOWN) is being processed, you perform one of the following operations:

    • You use the AttachThreadInput function to reattach the input processing mechanism to the current thread.

    • You create a window that is owned by a window in a different thread or process.

  • A call is made to the GetKeyState function.

In this scenario, the GetKeyState function returns a key or mouse button state that is not the down state. However, the key or the mouse button should remain in the down state until a corresponding key or mouse button release message (such as WM_KEYUP, WMSYSKEYUP, WM_LBUTTONUP) is processed.

Notes

  • This issue affects any application that uses the GetKeyState function or the KeyState property in this scenario.

  • This issue does not affect the GetMessage and PeekMessage functions.

  • This issue may affect the TranslateMessage function and the keyboard character messages if the key that you press is a modifier key (such as Alt, Shift, Ctrl, or Caps Lock).

Cause

This issue occurs because Windows creates a new input queue without copying the KeyState property in the scenario that is described in the "Symptoms" section. Therefore, the KeyState property of the new input queue has a null value. In this situation, every key and mouse button is in the up state or in the not toggled state.

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=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 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (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:

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

Registry information

To use the hotfix in this package, 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

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

    Version

    Product

    Milestone

    Service branch

    6.1.760
    1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • 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 R2 and for Windows 7" 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 x86-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Win32k.sys

6.1.7601.22171

2,354,688

22-Nov-2012

03:23

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

Win32k.sys

6.1.7601.22171

3,151,872

22-Nov-2012

03:28

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Win32k.sys

6.1.7601.22171

7,450,112

22-Nov-2012

02:59

IA-64


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 the AttachThreadInput function, visit the following Microsoft website:

General information about the AttachThreadInput functionFor more information about the TranslateMessage function, visit the following Microsoft website:

General information about the TranslateMessage functionFor more information about the GetKeyState function, visit the following Microsoft website:

General information about the GetKeyState functionFor more information about owned windows, visit the following Microsoft website:

General information about owned windowsFor 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 for Windows 7 and for Windows Server 2008 R2

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

File name

Update.mum

File version

Not Applicable

File size

2,136

Date (UTC)

03-Dec-2012

Time (UTC)

07:23

Platform

Not Applicable

File name

X86_fd2fc35fe4373c19d590e0ee80416b97_31bf3856ad364e35_6.1.7601.22171_none_a7d2efdf97c44f6b.manifest

File version

Not Applicable

File size

694

Date (UTC)

03-Dec-2012

Time (UTC)

07:23

Platform

Not Applicable

File name

X86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22171_none_bb407fc5121a0614.manifest

File version

Not Applicable

File size

42,086

Date (UTC)

22-Nov-2012

Time (UTC)

07:18

Platform

Not Applicable

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

File name

Amd64_25d80f3c376d04ea1b3fb47d86c7b8f3_31bf3856ad364e35_6.1.7601.22171_none_50b5bc5d6e7adcd6.manifest

File version

Not Applicable

File size

698

Date (UTC)

03-Dec-2012

Time (UTC)

07:23

Platform

Not Applicable

File name

Amd64_839f36abcfe62f0b78d9cfd048c05f38_31bf3856ad364e35_6.1.7601.22171_none_87e3cd15f8efad81.manifest

File version

Not Applicable

File size

1,038

Date (UTC)

03-Dec-2012

Time (UTC)

07:23

Platform

Not Applicable

File name

Amd64_c781921f88855a4aaa2b9f714cb45579_31bf3856ad364e35_6.1.7601.22171_none_c35757d4574ba632.manifest

File version

Not Applicable

File size

698

Date (UTC)

03-Dec-2012

Time (UTC)

07:23

Platform

Not Applicable

File name

Amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22171_none_175f1b48ca77774a.manifest

File version

Not Applicable

File size

42,090

Date (UTC)

22-Nov-2012

Time (UTC)

06:42

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

2,773

Date (UTC)

03-Dec-2012

Time (UTC)

07:23

Platform

Not Applicable

File name

Wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22171_none_21b3c59afed83945.manifest

File version

Not Applicable

File size

4,178

Date (UTC)

22-Nov-2012

Time (UTC)

07:12

Platform

Not Applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_9e3e98b4e41a8661b469314df6d0f9cc_31bf3856ad364e35_6.1.7601.22171_none_1cfeace1b00a5ed0.manifest

File version

Not Applicable

File size

1,036

Date (UTC)

03-Dec-2012

Time (UTC)

07:23

Platform

Not Applicable

File name

Ia64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22171_none_bb4223bb12180f10.manifest

File version

Not Applicable

File size

42,088

Date (UTC)

22-Nov-2012

Time (UTC)

06:39

Platform

Not Applicable

File name

Update.mum

File version

Not Applicable

File size

1,447

Date (UTC)

03-Dec-2012

Time (UTC)

07:23

Platform

Not Applicable

File name

Wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.22171_none_21b3c59afed83945.manifest

File version

Not Applicable

File size

4,178

Date (UTC)

22-Nov-2012

Time (UTC)

07:12

Platform

Not Applicable


Need more help?

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

Was this information helpful?

Thank you for your feedback!

×