CRL processing causes high CPU usage, heavy network traffic, and service outage on a Windows Server 2008 R2-based or Windows 7-based computer

Applies to: Windows Server 2008 R2 EnterpriseWindows Server 2008 R2 DatacenterWindows Server 2008 R2 for Itanium-Based Systems More

Symptoms


Assume that you have a Windows Server 2008 R2-based domain controller that processes a large Certificate Revocation List (CRL). For example, the size of the CRL is larger than 20 megabytes (MB). In this situation, the domain controller experiences high CPU usage, heavy network traffic, and service outage.

Note The service outage occurs because the domain controller delays processing authentication requests.

Cause


This issue occurs because of the inefficient CRL decoding and fetching logic.

Resolution


Hotfix information

The hotfix packages provide the following improvements to the Windows Server 2008 R2-based domain controller:
  • Improves performance by eliminating concurrent multiple threads fetching against the same the same CRL. All successive fetch requests will then have to wait for the first fetch to complete and then share the result before they continue.
  • Optimizes memory usage for CRL decoding logic.
  • Optimizes memory allocation for on-wire fetching.
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 website: 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, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the previously released hotfix 2831238.

Status


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

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