Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

An application may stop responding when the application closes a socket connection or shuts down


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows 7,  Windows Server 2008 R2, Windows Server 2008, or Windows Vista.
  • You have an application that calls the WSASocket function to create sockets and that calls the SetHandleInformation function to set the socket attribute on the computer.
  • The application also creates child processes.
  • The application closes a socket connection or shuts down.
In this scenario, the application may stop responding.

↑ Back to the top


Cause

This issue occurs because the child process does not release the handle for a long time.

By default, socket handles are inheritable. When a child process is created, the child process inherits the socket handle from the parent process. When the parent process tries to close the socket, it waits until the child process releases the handle. However, the child process does not release the handle for a long time. Therefore, the application stops responding. 

↑ Back to the top


Resolution

Windows 7 and Windows Server 2007 R2: The fix for this issue was first included in Service Pack 1 for Windows Server 2008 R2. You can download this service pack from the following Microsoft website:

The following hotfix introduces a new WSA_FLAG_NO_HANDLE_INHERIT flag for the WSASocket function to specify whether to inherit the socket handle.

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: 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 one of the following operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:

935791 How to obtain the latest Windows Vista service pack

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

968849 How to obtain the latest service pack for Windows Server 2008

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.

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 Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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.
    VersionProductSR_LevelService branch
    6.0.600
    1.
    22xxx
    Windows Vista and Windows Server 2008SP1LDR
    6.0.600
    2.
    22xxx
    Windows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • 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 Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are very important for 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.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatformService branch
Mswsock.dll6.0.6001.22755223,23201-Sep-201019:24x86X86_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6001.22755_NONE_B8ABF10B468D57AA
Mswsock.dll6.0.6002.22479223,23201-Sep-201021:06x86X86_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6002.22479_NONE_BA80C44343C04A0C
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatformService branch
Mswsock.dll6.0.6001.22755304,12801-Sep-201019:50x64AMD64_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6001.22755_NONE_14CA8C8EFEEAC8E0
Mswsock.dll6.0.6002.22479304,12801-Sep-201020:26x64AMD64_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6002.22479_NONE_169F5FC6FC1DBB42
Mswsock.dll6.0.6001.22755223,23201-Sep-201019:24x86X86_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6001.22755_NONE_B8ABF10B468D57AA
Mswsock.dll6.0.6002.22479223,23201-Sep-201021:06x86X86_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6002.22479_NONE_BA80C44343C04A0C
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatformService branch
Mswsock.dll6.0.6001.22755710,65601-Sep-201019:26IA-64IA64_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6001.22755_NONE_B8AD9501468B60A6
Mswsock.dll6.0.6002.22479710,65601-Sep-201020:37IA-64IA64_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6002.22479_NONE_BA82683943BE5308
Mswsock.dll6.0.6001.22755223,23201-Sep-201019:24x86X86_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6001.22755_NONE_B8ABF10B468D57AA
Mswsock.dll6.0.6002.22479223,23201-Sep-201021:06x86X86_MICROSOFT-WINDOWS-W..-INFRASTRUCTURE-BSP_31BF3856AD364E35_6.0.6002.22479_NONE_BA80C44343C04A0C

↑ 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 the WSASocket function, visit the following Microsoft website:For more information about the SetHandleInformation function, visit the following Microsoft website:For more information about the CreateProcess function, visit the following Microsoft website:For more information about the closesocket function, visit the following Microsoft website: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 Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameUpdate.mum
File versionNot applicable
File size3,577
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameX86_c2380966ccbdcbf3264293a78b8f57a3_31bf3856ad364e35_6.0.6001.22755_none_2266dd51e7696d00.manifest
File versionNot applicable
File size719
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameX86_fb6890ba4dc2b20e0eee942dbc1213b9_31bf3856ad364e35_6.0.6002.22479_none_d31eb0f3e5a25546.manifest
File versionNot applicable
File size719
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameX86_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6001.22755_none_b8abf10b468d57aa.manifest
File versionNot applicable
File size6,759
Date (UTC)01-Sep-2010
Time (UTC)19:41
PlatformNot applicable
File nameX86_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6002.22479_none_ba80c44343c04a0c.manifest
File versionNot applicable
File size6,759
Date (UTC)01-Sep-2010
Time (UTC)21:27
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_3a56df4bff5eefa45859cf0099cfc5ae_31bf3856ad364e35_6.0.6001.22755_none_8d29a8985cdbea11.manifest
File versionNot applicable
File size723
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameAmd64_bf8816280a301c699a8f8203c4190e17_31bf3856ad364e35_6.0.6001.22755_none_9fcb2725b847333c.manifest
File versionNot applicable
File size1,086
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameAmd64_c53f614436b68b52749ee20d20cb3435_31bf3856ad364e35_6.0.6002.22479_none_d4f2dca3963de973.manifest
File versionNot applicable
File size1,086
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameAmd64_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6001.22755_none_14ca8c8efeeac8e0.manifest
File versionNot applicable
File size6,783
Date (UTC)01-Sep-2010
Time (UTC)20:10
PlatformNot applicable
File nameAmd64_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6002.22479_none_169f5fc6fc1dbb42.manifest
File versionNot applicable
File size6,783
Date (UTC)01-Sep-2010
Time (UTC)20:46
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,605
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameX86_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6001.22755_none_b8abf10b468d57aa.manifest
File versionNot applicable
File size6,759
Date (UTC)01-Sep-2010
Time (UTC)19:41
PlatformNot applicable
File nameX86_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6002.22479_none_ba80c44343c04a0c.manifest
File versionNot applicable
File size6,759
Date (UTC)01-Sep-2010
Time (UTC)21:27
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_19a703e0e85c6dc3d4f6817e1a36a3bd_31bf3856ad364e35_6.0.6002.22479_none_549e6a19dd10210a.manifest
File versionNot applicable
File size1,084
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameIa64_53757a883c48ae1b549cbf717db16dcf_31bf3856ad364e35_6.0.6001.22755_none_e9c62c6836e81204.manifest
File versionNot applicable
File size1,084
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameIa64_da9456f4135fedc07df726979373e0b5_31bf3856ad364e35_6.0.6001.22755_none_94f7bb42e01b6ed7.manifest
File versionNot applicable
File size721
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameIa64_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6001.22755_none_b8ad9501468b60a6.manifest
File versionNot applicable
File size6,771
Date (UTC)01-Sep-2010
Time (UTC)19:42
PlatformNot applicable
File nameIa64_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6002.22479_none_ba82683943be5308.manifest
File versionNot applicable
File size6,771
Date (UTC)01-Sep-2010
Time (UTC)20:52
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,758
Date (UTC)02-Sep-2010
Time (UTC)06:56
PlatformNot applicable
File nameX86_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6001.22755_none_b8abf10b468d57aa.manifest
File versionNot applicable
File size6,759
Date (UTC)01-Sep-2010
Time (UTC)19:41
PlatformNot applicable
File nameX86_microsoft-windows-w..-infrastructure-bsp_31bf3856ad364e35_6.0.6002.22479_none_ba80c44343c04a0c.manifest
File versionNot applicable
File size6,759
Date (UTC)01-Sep-2010
Time (UTC)21:27
PlatformNot applicable

↑ Back to the top


Keywords: kbqfe, kbhotfixserver, kbfix, kbexpertiseadvanced, kbsurveynew, kb, kbautohotfix

↑ Back to the top

Article Info
Article ID : 2398202
Revision : 3
Created on : 4/9/2020
Published on : 4/9/2020
Exists online : False
Views : 144