The system automatically restarts when you try to encrypt files or to decrypt files by using EFS on a computer that is running Windows Vista

Consider the following scenario:

• A third-party cryptographic service provider (CSP) is installed on a computer that is running Windows Vista.
• You log on to the system by using a smart card that stores the user credentials and the Encrypting File System (EFS) certificate.
• You try to encrypt files or to decrypt files by using EFS.

In this scenario, you receive the following warning message:Then, the system automatically restarts.

This problem occurs because an error in EFS causes the Lsass.exe process to exit unexpectedly.

If you try to encrypt files or to decrypt files by using EFS, and if the EFS certificate is stored in a smart card, EFS obtains the certificate from the smart card by using the CSP. To obtain the certificate, the CSP uses some fields in the CRYPT_KEY_PROV_INFO structure. However, EFS has not initialized all the fields in the CRYPT_KEY_PROV_INFO structure.

When the CSP tries to retrieve the uninitialized fields, an access violation occurs. This access violation causes the Lsass.exe process to exit. Then, the system restarts automatically when the system detects that the Lsass.exe process is not running.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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 this specific problem. 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

There are no prerequisites for installing this hotfix.

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 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 Vista, 32-bit versions

Windows Vista, 64-bit versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the CRYPT_KEY_PROV_INFO structure, visit the following Microsoft Developer Network (MSDN) Web site: For more information about third-party certification authority support for EFS, click the following article number to view the article in the Microsoft Knowledge Base: For more information about smart cards, visit the following Microsoft TechNet Web site:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: