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.

Network connectivity is lost when you install or upgrade to version 21.0 of a certain Norton product in Windows 8 or Windows Server 2012


View products that this article applies to.

Symptoms

When you install or upgrade to version 21.0 of a certain Norton product on a Windows 8-based or Windows Server 2012-based computer, network connectivity is lost.

Note The following Norton products are affected by this issue:
  • Norton Antivirus version 21.0
  • Norton Internet Security version 21.0
  • Norton 360 version 21.0

↑ Back to the top


Cause

This issue is caused by an interaction between Network Driver Interface Specification (NDIS) drivers that are installed by certain third-party lightweight and intermediate software and the Windows Filtering Platform (WFP) Layer 2 filters.

↑ 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 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 8 or 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.
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 8 and Windows Server 2012 file information notes
Important Windows 8 hotfixes 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.16 xxxWindows 8 and Windows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows 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 for Windows 8 and Windows Server 2012" 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
Bfe.dll6.2.9200.16745473,60019-Oct-201304:03x86
Fwpuclnt.dll6.2.9200.16634245,24810-Jun-201319:10x86
Ikeext.dll6.2.9200.16745683,52019-Oct-201304:04x86
Networksecurity-ppdlic.xrm-msNot applicable2,92019-Oct-201305:10Not applicable
Nshwfp.dll6.2.9200.16634702,46410-Jun-201319:10x86
Wfplwfs.sys6.2.9200.1674538,73619-Oct-201304:44x86
Bfe.dll6.2.9200.20741473,60011-Jun-201300:15x86
Fwpuclnt.dll6.2.9200.20569245,24827-Nov-201204:22x86
Ikeext.dll6.2.9200.20856683,52019-Oct-201306:08x86
Networksecurity-ppdlic.xrm-msNot applicable2,92019-Oct-201307:00Not applicable
Nshwfp.dll6.2.9200.20856702,46419-Oct-201306:09x86
Wfplwfs.sys6.2.9200.2085638,74419-Oct-201306:56x86
For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.2.9200.16745723,96819-Oct-201305:45x64
Fwpuclnt.dll6.2.9200.16634381,95210-Jun-201319:15x64
Ikeext.dll6.2.9200.167451,160,19219-Oct-201305:45x64
Networksecurity-ppdlic.xrm-msNot applicable2,92019-Oct-201306:42Not applicable
Nshwfp.dll6.2.9200.16634888,83210-Jun-201319:16x64
Wfplwfs.sys6.2.9200.1674596,60019-Oct-201306:56x64
Bfe.dll6.2.9200.20741718,84811-Jun-201306:17x64
Fwpuclnt.dll6.2.9200.20569378,88027-Nov-201204:25x64
Ikeext.dll6.2.9200.208561,074,68819-Oct-201306:34x64
Networksecurity-ppdlic.xrm-msNot applicable2,92019-Oct-201309:22Not applicable
Nshwfp.dll6.2.9200.20856888,83219-Oct-201306:35x64
Wfplwfs.sys6.2.9200.2085696,60019-Oct-201309:28x64
Fwpuclnt.dll6.2.9200.16634245,24810-Jun-201319:10x86
Nshwfp.dll6.2.9200.16634702,46410-Jun-201319:10x86
Fwpuclnt.dll6.2.9200.20569245,24827-Nov-201204:22x86
Nshwfp.dll6.2.9200.20856702,46419-Oct-201306:09x86


↑ 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
Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.


Additional file information

Additional file information for Windows 8 and Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File propertyValue
File nameX86_22a1793eb7f4f06b6c9a46f2e0c32445_31bf3856ad364e35_6.2.9200.16745_none_0f61f35718bc0d53.manifest
File versionNot applicable
File size704
Date (UTC)21-Oct-2013
Time (UTC)17:27
File nameX86_aaf9099e205548beb49cf2f26fefca6c_31bf3856ad364e35_6.2.9200.20856_none_c68b4f39e2fcb18e.manifest
File versionNot applicable
File size704
Date (UTC)21-Oct-2013
Time (UTC)17:27
File nameX86_microsoft-windows-network-security_31bf3856ad364e35_6.2.9200.16745_none_c9fbc35bfbd03af9.manifest
File versionNot applicable
File size93,475
Date (UTC)21-Oct-2013
Time (UTC)17:27
File nameX86_microsoft-windows-network-security_31bf3856ad364e35_6.2.9200.20856_none_ca7b908514f5100b.manifest
File versionNot applicable
File size93,475
Date (UTC)21-Oct-2013
Time (UTC)17:27
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File propertyValue
File nameAmd64_22a578e24507f89440acc72ece96e654_31bf3856ad364e35_6.2.9200.16745_none_09788ed8d67c7c1a.manifest
File versionNot applicable
File size1,058
Date (UTC)21-Oct-2013
Time (UTC)17:32
File nameAmd64_618eeb3a351795ff5800b5135f50eaa9_31bf3856ad364e35_6.2.9200.20856_none_6d509ea0492c807c.manifest
File versionNot applicable
File size1,058
Date (UTC)21-Oct-2013
Time (UTC)17:32
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.2.9200.16745_none_261a5edfb42dac2f.manifest
File versionNot applicable
File size93,718
Date (UTC)21-Oct-2013
Time (UTC)17:32
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.2.9200.20856_none_269a2c08cd528141.manifest
File versionNot applicable
File size93,718
Date (UTC)21-Oct-2013
Time (UTC)17:32
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.2.9200.16745_none_306f0931e88e6e2a.manifest
File versionNot applicable
File size16,196
Date (UTC)21-Oct-2013
Time (UTC)17:32
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.2.9200.20856_none_30eed65b01b3433c.manifest
File versionNot applicable
File size16,196
Date (UTC)21-Oct-2013
Time (UTC)17:32

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2901834
Revision : 1
Created on : 1/7/2017
Published on : 12/13/2013
Exists online : False
Views : 172