Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

This article describes an issue that occurs in a Windows 8.1 or Windows Server 2012 R2 Hyper-V host. A hotfix is available to resolve this issue. Before you install this hotfix, check out the Prerequisites section.

Introduction

Consider the following scenario:

  • You have a Windows Server 2012 R2-based computer that is configured for one or more NIC teams by using Windows NIC Teaming (LBFO).

  • You have implemented Windows NIC Teaming (LBFO) in Switch Independent teaming mode by using Hyper-V Port or Dynamic Load Balancing mode. Additionally, you have correctly configured the NICs to use non-overlapping processors. (For more information, see Knowledge Base article 2974384).

  • A Hyper-V virtual switch is bound to one of the LBFO teams.

  • You start a virtual machine on the Hyper-V server, or you live migrate a virtual machine from one server to another server.

In this scenario, you experience one or more of the following issues:

  • Issue 1: The following Error 113 event is logged intermittently in the event log:

    Log Name: System
    Source: Microsoft-Windows-Hyper-V-VmSwitch
    Date: <DateTime>
    Event ID: 113
    Task Category: None
    Level: Error
    Keywords:
    User: SYSTEM
    Computer: Server1.contoso.com
    Description:
    Failed to allocate VMQ for NIC EDCED345-4C96-4C75-92A0-0C4FC5688F73--35BEB899-5BE9-4128-900A-6FE0BBFC7B22
    (Friendly Name: Network Adapter) on switch DE4F3664-68D9-4781-825B-882A540FAB08 (Friendly Name: VM Switch).
    Reason - The OID failed. Status = {Operation Failed} The requested operation was unsuccessful. Additionally, the Hyper-V VmSwitch may fail to allocate VMQ queues for virtual machines.

    Note In the event description, the Reason text is always "The OID failed." The Status text varies based on the network adapter driver that is being used. Other Status examples include the following:

    • Status = An invalid parameter was passed to a service or function

    • Status = Insufficient system resources exist to complete the API

    • Status = Unknown

    Cause This issue occurs because the VmSwitch assumes that the default processor for VMQ is zero (0) when it performs VMQ allocation. This causes some network adapter drivers to reject the allocation and generate Error 113.

    Fix information After you apply this hotfix, the VmSwitch no longer assumes that the default processor for VMQ is zero (0).

    For more information about this issue, see Knowledge Base article 3001783.

  • Issue 2: Performance degrades or the system stops responding.

    Cause This issue occurs because LBFO physical resource mapping algorithm overloads the host. This issue can also trigger "MAC flapping."

    Fix information After you apply this hotfix, the rebalancing algorithm is optimized and made more scalable.

  • Issue 3: A STOP 0xD1 error occurs on the host during live migration.

    Cause This issue occurs after LBFO clears its own structures because it assumes that the forward progress of the Object identifier (OID) is guaranteed.

    Fix information After you apply this hotfix, LBFO clears its mappings only if the OID succeeds. For failure scenarios, LBFO passes the OID status back to VmSwitch. VmSwitch receives the failure status and processes it through its own logic.


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=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, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or 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 may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" 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.17 xxx

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

    RTM

    GDR

  • 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, 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.

For all supported x86-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Msft_netlbfoteam.cdxml

Not applicable

7,069

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteam.format.ps1xml

Not applicable

2,973

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteammember.cdxml

Not applicable

5,764

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteammember.format.ps1xml

Not applicable

4,789

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteamnic.cdxml

Not applicable

4,824

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteamnic.format.ps1xml

Not applicable

4,720

18-Jun-2013

12:26

Not applicable

Msft_netswitchteam.cdxml

Not applicable

5,834

18-Jun-2013

12:26

Not applicable

Msft_netswitchteam.format.ps1xml

Not applicable

2,428

18-Jun-2013

12:26

Not applicable

Msft_netswitchteammember.cdxml

Not applicable

1,234

18-Jun-2013

12:26

Not applicable

Msft_netswitchteammember.format.ps1xml

Not applicable

3,380

18-Jun-2013

12:26

Not applicable

Msnetimplatform.mof

Not applicable

43,638

21-Aug-2013

23:45

Not applicable

Ndisimplatcim.dll

6.3.9600.17714

156,672

26-Feb-2015

04:04

x86

Ndisimplatform.dll

6.3.9600.17415

98,304

29-Oct-2014

01:45

x86

Ndisimplatform.sys

6.3.9600.17714

109,568

26-Feb-2015

04:20

x86

Netlbfo.psd1

Not applicable

1,074

18-Jun-2013

12:26

Not applicable

Netlbfo.types.ps1xml

Not applicable

8,547

18-Jun-2013

12:26

Not applicable

Netswitchteam.mof

Not applicable

28,338

21-Aug-2013

23:45

Not applicable

Netswitchteam.psd1

Not applicable

1,056

18-Jun-2013

12:26

Not applicable

Netswitchteamcim.dll

6.3.9600.17415

110,080

29-Oct-2014

01:45

x86

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

File name

File version

File size

Date

Time

Platform

Vmsif.dll

6.3.9600.17396

65,024

08-Oct-2014

05:53

x64

Vmsnetsetupplugin.dll

6.3.9600.17396

33,792

08-Oct-2014

06:07

x64

Vmswitch.sys

6.3.9600.17714

689,152

26-Feb-2015

05:00

x64

Vmsif.dll

6.3.9600.17396

65,024

08-Oct-2014

05:53

x64

Vmsntfy.dll

6.3.9600.17396

91,648

08-Oct-2014

06:54

x64

Vmswitch.sys

6.3.9600.17714

689,152

26-Feb-2015

05:00

x64

Msft_netlbfoteam.cdxml

Not applicable

7,069

18-Jun-2013

14:54

Not applicable

Msft_netlbfoteam.format.ps1xml

Not applicable

2,973

18-Jun-2013

14:54

Not applicable

Msft_netlbfoteammember.cdxml

Not applicable

5,764

18-Jun-2013

14:54

Not applicable

Msft_netlbfoteammember.format.ps1xml

Not applicable

4,789

18-Jun-2013

14:54

Not applicable

Msft_netlbfoteamnic.cdxml

Not applicable

4,824

18-Jun-2013

14:54

Not applicable

Msft_netlbfoteamnic.format.ps1xml

Not applicable

4,720

18-Jun-2013

14:54

Not applicable

Msft_netswitchteam.cdxml

Not applicable

5,834

18-Jun-2013

14:53

Not applicable

Msft_netswitchteam.format.ps1xml

Not applicable

2,428

18-Jun-2013

14:53

Not applicable

Msft_netswitchteammember.cdxml

Not applicable

1,234

18-Jun-2013

14:53

Not applicable

Msft_netswitchteammember.format.ps1xml

Not applicable

3,380

18-Jun-2013

14:53

Not applicable

Msnetimplatform.mof

Not applicable

43,638

22-Aug-2013

06:50

Not applicable

Ndisimplatcim.dll

6.3.9600.17714

202,752

26-Feb-2015

04:41

x64

Ndisimplatform.dll

6.3.9600.17415

119,808

29-Oct-2014

02:26

x64

Ndisimplatform.sys

6.3.9600.17714

126,464

26-Feb-2015

05:01

x64

Netlbfo.psd1

Not applicable

1,074

18-Jun-2013

14:54

Not applicable

Netlbfo.types.ps1xml

Not applicable

8,547

18-Jun-2013

14:54

Not applicable

Netswitchteam.mof

Not applicable

28,338

22-Aug-2013

06:50

Not applicable

Netswitchteam.psd1

Not applicable

1,056

18-Jun-2013

14:53

Not applicable

Netswitchteamcim.dll

6.3.9600.17415

143,360

29-Oct-2014

02:26

x64

Mslbfoprovider.sys

6.3.9600.17714

117,248

26-Feb-2015

05:02

x64

Vmsif.dll

6.3.9600.17396

65,024

08-Oct-2014

05:53

x64

