High CPU usage on a Windows Server 2012-based server when many client computers connect to the server

Applies to: Windows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 Essentials

Symptoms


Assume that many client computers that have unique IP addresses connect to a Windows Server 2012-based server. For example, more than 100,000 client computers that have unique IP addresses connect to the server. In this situation, the network traffic stalls, and the server experiences high CPU usage.

Cause


This issue occurs because the periodic cleanup routine for the local cache holds lots of locks during operations that consume lots of resources.

Resolution


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.

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 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 Server 2012.

Registry information

To use the hotfix in this package, 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 does not replace a previously released hotfix.

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

Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_6f8da144bf9129ce473a38403bfaf001_31bf3856ad364e35_6.2.9200.20678_none_101e4385a28ed437.manifest
File versionNot applicable
File size706
Date (UTC)02-Apr-2013
Time (UTC)10:41
PlatformNot applicable
File nameAmd64_af269963821c543127da946566ff0d97_31bf3856ad364e35_6.2.9200.16574_none_817d34f292b29eb6.manifest
File versionNot applicable
File size706
Date (UTC)02-Apr-2013
Time (UTC)10:41
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.16574_none_0bf28d6ef022554a.manifest
File versionNot applicable
File size3,884
Date (UTC)02-Apr-2013
Time (UTC)00:54
PlatformNot applicable
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.20678_none_0c802b62093c5a70.manifest
File versionNot applicable
File size3,887
Date (UTC)02-Apr-2013
Time (UTC)10:41
PlatformNot applicable
File nameUpdate-bf.mum
File versionNot applicable
File size1,593
Date (UTC)02-Apr-2013
Time (UTC)10:41
PlatformNot applicable