Windows logo key remains pressed in Windows XP Mode after you unlock a computer that is running Windows 7 SP1

Symptoms
Consider the following scenario:
  • You run a Windows XP Mode virtual machine in full-screen mode on a computer that is running Windows 7 Service Pack 1 (SP1).
  • You lock the computer by pressing the Windows logo key+L keyboard shortcut.
  • You unlock the computer.
In this scenario, the Windows logo key remains pressed in Windows XP Mode. For example, when you press E in Windows XP Mode, Windows Explorer starts.

Notes
  • Windows Explorer should start when you press the Windows logo key+E keyboard shortcut.
  • If you use the Ctrl+Alt+Delete keyboard shortcut to lock the computer, the Ctrl and Alt keys remain pressed in Windows XP Mode after you unlock the computer.
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: 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 7 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.

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 7 file information notes
  • 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:
    VersionProductMilestoneService branch
    6.1.760 1.21xxxWindows 7SP1LDR
  • 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 nameFile versionFile sizeDateTimePlatform
Vmwindow.exe6.1.7601.222151,003,00811-Jan-201311:29x86
For all supported x64-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Vmwindow.exe6.1.7601.222151,210,36811-Jan-201312:19x64
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 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

Additional file information for Windows 7

Additional files for all supported x86-based versions of Windows 7
File nameX86_8c7cf0e701087f7e9dd010ff2d4b14de_31bf3856ad364e35_7.1.7601.22215_none_7948ce9f85c9c5e8.manifest
File versionNot applicable
File size709
Date (UTC)11-Jan-2013
Time (UTC)18:12
PlatformNot applicable
File nameX86_microsoft-windows-virtualpc-ui-vmwindow_31bf3856ad364e35_7.1.7601.22215_none_6d0b836ccc4e1c39.manifest
File versionNot applicable
File size2,186
Date (UTC)11-Jan-2013
Time (UTC)13:01
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7
File nameAmd64_cb5dcb5cb5d69c711b27afc2bd0e72b4_31bf3856ad364e35_7.1.7601.22215_none_5c44e78e3f6a4493.manifest
File versionNot applicable
File size713
Date (UTC)11-Jan-2013
Time (UTC)18:12
PlatformNot applicable
File nameAmd64_microsoft-windows-virtualpc-ui-vmwindow_31bf3856ad364e35_7.1.7601.22215_none_c92a1ef084ab8d6f.manifest
File versionNot applicable
File size2,190
Date (UTC)11-Jan-2013
Time (UTC)14:05
PlatformNot applicable
Properties

Article ID: 2801466 - Last Review: 02/13/2013 04:15:00 - Revision: 1.0

Windows 7 Service Pack 1

  • kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseinter kbsurveynew KB2801466
Feedback