Vmsntfy.dll

6.3.9600.17396

91,648

08-Oct-2014

06:54

x64

Vmswitch.sys

6.3.9600.17714

689,152

26-Feb-2015

05:00

x64

Vmsif.dll

6.3.9600.17396

65,024

08-Oct-2014

05:53

x64

Vmsntfy.dll

6.3.9600.17396

91,648

08-Oct-2014

06:54

x64

Vmswitch.sys

6.3.9600.17714

689,152

26-Feb-2015

05:00

x64

Msft_netlbfoteam.cdxml

Not applicable

7,069

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteam.format.ps1xml

Not applicable

2,973

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteammember.cdxml

Not applicable

5,764

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteammember.format.ps1xml

Not applicable

4,789

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteamnic.cdxml

Not applicable

4,824

18-Jun-2013

12:26

Not applicable

Msft_netlbfoteamnic.format.ps1xml

Not applicable

4,720

18-Jun-2013

12:26

Not applicable

Msft_netswitchteam.cdxml

Not applicable

5,834

18-Jun-2013

12:26

Not applicable

Msft_netswitchteam.format.ps1xml

Not applicable

2,428

18-Jun-2013

12:26

Not applicable

Msft_netswitchteammember.cdxml

Not applicable

1,234

18-Jun-2013

12:26

Not applicable

Msft_netswitchteammember.format.ps1xml

Not applicable

3,380

18-Jun-2013

12:26

Not applicable

Netlbfo.psd1

Not applicable

1,074

18-Jun-2013

12:26

Not applicable

Netlbfo.types.ps1xml

Not applicable

8,547

18-Jun-2013

12:26

Not applicable

Netswitchteam.psd1

Not applicable

1,056

18-Jun-2013

12:26

Not applicable

For all supported Windows RT 8.1

File name

File version

File size

Date

Time

Platform

Msft_netlbfoteam.cdxml

Not applicable

7,069

18-Jun-2013

14:56

Not applicable

Msft_netlbfoteam.format.ps1xml

Not applicable

2,973

18-Jun-2013

14:56

Not applicable

Msft_netlbfoteammember.cdxml

Not applicable

5,764

18-Jun-2013

14:56

Not applicable

Msft_netlbfoteammember.format.ps1xml

Not applicable

4,789

18-Jun-2013

14:56

Not applicable

Msft_netlbfoteamnic.cdxml

Not applicable

4,824

18-Jun-2013

14:56

Not applicable

Msft_netlbfoteamnic.format.ps1xml

Not applicable

4,720

18-Jun-2013

14:56

Not applicable

Msft_netswitchteam.cdxml

Not applicable

5,834

18-Jun-2013

14:56

Not applicable

Msft_netswitchteam.format.ps1xml

Not applicable

2,428

18-Jun-2013

14:56

Not applicable

Msft_netswitchteammember.cdxml

Not applicable

1,234

18-Jun-2013

14:56

Not applicable

Msft_netswitchteammember.format.ps1xml

Not applicable

3,380

18-Jun-2013

14:56

Not applicable

Msnetimplatform.mof

Not applicable

43,638

21-Aug-2013

23:38

Not applicable

Ndisimplatcim.dll

6.3.9600.17714

141,824

26-Feb-2015

03:33

Not applicable

Ndisimplatform.dll

6.3.9600.17714

94,208

26-Feb-2015

03:33

Not applicable

Ndisimplatform.sys

6.3.9600.17714

99,840

26-Feb-2015

03:44

Not applicable

Netlbfo.psd1

Not applicable

1,074

18-Jun-2013

14:56

Not applicable

Netlbfo.types.ps1xml

Not applicable

8,547

18-Jun-2013

14:56

Not applicable

Netswitchteam.mof

Not applicable

28,338

21-Aug-2013

23:38

Not applicable

Netswitchteam.psd1

Not applicable

1,056

18-Jun-2013

14:56

Not applicable

Netswitchteamcim.dll

6.3.9600.16384

103,936

22-Aug-2013

02:57

Not applicable

