A domain user account that is named Account A. Also, the check box for the Do not require Kerberos preauthentication account option is enabled on Account A.
A client computer that is running Windows 7 or Windows Server 2008 R2.
You use Account A to log on to the client computer. Then, you log off from this computer.
You use Account A to log on to this computer again after some time. For example, you use Account A to log on to this computer again after 10 seconds.
From Account A, you lock the computer.Then, you unlock the computer.
In this scenario, you receive an error message that resembles the following:
Windows has encountered a critical problem and will restart automatically in one minute. Please save your work now.
Then, the computer restarts.
When this issue occurs, the following event is logged in the Application log:
Log Name: Application Source: Microsoft-Windows-Wininit Date: <Date> Event ID: 1015 Task Category: None Level: Error Keywords: Classic User: N/A Computer: <Computer> Description:A critical system process, C:\Windows\system32\lsass.exe, failed with status code 255. The machine must now be restarted.
Note The issue also occurs when you have Account A and another user logged on to the computer. Then, you click the Switch user option from the other user account, and then you use Account A to log on to the computer again.
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.
To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.
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 of these 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
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
For all supported IA-64-based versions of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
How to enable the Do not require Kerberos preauthentication account option
To enable Do not require Kerberos preauthentication account option, follow these steps:
Use a domain administrator account to log on to the domain controller.
In the Active Directory Users and Computers snap-in, expand Users.
Right-click the user account on which you want to enable the account option, and then click Properties.
Click the Account tab in the Account options list, select the Do not require Kerberos preauthentication check box, click Apply, and then click OK.
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
Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate, Windows Web Server 2008 R2, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Standard, Windows HPC Server 2008 R2, Windows Server 2008 R2 Datacenter without Hyper-V, Windows Server 2008 R2 Enterprise without Hyper-V, Windows Server 2008 R2 Standard without Hyper-V