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. Computer does not shut down after you remove a virtual switch in Windows Server 2012

Computer does not shut down after you remove a virtual switch in Windows Server 2012

View products that this article applies to.

Symptoms

Consider the following scenario:

  • You install a virtual switch that is associated with a network adapter team on a Windows Server 2012-based computer.        
  • A virtual switch extension is also installed on the computer.
  • A Virtual Machine Queue (VMQ) is enabled on the network adapter team.
  • You delete the virtual switch, and then you try to shut down the computer.
In this scenario, the computer hangs, and it must be manually turned off and on to recover.

↑ Back to the top

Cause

This issue occurs because Windows encounters a problem and cannot remove the VMQ from the network adapter team after you delete the virtual switch. Therefore, the computer hangs when you try to shut it down.

↑ Back to the top

Resolution

This hotfix is also available at Microsoft Update Catalog.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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, 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.

Registry information

To apply this hotfix, 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 file information 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.2.920 0.16 xxxWindows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows 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 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 x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Vmsif.dll6.2.9200.1638446,08026-Jul-201203:07x64
Vmsntfy.dll6.2.9200.1638489,08826-Jul-201203:07x64
Vmswitch.sys6.2.9200.16627569,34430-May-201323:12x64
Vmsif.dll6.2.9200.1638446,08026-Jul-201203:07x64
Vmsntfy.dll6.2.9200.1638489,08826-Jul-201203:07x64
Vmswitch.sys6.2.9200.20732569,34431-May-201306:32x64
Vmsif.dll6.2.9200.1638446,08026-Jul-201203:07x64
Vmsntfy.dll6.2.9200.1638489,08826-Jul-201203:07x64
Vmswitch.sys6.2.9200.16627569,34430-May-201323:12x64
Vmsif.dll6.2.9200.1638446,08026-Jul-201203:07x64
Vmsntfy.dll6.2.9200.1638489,08826-Jul-201203:07x64
Vmswitch.sys6.2.9200.20732569,34431-May-201306:32x64

↑ Back to the top

Workaround

To work around this issue, disable the VMQ on the network adapter team.

Note Network performance might decrease after you disable the VMQ feature.

↑ 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
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameAmd64_2fbe186cb7ef48a6e50bd8c5a6d4134f_31bf3856ad364e35_6.2.9200.20732_none_350b9be07d4ce5f9.manifest
File versionNot applicable
File size708
Date (UTC)31-May-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_67343cdc17d62f2960b7f2d07eca311d_31bf3856ad364e35_6.2.9200.16627_none_ed1bb4d9c045134c.manifest
File versionNot applicable
File size708
Date (UTC)31-May-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.2.9200.16627_none_c218c70009adba3c.manifest
File versionNot applicable
File size162,594
Date (UTC)31-May-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.2.9200.20732_none_c292926d22d7f744.manifest
File versionNot applicable
File size162,594
Date (UTC)31-May-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.2.9200.16627_none_bbf320da7af33330.manifest
File versionNot applicable
File size3,379
Date (UTC)31-May-2013
Time (UTC)15:46
PlatformNot applicable
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.2.9200.20732_none_bc6cec47941d7038.manifest
File versionNot applicable
File size3,379
Date (UTC)31-May-2013
Time (UTC)15:46
PlatformNot applicable
File nameUpdate-bf.mum
File versionNot applicable
File size2,415
Date (UTC)31-May-2013
Time (UTC)15:46
PlatformNot applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2840681
Revision : 1
Created on : 1/7/2017
Published on : 7/9/2013
Exists online : False
Views : 186