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.

SHIFT does not override the automatic logon setting on a computer that is running a 64-bit edition of Windows Server 2003, Windows XP Professional x64 Edition, Windows 7 or Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running a 64-bit edition of Windows Server 2003 Service Pack 2 (SP2), Windows XP Professional x64 Edition Service Pack 2 (SP2), Windows 7 or Windows Server 2008 R2.
  • You enable automatic logon on the computer.
    Note To enable automatic logon, set the AutoAdminLogon registry value to 1 in Registry Editor. For more information, refer to the "More information" section.
  • You press SHIFT to override the automatic logon setting during operating system startup.
In this scenario, the Secure Attention Sequence (SAS) dialog box does not appear.

Note The SAS dialog box lets users enter their own account credentials and therefore override the automatic logon setting that is configured in the registry of the computer.

↑ Back to the top


Resolution

Note If you use a USB keyboard on a computer that is running Windows 7 or Windows Server 2008 R2, you must apply hotfix 2526967 after you apply hotfix 977534. For more information about hotfix 2526967, click the following article number to view the article in the Microsoft Knowledge Base:
2526967 The Shift key does not override the automatic logon setting on a computer that is running Windows 7 or Windows Server 2008 R2

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: 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 operating systems:
  • Windows XP Service Pack 2 (SP2)
  • Windows Server 2003 Service Pack 2 (SP2)
  • Windows 7
  • Windows Server 2008 R2
For more information about how to obtain a Windows XP service pack, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

For more information about how to obtain a Windows Server 2003 service pack or a Windows XP Professional x64 Edition service pack, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

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.

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 times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.
Windows XP and Windows Server 2003 file information notes
  • In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KB977534.cat) that is signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2003 SP2 and of Windows XP Professional Edition SP2
File nameFile versionFile sizeDateTimePlatform
Win32k.sys5.2.3790.46184,546,04813-Nov-200910:17x64
For all supported IA-64-based versions of Windows Server 2003 Service Pack 2
File nameFile versionFile sizeDateTimePlatform
Win32k.sys5.2.3790.46185,592,57613-Nov-200908:51IA-64
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, 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.1.760
    0.20xxx
    Windows 7 and Windows Server 2008 R2RTMLDR
  • 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 nameFile versionFile sizeDateTimePlatform
Win32k.sys6.1.7600.207832,327,55218-Aug-201002:28x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Win32k.sys6.1.7600.207833,124,22418-Aug-201002:58x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Win32k.sys6.1.7600.207837,414,78418-Aug-201002:32IA-64

↑ 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 how to enable automatic logon in Windows, see the following Microsoft Knowledge Base article:For more information about how to fix a similar issue on Windows XP Professional, see the following Microsoft Knowledge Base article:

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

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot Applicable
File size1,874
Date (UTC)18-Aug-2010
Time (UTC)07:31
PlatformNot Applicable
File nameX86_microsoft-windows-win32k_31bf3856ad364e35_6.1.7600.20783_none_b95171c714f9c3c2.manifest
File versionNot Applicable
File size42,086
Date (UTC)18-Aug-2010
Time (UTC)04:53
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7600.20783_none_15700d4acd5734f8.manifest
File versionNot Applicable
File size42,090
Date (UTC)18-Aug-2010
Time (UTC)05:50
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,530
Date (UTC)18-Aug-2010
Time (UTC)07:31
PlatformNot Applicable
File nameWow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7600.20783_none_1fc4b79d01b7f6f3.manifest
File versionNot Applicable
File size4,178
Date (UTC)18-Aug-2010
Time (UTC)04:47
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7600.20783_none_b95315bd14f7ccbe.manifest
File versionNot Applicable
File size42,088
Date (UTC)18-Aug-2010
Time (UTC)05:43
PlatformNot Applicable
File size1,684
Date (UTC)18-Aug-2010
Time (UTC)07:31
PlatformNot Applicable
File nameWow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7600.20783_none_1fc4b79d01b7f6f3.manifest
File versionNot Applicable
File size4,178
Date (UTC)18-Aug-2010
Time (UTC)04:47
PlatformNot Applicable

↑ Back to the top


Keywords: kb, kbexpertiseinter, kbfix, kbhotfixserver, kbqfe, kbautohotfix, kbsurveynew, kbprb

↑ Back to the top

Article Info
Article ID : 977534
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 266