The following forum(s) have migrated to Microsoft Q&A (Preview): Azure Virtual Machines!
Visit Microsoft Q&A (Preview) to post new questions.

Learn More

 locked
New NIC every re-boot of Deallocated VM RRS feed

  • Question

  • Each Windows Server 2012 VM creates a new NIC 'Ethernet #n' when VM is started.  Looking in Device Manager (hidden devices) all previous NICs still exists; how many NICs can be hidden before VM can no longer add another NIC device?

    Friday, August 9, 2013 1:58 PM

Answers

All replies

  • Hi,

    Thanks for your posting.

    Have you check this article?

    http://blogs.technet.com/b/danstolts/archive/2010/09/25/how-to-find-a-lost-missing-hidden-or-removed-network-card-nic-or-other-device-and-even-remove-it.aspx

    Regards.


    Vivian Wang
    TechNet Community Support

    • Marked as answer by Vivian_Wang Wednesday, August 14, 2013 1:13 PM
    • Unmarked as answer by MULTISY Saturday, June 28, 2014 11:07 AM
    • Proposed as answer by Erick Nogueira Wednesday, June 15, 2016 12:02 PM
    Monday, August 12, 2013 6:29 AM
  • I'm not sure how this answers the root issue of a new NIC being created after every reboot?  We also have the same problem which causes a problem with some of the services running on our vm.  How can we stop a new NIC being created on every reboot?
    • Proposed as answer by mantis2k Saturday, May 3, 2014 4:03 AM
    Thursday, April 3, 2014 5:57 PM
  • We are also seeing this and would like to stop the creation of a new NIC being created.
    Thursday, April 3, 2014 7:33 PM
  • This issue is still unresolved.

    Saturday, May 3, 2014 4:04 AM
  • Got the same issue here.

    We are stopping our developper VMs everey evening at 20:00 and are starting them up next morning at 08:00. Last Week i had a VM wich was unable to connect to any UNC Network Paths f.e \\fileserver\share or \\localhost\\share. So i spent about two days searching the web and troubleshooting until i could deleted all the hidden network adapters by a devcon skript.

    Details in this thread (http://social.technet.microsoft.com/Forums/projectserver/en-US/c9f17816-9ef3-4249-98e6-5de990112d3d/windows-cannot-access-machinesharedfolder-error-code-0x80004005?forum=w7itpronetworking)

    This finaly solved the problem, but new network adapters are still generated every morning, it's just a matter of time till the next VM is running into the same problem.

    Tuesday, May 20, 2014 1:01 PM
  • We got the same problem. I am baffled that Microsoft seems to be taking a nonchalant stand on this.

    Monday, August 11, 2014 2:18 PM
  • In addition to removing old adapters and changing the vm size back and forth, we also ran netsh int ip reset per below.  So far it has held across reboots and an azure maintenance update.

    http://msdn.microsoft.com/en-us/library/dn168976(v=nav.70).aspx

    http://support.microsoft.com/kb/299357/en-us


    Monday, August 11, 2014 3:53 PM
  • Hello Microsoft

    When will you fix this issue?
    New Network Adapters are still created every time a VM is reprovisioned...!

    We have to remove those adapters every 100 days, otherwise we can be sure to run into problems (f.e. VM not starting up, No connection to VM, No Connection to Network Shares, etc. )

    Thursday, February 19, 2015 8:28 AM
  • How much longer do you think it will actually take to switch this I've had enough of Azure and this issue.
    Tuesday, April 14, 2015 12:42 AM
  • As I had to cleanup VMs today with heavy performance issues and nearly 500 virtual network adapters, i have to come back to this Problem..

    The question still is: Is Microsoft able to provide a solution for this?


    Thursday, November 12, 2015 4:04 PM
  • Manually delete NICs isn´t a great solution.
    Wednesday, June 15, 2016 12:04 PM
  • I've been speaking to Microsoft today.  Apparently the fix is being deployed during Aug/Sept this year (that would be about now....)

    In the meantime if you have a few hundred NICs to get rid of like me there's a tool on this page that will do it for you https ://support.microsoft.com/en-us/kb/269155 (apologies for the extra space - apparently I can't post links...)

    Fingers crossed the real fix hits VMs soon!

    • Proposed as answer by Celebrinmir Tuesday, September 13, 2016 3:25 PM
    Tuesday, September 13, 2016 3:25 PM
  • Years went by and I am still dealing with the same old bug.... at least i know now that to look for if I am dealing with Azure Machines having suspicious Network Issues.
    Thursday, November 3, 2016 10:44 AM