The Winlogon.exe process uses excessive CPU resources when a user reinserts a smart card to log on to a Windows Server 2003 Service Pack 1-based terminal server

Consider the following scenario. You have a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based terminal server in your organization. To log on to this terminal server, a user is required to use an Infineon smart card together with the cryptographic service provider (CSP) that is included with Windows Server 2003. When the user exits the terminal server session, the user removes the smart card from the smart card reader that is connected to the client. Although the local system is configured to lock the terminal server session at this point, the local session remains unlocked.

Then, the user reinserts the smart card. Even though the local session is unlocked, the terminal server session no longer responds. Additionally, CPU usage for the Winlogon instance that belongs to the user session increases to almost 100 percent of the system's resources.

This problem occurs because Windows Server 2003 SP1 handles the internal objects for the smart card differently from the way that Windows Server 2003 handles this situation.

The CSP has clean-up code that does not recognize the combination of data field contents. Therefore, the clean-up code generates an endless loop. This behavior causes the session to stop responding (hang). This, in turn, triggers a significant increase in CPU usage.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. 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

You must have Windows Server 2003 SP1 installed to apply this hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 Server 2003 with SP1, x86-based versionsWindows Server 2003 with SP1, x64-based versionsWindows Server 2003 with SP1, Itanium-based versions

To work around this problem, uninstall Service Pack 1 for Windows Server 2003.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.