Microsoft KB Archive Search

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.

  1. Home
  2. An application connection fails through a dual-use socket that is redirected by using a WFP callout driver

An application connection fails through a dual-use socket that is redirected by using a WFP callout driver

View products that this article applies to.

Symptoms

Assume that an application on a Windows 8.1 or Windows 8 client tries to connect through a dual-use socket (IPv4-mapped IPv6 address). If the connection is redirected by using a Windows Filtering Platform (WFP) callout driver, the connection fails.

Note Even though this issue has been observed only in Windows 8.1 and Windows 8, this hotfix also applies to Windows Server 2012 R2 and Windows Server 2012.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to 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 in Windows 8.1 or Windows Server 2012 R2, you must first have update 2919355 installed.

There are no prerequisites for installing this hotfix on Windows 8 and Windows Server 2012.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

File information
The English (United States) 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 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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 8.1" 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, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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 8.1
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.3.9600.17336286,52808-Sep-201402:33x86
Tcpip.sys6.3.9600.173361,858,36808-Sep-201402:33x86
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.3.9600.17336428,86408-Sep-201403:07x64
Tcpip.sys6.3.9600.173362,497,34408-Sep-201403:07x64
For all supported ARM-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.3.9600.17336278,86408-Sep-201401:20Not applicable
Tcpip.sys6.3.9600.173361,767,24808-Sep-201401:20Not applicable

Windows 8 and Windows Server 2012 file information and notes

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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 8" 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, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductMilestoneService branch
    6.2.920 0.16xxxWindows RT, Windows 8, and Windows Server 2012RTMGDR
    6.2.920 0.17xxxWindows RT, Windows 8, and Windows Server 2012RTMLDR
    6.2.920 0.21xxxWindows 8 and Windows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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 8
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.2.9200.16548271,08002-Mar-201309:21x86
Tcpip.sys6.2.9200.171211,799,48813-Sep-201404:40x86
Fwpkclnt.sys6.2.9200.16384271,08826-Jul-201203:30x86
Tcpip.sys6.2.9200.212371,814,84813-Sep-201416:12x86
For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.2.9200.16547411,88002-Mar-201309:59x64
Tcpip.sys6.2.9200.171212,233,15213-Sep-201406:24x64
Fwpkclnt.sys6.2.9200.16384411,88826-Jul-201204:43x64
Tcpip.sys6.2.9200.212372,231,61613-Sep-201418:36x64
For all supported ARM-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Fwpkclnt.sys6.2.9200.16420273,64020-Sep-201208:03Not applicable
Tcpip.sys6.2.9200.171211,691,96813-Sep-201403:59Not applicable

Additional file information for Windows 8.1

Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_c6f8ba4121bbdd199081875f06b631b3_31bf3856ad364e35_6.3.9600.17336_none_71edf8fadc891bf0.manifest
File versionNot applicable
File size702
Date (UTC)09-Sep-2014
Time (UTC)04:24
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.3.9600.17336_none_47f5d04181d596ce.manifest
File versionNot applicable
File size3,880
Date (UTC)08-Sep-2014
Time (UTC)02:37
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_338deaa5aa1bb9e6db4eb329fb4a5055_31bf3856ad364e35_6.3.9600.17336_none_b97d347194b9d40f.manifest
File versionNot applicable
File size706
Date (UTC)09-Sep-2014
Time (UTC)04:26
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.3.9600.17336_none_a4146bc53a330804.manifest
File versionNot applicable
File size3,884
Date (UTC)08-Sep-2014
Time (UTC)03:11
Additional files for all supported ARM-based versions of Windows 8.1
File propertyValue
File nameArm_64b8ee357ba1dee5185548d2c2ec0126_31bf3856ad364e35_6.3.9600.17336_none_9be1972c72d4f3c8.manifest
File versionNot applicable
File size702
Date (UTC)09-Sep-2014
Time (UTC)04:25
File nameArm_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.3.9600.17336_none_47f8429981d2b594.manifest
File versionNot applicable
File size3,880
Date (UTC)08-Sep-2014
Time (UTC)01:22

Additional file information for Windows 8

Additional files for all supported x86-based versions of Windows 8
File propertyValue
File nameX86_221a1f728cdf134079412036154dea0b_31bf3856ad364e35_6.2.9200.17121_none_e2563dbf59d7d251.manifest
File versionNot applicable
File size702
Date (UTC)13-Sep-2014
Time (UTC)22:39
File nameX86_cb8e288c73450bd0a7d53a6e8d783fc7_31bf3856ad364e35_6.2.9200.21237_none_6bcfa78d25a359a7.manifest
File versionNot applicable
File size702
Date (UTC)13-Sep-2014
Time (UTC)22:39
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.17121_none_b006e249379f315f.manifest
File versionNot applicable
File size3,883
Date (UTC)13-Sep-2014
Time (UTC)22:39
File nameX86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.21237_none_b08bb0e450bf8524.manifest
File versionNot applicable
File size3,883
Date (UTC)13-Sep-2014
Time (UTC)22:39
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File propertyValue
File nameAmd64_63ea3518c18670b61aaa8394e24c2793_31bf3856ad364e35_6.2.9200.17121_none_64a7896e2006a1e4.manifest
File versionNot applicable
File size706
Date (UTC)13-Sep-2014
Time (UTC)22:40
File nameAmd64_a83262d95244e43c6be39420cbe38a91_31bf3856ad364e35_6.2.9200.21237_none_ac39b2b01a17f97f.manifest
File versionNot applicable
File size706
Date (UTC)13-Sep-2014
Time (UTC)22:40
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.17121_none_0c257dcceffca295.manifest
File versionNot applicable
File size3,887
Date (UTC)13-Sep-2014
Time (UTC)22:40
File nameAmd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.21237_none_0caa4c68091cf65a.manifest
File versionNot applicable
File size3,887
Date (UTC)13-Sep-2014
Time (UTC)22:40
Additional files for all supported ARM-based versions of Windows 8
File propertyValue
File nameArm_8df0be4af55e1aacb7991a3db9bd9ae8_31bf3856ad364e35_6.2.9200.17121_none_5778297715b50c55.manifest
File versionNot applicable
File size702
Date (UTC)13-Sep-2014
Time (UTC)22:38
File nameArm_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.17121_none_b00954a1379c5025.manifest
File versionNot applicable
File size3,883
Date (UTC)13-Sep-2014
Time (UTC)22:38

↑ 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

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2999237
Revision : 1
Created on : 1/7/2017
Published on : 5/12/2015
Exists online : False
Views : 196