Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
The LSASS.exe process crashes and the computer restarts when you try to start the Network Access Protection Agent service on a Windows XP Service Pack 3 -based client computer
Article ID: 954879 - View products that this article applies to.
In a network environment, you deploy Network Access Protection (NAP) Internet Protocol security (IPsec) enforcement. However, when you try to start the Network Access Protection Agent service on a Windows XP Service Pack 3 (SP3)-based client computer, the LSASS.exe process crashes. Additionally, the computer restarts. If you configured the service to start automatically, the computer crashes after each restart.
This problem occurs because NAP is a new feature in Windows XP SP3. NAP has a new health policy enforcement mechanism. IPsec enforcement is part of NAP enforcement. To implement IPsec enforcement in Windows XP SP3, the client must obtain the NAP Health Certificate from the Health Registration Authority (HRA) server. To obtain the health certificate, the client must provide its health status. If the client uses Kerberos authentication to establish the connection to the HRA server to obtain the certificate, some security associations are generated on the client computer. After the client computer receives the health certificate, the client computer deletes the old security associations. However, the client computer runs a check for a non-null pointer on security associations. Because the security associations were deleted, a crash occurs.
Hotfix informationA 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 this specific problem.
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, submit a request to 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.
PrerequisitesTo apply this hotfix, you must have Windows XP Service Pack 3 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322389/ )How to obtain the latest Windows XP service pack
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows XP with Service Pack 3, x86-based versions
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about NAP IPsec enforcement, visit the following Web site:
http://technet.microsoft.com/en-us/library/cc726008.aspxFor more information about IPsec enforcement client, visit the following Web site: