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.

In an MIT realm, user authentication fails after invalid credentials are received on a computer that is running 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 Windows 7 or Windows Server 2008 R2.
  • The computer is joined to a Massachusetts Institute of Technology (MIT) realm as a client computer.
  • An invalid user credential is entered on the computer.
In this scenario, all successive user authentications fail. Therefore, you have to restart the computer to resolve the problem.

↑ Back to the top


Cause

This issue is caused by a dead lock situation in the Lsass.exe process.

↑ Back to the top


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: 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 Windows 7 or Windows Server 2008 R2.

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 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 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 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Kerberos.dll6.1.7600.20589541,18404-Dec-200921:24x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformService branch
Kerberos.dll6.1.7600.20589714,75204-Dec-200921:43x64Not Applicable
Kerberos.dll6.1.7600.20589541,18404-Dec-200921:24x86WOW
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformService branch
Kerberos.dll6.1.7600.205891,498,62404-Dec-200908:57IA-64Not Applicable
Kerberos.dll6.1.7600.20589541,18404-Dec-200921:24x86WOW

↑ 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 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Update.mumNot Applicable1,67405-Dec-200900:17Not Applicable
X86_770f6f7b769c60e3cb46719e6dd3fb2c_31bf3856ad364e35_6.1.7600.20589_none_1b75f5072eb59bf2.manifestNot Applicable70505-Dec-200900:17Not Applicable
X86_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.20589_none_e73ad3282b3b27b6.manifestNot Applicable33,21804-Dec-200921:47Not Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_dfc40a43da2fa9e10295f2af2bc47123_31bf3856ad364e35_6.1.7600.20589_none_65562d2e45829514.manifestNot Applicable1,06005-Dec-200900:17Not Applicable
Amd64_f152749c236f239599bdf7ebc1f6bd63_31bf3856ad364e35_6.1.7600.20589_none_bd32a24bad1f233f.manifestNot Applicable70905-Dec-200900:17Not Applicable
Amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.20589_none_43596eabe39898ec.manifestNot Applicable33,22204-Dec-200922:30Not Applicable
Update.mumNot Applicable1,90605-Dec-200900:17Not Applicable
Wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.20589_none_4dae18fe17f95ae7.manifestNot Applicable22,96704-Dec-200921:40Not Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_00a5463e4693c80545349c80f835592c_31bf3856ad364e35_6.1.7600.20589_none_1de327f06bd38074.manifestNot Applicable1,05805-Dec-200900:17Not Applicable
Ia64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.20589_none_e73c771e2b3930b2.manifestNot Applicable33,22004-Dec-200922:27Not Applicable
Update.mumNot Applicable1,68405-Dec-200900:17Not Applicable
Wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7600.20589_none_4dae18fe17f95ae7.manifestNot Applicable22,96704-Dec-200921:40Not Applicable

↑ Back to the top


Keywords: kbsurveynew, kbexpertiseadvanced, kbqfe, kbautohotfix, kbhotfixserver, kbfix, KB978116

↑ Back to the top

Article Info
Article ID : 978116
Revision : 2
Created on : 12/31/2009
Published on : 12/31/2009
Exists online : False
Views : 323