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.

A third-party switch extension to the Microsoft VM switch cannot be disabled on Windows Server 2012 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Hyper-V host that is running on Windows Server 2012 R2.
  • You install a third-party switch extension to the Microsoft VM switch.

In this scenario, the VM switch internal counters are nonzero. This prevents the disabling of the third-party switch extension.

↑ 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: 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 update, you must first have update 2919355 installed in Windows Server 2012 R2.

Restart requirement

You do not have to 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 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.17 xxxWindows 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 for Windows Server 2012 R2" 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 x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Vmsif.dll6.3.9600.1748165,02405-Nov-201401:20x64
Vmsnetsetupplugin.dll6.3.9600.1748133,79205-Nov-201401:34x64
Vmswitch.sys6.3.9600.17481688,64005-Nov-201402:59x64
Vmsif.dll6.3.9600.1748165,02405-Nov-201401:20x64
Vmsntfy.dll6.3.9600.1748191,64805-Nov-201402:21x64
Vmswitch.sys6.3.9600.17481688,64005-Nov-201402:59x64
Mslbfoprovider.sys6.3.9600.17481115,71205-Nov-201403:00x64
Wnv.sys6.3.9600.17481704,00005-Nov-201402:59x64
Wnvapi.dll6.3.9600.1748164,51205-Nov-201401:35x64
Vmsif.dll6.3.9600.1748165,02405-Nov-201401:20x64
Vmsntfy.dll6.3.9600.1748191,64805-Nov-201402:21x64
Vmswitch.sys6.3.9600.17481688,64005-Nov-201402:59x64
Vmsif.dll6.3.9600.1748165,02405-Nov-201401:20x64
Vmsntfy.dll6.3.9600.1748191,64805-Nov-201402:21x64
Vmswitch.sys6.3.9600.17481688,64005-Nov-201402:59x64

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_8e9272370522b6f6009d04be8dc3f4cb_31bf3856ad364e35_6.3.9600.17481_none_d6aef621813b8477.manifest
File versionNot applicable
File size695
Date (UTC)05-Nov-2014
Time (UTC)21:42
PlatformNot applicable
File nameAmd64_d6a14bc09cec3564a344af73db7ff68e_31bf3856ad364e35_6.3.9600.17481_none_cd09b61c96116e9a.manifest
File versionNot applicable
File size701
Date (UTC)05-Nov-2014
Time (UTC)21:42
PlatformNot applicable
File nameAmd64_d8224a451c37591913fa0db1249d922d_31bf3856ad364e35_6.3.9600.17481_none_3a584f3c0fe868ee.manifest
File versionNot applicable
File size725
Date (UTC)05-Nov-2014
Time (UTC)21:42
PlatformNot applicable
File nameAmd64_f0601ce6c2bb049b67973b033a9be0fe_31bf3856ad364e35_6.3.9600.17481_none_aa61c217dbf44f4d.manifest
File versionNot applicable
File size708
Date (UTC)05-Nov-2014
Time (UTC)21:42
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-d..ch-coresystem-state_31bf3856ad364e35_6.3.9600.17481_none_e8510c5c4392ec77.manifest
File versionNot applicable
File size10,072
Date (UTC)05-Nov-2014
Time (UTC)04:01
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.17481_none_59c683ce5416b9a8.manifest
File versionNot applicable
File size7,634
Date (UTC)05-Nov-2014
Time (UTC)04:01
PlatformNot applicable
File nameAmd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.17481_none_021f4aefeacaa72f.manifest
File versionNot applicable
File size21,645
Date (UTC)05-Nov-2014
Time (UTC)04:01
PlatformNot applicable
File nameAmd64_microsoft-windows-wnv_31bf3856ad364e35_6.3.9600.17481_none_a06160e92abdff18.manifest
File versionNot applicable
File size54,207
Date (UTC)05-Nov-2014
Time (UTC)04:01
PlatformNot applicable
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.17481_none_53a0dda8c55c329c.manifest
File versionNot applicable
File size3,376
Date (UTC)05-Nov-2014
Time (UTC)04:01
PlatformNot applicable
File nameAmd64_wvms_pp_coresys.inf_31bf3856ad364e35_6.3.9600.17481_none_621ef0eb604b42cb.manifest
File versionNot applicable
File size3,408
Date (UTC)05-Nov-2014
Time (UTC)04:01
PlatformNot applicable

↑ 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: kbbug, kbsurveynew, kbexpertiseinter, kbautohotfix, kbhotfixserver, kbqfe, kb, kbfix

↑ Back to the top

Article Info
Article ID : 3014795
Revision : 1
Created on : 1/7/2017
Published on : 12/9/2014
Exists online : False
Views : 189