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. Cluster nodes or VMs go offline when they are using VMQ capable NICs on a Windows Server 2012 R2 host

Cluster nodes or VMs go offline when they are using VMQ capable NICs on a Windows Server 2012 R2 host

View products that this article applies to.

This article describes an issue in which all virtual machines (VM) go into failed state on a Windows Server 2012 R2 host and may not be migrated automatically to other cluster nodes. An update is available to fix this issue. Before you install this update, see the Prerequisites section.

↑ Back to the top

Symptoms

This issue occurs when Hyper-V cluster hosts use virtual machine queue (VMQ) capable NICs (high performance NICs) and when the VMQ feature is enabled. All VMs on the hosts would go into failed state instead of failing over to other nodes.

↑ Back to the top

How to get this update

Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.

Method 1: Windows Update

This update is provided as a Recommended update on Windows Update. For more information on how to run Windows Update, see How to get an update through Windows Update.

Method 2: Microsoft Update Catalog

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.

↑ Back to the top

Update detail information

Prerequisites

To install this update, you should first install April 2014, update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) in Windows Server 2012 R2.

Registry information

To apply this update, you don't have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this update.

Update replacement information

This update doesn't replace a previously released update.

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

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.

↑ Back to the top

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables.
Windows Server 2012 R2
Notes
  • 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
    6.3.960 0.18 xxxWindows Server 2012 R2RTMGDR
  • 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 in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.
x64 Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Msft_netlbfoteam.cdxmlNot applicable7,06918-Jun-201314:54Not applicable
Msft_netlbfoteam.format.ps1xmlNot applicable2,97318-Jun-201314:54Not applicable
Msft_netlbfoteammember.cdxmlNot applicable5,76418-Jun-201314:54Not applicable
Msft_netlbfoteammember.format.ps1xmlNot applicable4,78918-Jun-201314:54Not applicable
Msft_netlbfoteamnic.cdxmlNot applicable4,82418-Jun-201314:54Not applicable
Msft_netlbfoteamnic.format.ps1xmlNot applicable4,72018-Jun-201314:54Not applicable
Msft_netswitchteam.cdxmlNot applicable5,83418-Jun-201314:53Not applicable
Msft_netswitchteam.format.ps1xmlNot applicable2,42818-Jun-201314:53Not applicable
Msft_netswitchteammember.cdxmlNot applicable1,23418-Jun-201314:53Not applicable
Msft_netswitchteammember.format.ps1xmlNot applicable3,38018-Jun-201314:53Not applicable
Msnetimplatform.mofNot applicable43,63822-Aug-201306:50Not applicable
Ndisimplatcim.dll6.3.9600.18258202,75203-Mar-201618:03x64
Ndisimplatform.dll6.3.9600.17415119,80829-Oct-201402:26x64
Ndisimplatform.sys6.3.9600.18258126,46403-Mar-201618:24x64
Netlbfo.psd1Not applicable1,07418-Jun-201314:54Not applicable
Netlbfo.types.ps1xmlNot applicable8,54718-Jun-201314:54Not applicable
Netswitchteam.mofNot applicable28,33822-Aug-201306:50Not applicable
Netswitchteam.psd1Not applicable1,05618-Jun-201314:53Not applicable
Netswitchteamcim.dll6.3.9600.17415143,36029-Oct-201402:26x64
Mslbfoprovider.sys6.3.9600.18258117,24803-Mar-201618:25x64
Msft_netlbfoteam.cdxmlNot applicable7,06918-Jun-201312:26Not applicable
Msft_netlbfoteam.format.ps1xmlNot applicable2,97318-Jun-201312:26Not applicable
Msft_netlbfoteammember.cdxmlNot applicable5,76418-Jun-201312:26Not applicable
Msft_netlbfoteammember.format.ps1xmlNot applicable4,78918-Jun-201312:26Not applicable
Msft_netlbfoteamnic.cdxmlNot applicable4,82418-Jun-201312:26Not applicable
Msft_netlbfoteamnic.format.ps1xmlNot applicable4,72018-Jun-201312:26Not applicable
Msft_netswitchteam.cdxmlNot applicable5,83418-Jun-201312:26Not applicable
Msft_netswitchteam.format.ps1xmlNot applicable2,42818-Jun-201312:26Not applicable
Msft_netswitchteammember.cdxmlNot applicable1,23418-Jun-201312:26Not applicable
Msft_netswitchteammember.format.ps1xmlNot applicable3,38018-Jun-201312:26Not applicable
Netlbfo.psd1Not applicable1,07418-Jun-201312:26Not applicable
Netlbfo.types.ps1xmlNot applicable8,54718-Jun-201312:26Not applicable
Netswitchteam.psd1Not applicable1,05618-Jun-201312:26Not applicable
Additional file information
x64 Windows Server 2012 R2
File propertyValue
File nameAmd64_26c4f89eeae5f7feb8074bf29b899152_31bf3856ad364e35_6.3.9600.18259_none_bdbb0d11502fe9f7.manifest
File versionNot applicable
File size707
Date (UTC)04-Mar-2016
Time (UTC)21:53
PlatformNot applicable
File nameAmd64_cd8068557c5605ccb4ae789c87137b3b_31bf3856ad364e35_6.3.9600.18259_none_1b7eef7d4fab9441.manifest
File versionNot applicable
File size707
Date (UTC)04-Mar-2016
Time (UTC)21:53
PlatformNot applicable
File nameAmd64_e818767e11e68b25884dc52f63320d7e_31bf3856ad364e35_6.3.9600.18259_none_3da7b741c607cfcd.manifest
File versionNot applicable
File size701
Date (UTC)04-Mar-2016
Time (UTC)21:53
PlatformNot applicable
File nameAmd64_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.18259_none_46cecf5517b968a5.manifest
File versionNot applicable
File size48,034
Date (UTC)04-Mar-2016
Time (UTC)22:02
PlatformNot applicable
File nameAmd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.18259_none_0247a26feaab3d67.manifest
File versionNot applicable
File size21,621
Date (UTC)04-Mar-2016
Time (UTC)15:54
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,285
Date (UTC)04-Mar-2016
Time (UTC)21:53
PlatformNot applicable
File nameWow64_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.18259_none_512379a74c1a2aa0.manifest
File versionNot applicable
File size20,681
Date (UTC)04-Mar-2016
Time (UTC)15:43
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbsurveynew, atdownload, kbexpertiseadvanced, kbfix

↑ Back to the top

Article Info
Article ID : 3145432
Revision : 1
Created on : 1/7/2017
Published on : 5/10/2016
Exists online : False
Views : 270