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. Windows Server 2012 R2-based Hyper-V server crashes when network traffic passes through a virtual switch

Windows Server 2012 R2-based Hyper-V server crashes when network traffic passes through a virtual switch

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have the Hyper-V server role installed on a computer that is running Windows Server 2012 R2.
  • You create a switch team over a physical network adapter.
    Note The virtual machine queue (VMQ) is enabled on the network adapter.
  • You create a virtual switch over the switch team.
    Note There is no forward extension present.
  • Network traffic passes through the virtual switch.
In this scenario, the computer crashes, and data loss occurs.

↑ 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:
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, you must be running Windows Server 2012 R2.

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 Server 2012 R2 file information notes
Important Windows 8.1 hotfixes 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.16 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.1638462,46422-Aug-201309:34x64
Vmsnetsetupplugin.dll6.3.9600.1638433,79222-Aug-201309:52x64
Vmswitch.sys6.3.9600.16475686,08024-Nov-201323:47x64
Vmsif.dll6.3.9600.1638462,46422-Aug-201309:34x64
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.3.9600.16475686,08024-Nov-201323:47x64
Mslbfoprovider.sys6.3.9600.16423115,71208-Oct-201307:38x64
Wnv.sys6.3.9600.16474705,02423-Nov-201307:08x64
Wnvapi.dll6.3.9600.1638461,95222-Aug-201309:53x64
Vmsif.dll6.3.9600.1638462,46422-Aug-201309:34x64
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.3.9600.16475686,08024-Nov-201323:47x64
Vmsif.dll6.3.9600.1638462,46422-Aug-201309:34x64
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.3.9600.16475686,08024-Nov-201323:47x64

↑ 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
Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_3c5bd115312b4309869c6e4c33c94db3_31bf3856ad364e35_6.3.9600.16475_none_4ed8e453de0a8793.manifest
File versionNot applicable
File size708
Date (UTC)26-Nov-2013
Time (UTC)05:28
File nameAmd64_48b3b4cc6f7d336aa60cf10ca4c48569_31bf3856ad364e35_6.3.9600.16475_none_d1f0a8fa8cfba289.manifest
File versionNot applicable
File size695
Date (UTC)26-Nov-2013
Time (UTC)05:28
File nameAmd64_8a9fe2e875e43663d2294d0a6792c2a1_31bf3856ad364e35_6.3.9600.16475_none_7cce0a3ad08c39b2.manifest
File versionNot applicable
File size725
Date (UTC)26-Nov-2013
Time (UTC)05:28
File nameAmd64_aa7fdffd35cc6cc6529fe1b2cb0daede_31bf3856ad364e35_6.3.9600.16475_none_a502d2b7d0c6947f.manifest
File versionNot applicable
File size701
Date (UTC)26-Nov-2013
Time (UTC)05:28
File nameAmd64_microsoft-hyper-v-d..ch-coresystem-state_31bf3856ad364e35_6.3.9600.16475_none_e85ff43843871c41.manifest
File versionNot applicable
File size10,075
Date (UTC)26-Nov-2013
Time (UTC)05:28
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.16475_none_59d56baa540ae972.manifest
File versionNot applicable
File size7,637
Date (UTC)26-Nov-2013
Time (UTC)05:28
File nameAmd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.16475_none_022e32cbeabed6f9.manifest
File versionNot applicable
File size21,660
Date (UTC)26-Nov-2013
Time (UTC)05:28
File nameAmd64_microsoft-windows-wnv_31bf3856ad364e35_6.3.9600.16475_none_a07048c52ab22ee2.manifest
File versionNot applicable
File size54,090
Date (UTC)26-Nov-2013
Time (UTC)05:28
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.16475_none_53afc584c5506266.manifest
File versionNot applicable
File size3,379
Date (UTC)26-Nov-2013
Time (UTC)05:28
File nameAmd64_wvms_pp_coresys.inf_31bf3856ad364e35_6.3.9600.16475_none_622dd8c7603f7295.manifest
File versionNot applicable
File size3,411
Date (UTC)26-Nov-2013
Time (UTC)05:29

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2913659
Revision : 1
Created on : 1/7/2017
Published on : 1/15/2014
Exists online : False
Views : 203