Applies ToWindows Server 2012 R2 Datacenter Windows Server 2012 R2 Standard Windows Server 2012 R2 Essentials Windows Server 2012 R2 Foundation Windows 8.1 Enterprise Windows 8.1 Pro Windows 8.1 Windows Server 2012 Datacenter Windows Server 2012 Datacenter Windows Server 2012 Standard Windows Server 2012 Standard Windows Server 2012 Essentials Windows Server 2012 Foundation Windows Server 2012 Foundation Windows 8 Enterprise Windows 8 Pro Windows 8

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.

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=supportNote 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.

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 notesImportant 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.

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17xxx

    Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

    RTM

    GDR

  • 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 name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.3.9600.17336

286,528

08-Sep-2014

02:33

x86

Tcpip.sys

6.3.9600.17336

1,858,368

08-Sep-2014

02:33

x86

For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.3.9600.17336

428,864

08-Sep-2014

03:07

x64

Tcpip.sys

6.3.9600.17336

2,497,344

08-Sep-2014

03:07

x64

For all supported ARM-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.3.9600.17336

278,864

08-Sep-2014

01:20

Not applicable

Tcpip.sys

6.3.9600.17336

1,767,248

08-Sep-2014

01:20

Not applicable

Windows 8 and Windows Server 2012 file information and notesImportant 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.

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.16xxx

    Windows RT, Windows 8, and Windows Server 2012

    RTM

    GDR

    6.2.920 0.17xxx

    Windows RT, Windows 8, and Windows Server 2012

    RTM

    LDR

    6.2.920 0.21xxx

    Windows 8 and Windows Server 2012

    RTM

    LDR

  • 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 name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.2.9200.16548

271,080

02-Mar-2013

09:21

x86

Tcpip.sys

6.2.9200.17121

1,799,488

13-Sep-2014

04:40

x86

Fwpkclnt.sys

6.2.9200.16384

271,088

26-Jul-2012

03:30

x86

Tcpip.sys

6.2.9200.21237

1,814,848

13-Sep-2014

16:12

x86

For all supported x64-based versions of Windows 8 and of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.2.9200.16547

411,880

02-Mar-2013

09:59

x64

Tcpip.sys

6.2.9200.17121

2,233,152

13-Sep-2014

06:24

x64

Fwpkclnt.sys

6.2.9200.16384

411,888

26-Jul-2012

04:43

x64

Tcpip.sys

6.2.9200.21237

2,231,616

13-Sep-2014

18:36

x64

For all supported ARM-based versions of Windows 8

File name

File version

File size

Date

Time

Platform

Fwpkclnt.sys

6.2.9200.16420

273,640

20-Sep-2012

08:03

Not applicable

Tcpip.sys

6.2.9200.17121

1,691,968

13-Sep-2014

03:59

Not applicable

Additional file information for Windows 8.1

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

File property

Value

File name

X86_c6f8ba4121bbdd199081875f06b631b3_31bf3856ad364e35_6.3.9600.17336_none_71edf8fadc891bf0.manifest

File version

Not applicable

File size

702

Date (UTC)

09-Sep-2014

Time (UTC)

04:24

File name

X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.3.9600.17336_none_47f5d04181d596ce.manifest

File version

Not applicable

File size

3,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 property

Value

File name

Amd64_338deaa5aa1bb9e6db4eb329fb4a5055_31bf3856ad364e35_6.3.9600.17336_none_b97d347194b9d40f.manifest

File version

Not applicable

File size

706

Date (UTC)

09-Sep-2014

Time (UTC)

04:26

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.3.9600.17336_none_a4146bc53a330804.manifest

File version

Not applicable

File size

3,884

Date (UTC)

08-Sep-2014

Time (UTC)

03:11

Additional files for all supported ARM-based versions of Windows 8.1

File property

Value

File name

Arm_64b8ee357ba1dee5185548d2c2ec0126_31bf3856ad364e35_6.3.9600.17336_none_9be1972c72d4f3c8.manifest

File version

Not applicable

File size

702

Date (UTC)

09-Sep-2014

Time (UTC)

04:25

File name

Arm_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.3.9600.17336_none_47f8429981d2b594.manifest

File version

Not applicable

File size

3,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 property

Value

File name

X86_221a1f728cdf134079412036154dea0b_31bf3856ad364e35_6.2.9200.17121_none_e2563dbf59d7d251.manifest

File version

Not applicable

File size

702

Date (UTC)

13-Sep-2014

Time (UTC)

22:39

File name

X86_cb8e288c73450bd0a7d53a6e8d783fc7_31bf3856ad364e35_6.2.9200.21237_none_6bcfa78d25a359a7.manifest

File version

Not applicable

File size

702

Date (UTC)

13-Sep-2014

Time (UTC)

22:39

File name

X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.17121_none_b006e249379f315f.manifest

File version

Not applicable

File size

3,883

Date (UTC)

13-Sep-2014

Time (UTC)

22:39

File name

X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.21237_none_b08bb0e450bf8524.manifest

File version

Not applicable

File size

3,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 property

Value

File name

Amd64_63ea3518c18670b61aaa8394e24c2793_31bf3856ad364e35_6.2.9200.17121_none_64a7896e2006a1e4.manifest

File version

Not applicable

File size

706

Date (UTC)

13-Sep-2014

Time (UTC)

22:40

File name

Amd64_a83262d95244e43c6be39420cbe38a91_31bf3856ad364e35_6.2.9200.21237_none_ac39b2b01a17f97f.manifest

File version

Not applicable

File size

706

Date (UTC)

13-Sep-2014

Time (UTC)

22:40

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.17121_none_0c257dcceffca295.manifest

File version

Not applicable

File size

3,887

Date (UTC)

13-Sep-2014

Time (UTC)

22:40

File name

Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.21237_none_0caa4c68091cf65a.manifest

File version

Not applicable

File size

3,887

Date (UTC)

13-Sep-2014

Time (UTC)

22:40

Additional files for all supported ARM-based versions of Windows 8

File property

Value

File name

Arm_8df0be4af55e1aacb7991a3db9bd9ae8_31bf3856ad364e35_6.2.9200.17121_none_5778297715b50c55.manifest

File version

Not applicable

File size

702

Date (UTC)

13-Sep-2014

Time (UTC)

22:38

File name

Arm_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.2.9200.17121_none_b00954a1379c5025.manifest

File version

Not applicable

File size

3,883

Date (UTC)

13-Sep-2014

Time (UTC)

22:38

Status

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

References

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

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.