Additional file information

Additional file information for Windows 8.1 and Windows Server 2012 R2

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

File property

Value

File name

X86_e04ad3a3e8304f16cba023f89e067096_31bf3856ad364e35_6.3.9600.17714_none_81dec95afd1f5b18.manifest

File version

Not applicable

File size

703

Date (UTC)

26-Feb-2015

Time (UTC)

12:49

File name

X86_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.17714_none_ead692555f3fe11a.manifest

File version

Not applicable

File size

48,030

Date (UTC)

26-Feb-2015

Time (UTC)

12:53

Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2

File property

Value

File name

Amd64_8d2b32bffb793fef0ccfec7149515ce2_31bf3856ad364e35_6.3.9600.17714_none_fa040693f8245dae.manifest

File version

Not applicable

File size

708

Date (UTC)

26-Feb-2015

Time (UTC)

12:49

File name

Amd64_903502cbdb33d0857bb92ff39e542d3d_31bf3856ad364e35_6.3.9600.17714_none_b0a79eea08ee940f.manifest

File version

Not applicable

File size

701

Date (UTC)

26-Feb-2015

Time (UTC)

12:49

File name

Amd64_93ee7a0aed9826f3b72b577501886d87_31bf3856ad364e35_6.3.9600.17714_none_06e59fc97f759bb8.manifest

File version

Not applicable

File size

725

Date (UTC)

26-Feb-2015

Time (UTC)

12:49

File name

Amd64_c595584f86598a95cab06ca752e8eca3_31bf3856ad364e35_6.3.9600.17714_none_64b052be2676cd7e.manifest

File version

Not applicable

File size

707

Date (UTC)

26-Feb-2015

Time (UTC)

12:49

File name

Amd64_efa8c26a24c0ae028abab425c530c244_31bf3856ad364e35_6.3.9600.17714_none_a2e26f630d2dc92b.manifest

File version

Not applicable

File size

707

Date (UTC)

26-Feb-2015

Time (UTC)

12:49

File name

Amd64_microsoft-hyper-v-d..ch-coresystem-state_31bf3856ad364e35_6.3.9600.17714_none_e89fc26043576c5a.manifest

File version

Not applicable

File size

10,027

Date (UTC)

26-Feb-2015

Time (UTC)

12:55

File name

Amd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.17714_none_5a1539d253db398b.manifest

File version

Not applicable

File size

7,613

Date (UTC)

26-Feb-2015

Time (UTC)

12:55

File name

Amd64_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.17714_none_46f52dd9179d5250.manifest

File version

Not applicable

File size

48,034

Date (UTC)

26-Feb-2015

Time (UTC)

12:55

File name

Amd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.17714_none_026e00f3ea8f2712.manifest

File version

Not applicable

File size

21,621

Date (UTC)

26-Feb-2015

Time (UTC)

07:25

File name

Amd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.17714_none_53ef93acc520b27f.manifest

File version

Not applicable

File size

3,379

Date (UTC)

26-Feb-2015

Time (UTC)

12:55

File name

Amd64_wvms_pp_coresys.inf_31bf3856ad364e35_6.3.9600.17714_none_626da6ef600fc2ae.manifest

File version

Not applicable

File size

3,411

Date (UTC)

26-Feb-2015

Time (UTC)

12:55

File name

Wow64_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.17714_none_5149d82b4bfe144b.manifest

File version

Not applicable

File size

20,681

Date (UTC)

26-Feb-2015

Time (UTC)

05:26

Additional files for all supported Windows RT 8.1

File property

Value

File name

Arm_061f95770322a68617361b37d4eb19cc_31bf3856ad364e35_6.3.9600.17714_none_bdcdf2e07becbdc5.manifest

File version

Not applicable

File size

703

Date (UTC)

26-Feb-2015

Time (UTC)

12:49

File name

Arm_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.17714_none_ead904ad5f3cffe0.manifest

File version

Not applicable

File size

48,030

Date (UTC)

26-Feb-2015

Time (UTC)

12:49



Status

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

References

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

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×