Microsoft Knowledge Base Archive

Symptoms

Assume that you have some Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1-based client computers in a domain environment. You deploy Group Policy preferences on the domain, and item-level targeting is configured for security groups. In this situation, you receive the following error message:

WSAENOBUFS (10055)
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

Specifically, the client computers may experience TCP port exhaustion, and a "no buffer space available" or "insufficient buffer space" exception occurs on the computer. Then, the TCP port exhaustion causes key operations to fail.

↑ Back to the top

uter. Then, the TCP port exhaustion causes key operations to fail.

↑ Back to the top

Cause

This issue occurs because a Group Policy client service leaks an AFD endpoint handle.

↑ Back to the top

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 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:

http://support.microsoft.com/contactus/?ws=support

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 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 does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version Product Milestone Service branch
6.1.760
1.22xxx Windows 7 and Windows Server 2008 R2 SP1 LDR
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

Version	Product	Milestone	Service branch
6.1.760 1.22xxx	Windows 7 and Windows Server 2008 R2	SP1	LDR

For all supported x86-based versions of Windows 7

File name	File version	File size	Date	Time	Platform
Gpprefcl.dll	6.1.7601.22374	589,312	02-Jul-2013	05:05	x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name	File version	File size	Date	Time	Platform
Gpprefcl.dll	6.1.7601.22374	789,504	02-Jul-2013	05:12	x64
Gpprefcl.dll	6.1.7601.22374	589,312	02-Jul-2013	05:05	x86
Gpprefcl.dll	6.1.7601.22374	589,312	02-Jul-2013	05:05	x86

For all supported IA-64-based versions of Windows Server 2008 R2

File name	File version	File size	Date	Time	Platform
Gpprefcl.dll	6.1.7601.22374	1,519,104	02-Jul-2013	04:13	IA-64
Gpprefcl.dll	6.1.7601.22374	589,312	02-Jul-2013	05:05	x86

↑ Back to the top

Status

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

↑ Back to the top

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 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name	X86_e0bc3351853b34fc737dec7423f59e50_31bf3856ad364e35_6.1.7601.22374_none_c3c9937d2330e775.manifest
File version	Not applicable
File size	711
Date (UTC)	02-Jul-2013
Time (UTC)	11:33
Platform	Not applicable

File name	X86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22374_none_39993fa7c08c7689.manifest
File version	Not applicable
File size	53,968
Date (UTC)	02-Jul-2013
Time (UTC)	05:50
Platform	Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name	Amd64_a7bd5218f701d98c2f7705b1c2dacd60_31bf3856ad364e35_6.1.7601.22374_none_ec5d90a3e01c52a1.manifest
File version	Not applicable
File size	715
Date (UTC)	02-Jul-2013
Time (UTC)	11:33
Platform	Not applicable

File name	Amd64_d278541e78070bcc22f01e5f296feb96_31bf3856ad364e35_6.1.7601.22374_none_d9248257ad5aedec.manifest
File version	Not applicable
File size	715
Date (UTC)	02-Jul-2013
Time (UTC)	11:33
Platform	Not applicable

File name	Amd64_dacc5540c0b6c02e4b7a68514512444f_31bf3856ad364e35_6.1.7601.22374_none_1edc2e1a6e85ef04.manifest
File version	Not applicable
File size	1,070
Date (UTC)	02-Jul-2013
Time (UTC)	11:33
Platform	Not applicable

File name	Amd64_e0bc3351853b34fc737dec7423f59e50_31bf3856ad364e35_6.1.7601.22374_none_1fe82f00db8e58ab.manifest
File version	Not applicable
File size	713
Date (UTC)	02-Jul-2013
Time (UTC)	11:33
Platform	Not applicable

File name	Amd64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22374_none_95b7db2b78e9e7bf.manifest
File version	Not applicable
File size	53,972
Date (UTC)	02-Jul-2013
Time (UTC)	05:48
Platform	Not applicable

File name	Wow64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22374_none_a00c857dad4aa9ba.manifest
File version	Not applicable
File size	34,836
Date (UTC)	02-Jul-2013
Time (UTC)	05:24
Platform	Not applicable

File name	X86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22374_none_39993fa7c08c7689.manifest
File version	Not applicable
File size	53,968
Date (UTC)	02-Jul-2013
Time (UTC)	05:50
Platform	Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name	Ia64_f357a098e10789e2241fdc0d580e2aa3_31bf3856ad364e35_6.1.7601.22374_none_1b95501db7a5750d.manifest
File version	Not applicable
File size	1,068
Date (UTC)	02-Jul-2013
Time (UTC)	11:33
Platform	Not applicable

File name	Ia64_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22374_none_399ae39dc08a7f85.manifest
File version	Not applicable
File size	53,970
Date (UTC)	02-Jul-2013
Time (UTC)	05:25
Platform	Not applicable

File name	X86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.22374_none_39993fa7c08c7689.manifest
File version	Not applicable
File size	53,968
Date (UTC)	02-Jul-2013
Time (UTC)	05:50
Platform	Not applicable

↑ Back to the top

Article ID	:	2867625
Revision	:	1
Created on	:	1/7/2017
Published on	:	7/10/2014
Exists online	:	False
Views	:	224

Microsoft KB Archive Search

TCP port exhaustion causes key operations to fail when you deploy Group Policy preferences in Windows 7 SP1 or Windows Server 2008 R2 SP1

Symptoms

Cause

Resolution

Hotfix information

Prerequisites

Registry information

Restart requirement

Hotfix replacement information

Windows 7 and Windows Server 2008 R2 file information notes

For all supported x86-based versions of Windows 7

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

For all supported IA-64-based versions of Windows Server 2008 R2

Status

More Information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

Applies to: