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. A restarted virtual machine loses connectivity after you set the "Private VLAN (PVLAN) networks" option in a Windows Server 2012 R2 environment

A restarted virtual machine loses connectivity after you set the "Private VLAN (PVLAN) networks" option in a Windows Server 2012 R2 environment

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a host server that's running Windows Server 2012 R2 with the Hyper-V role installed.
  • You create two virtual machines on the host server, and you connect them to the same virtual switch.
  • You configure the Private VLAN (PVLAN) networks option for these two virtual machines.
  • You restart one of the virtual machines.

In this scenario, the restarted virtual machine loses connectivity after it restarts.

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

Restart requirement

You must 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.16 xxxWindows Server 2012 R2RTMGDR
    6.3.960 0.17 xxxWindows Server 2012 R2RTMDR
  • 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.1713662,46427-May-201410:23x64
Vmsnetsetupplugin.dll6.3.9600.1638433,79222-Aug-201309:52x64
Vmswitch.sys6.3.9600.17236690,68815-Jul-201410:30x64
Vmsif.dll6.3.9600.1713662,46427-May-201410:23x64
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.3.9600.17236690,68815-Jul-201410:30x64
Mslbfoprovider.sys6.3.9600.17236115,71215-Jul-201410:33x64
Wnv.sys6.3.9600.17136705,53627-May-201413:15x64
Wnvapi.dll6.3.9600.1638461,95222-Aug-201309:53x64
Vmsif.dll6.3.9600.1713662,46427-May-201410:23x64
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.3.9600.17236690,68815-Jul-201410:30x64
Vmsif.dll6.3.9600.1713662,46427-May-201410:23x64
Vmsntfy.dll6.3.9600.1638488,57622-Aug-201310:49x64
Vmswitch.sys6.3.9600.17236690,68815-Jul-201410:30x64

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_52d54ab5daf7e9391c951d06dd1da389_31bf3856ad364e35_6.3.9600.17236_none_52f86ad8b39a30db.manifest
File versionNot Applicable
File size725
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_88b38a33324b926a4a5c99392f83b077_31bf3856ad364e35_6.3.9600.17236_none_978b3b378cbaf003.manifest
File versionNot Applicable
File size695
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_97caf674228cec6e71c3cf0ce363415e_31bf3856ad364e35_6.3.9600.17236_none_f52f53ea53157c1b.manifest
File versionNot Applicable
File size701
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_f9c2e55fab83a828714877d72840680e_31bf3856ad364e35_6.3.9600.17236_none_094dd92ba1be2e64.manifest
File versionNot Applicable
File size708
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-hyper-v-d..ch-coresystem-state_31bf3856ad364e35_6.3.9600.17236_none_e88c199e4365e527.manifest
File versionNot Applicable
File size10,075
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.17236_none_5a01911053e9b258.manifest
File versionNot Applicable
File size7,637
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.17236_none_025a5831ea9d9fdf.manifest
File versionNot Applicable
File size21,645
Date (UTC)15-Jul-2014
Time (UTC)19:38
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-windows-wnv_31bf3856ad364e35_6.3.9600.17236_none_a09c6e2b2a90f7c8.manifest
File versionNot Applicable
File size54,090
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.17236_none_53dbeaeac52f2b4c.manifest
File versionNot Applicable
File size3,379
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_wvms_pp_coresys.inf_31bf3856ad364e35_6.3.9600.17236_none_6259fe2d601e3b7b.manifest
File versionNot Applicable
File size3,411
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File namePackage_1_for_kb2982439~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,304
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File namePackage_2_for_kb2982439~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,908
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File namePackage_3_for_kb2982439~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,004
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File namePackage_4_for_kb2982439~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,873
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File namePackage_5_for_kb2982439~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,847
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File namePackage_6_for_kb2982439~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,074
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File namePackage_for_kb2982439_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,806
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File namePackage_for_kb2982439_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size3,471
Date (UTC)16-Jul-2014
Time (UTC)03:07
SHA-1 hashNot Applicable
MD5 hashNot 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: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2982439
Revision : 1
Created on : 1/7/2017
Published on : 11/4/2014
Exists online : False
Views : 208