Issue: HyperV Virtual Machine not able to access any network.

Summary: Transferring HyperV Virtual Machines from old Host Server (Windows Server 2008 R2) to new Host Server (Windows Server 2012 R2) via manual process. Copied VHD to the new server, configured Virtual Machine on the new HyperV 2012 R2 Server. The VHDs were not converted to VHDx format. When all was then and we started the machine and gave it the same static IP, it failed to connect to any network. This Hyper V VM is not able to access the HOST Network, the Gateway,  and had an exclamation sign on the Network Icon in system tray.

Network Error IP Already Assigned to another adaptor

Solution: This is usually caused because of the hidden network adaptor present in the virtual machine, with the same static IP. You’ll have to remove these hidden adaptors to ensure all goes well. Here are the steps to do so:

  1. Shutdown the Virtual Machine, which has problem accessing the network

  2. Remove all Network Adaptor from the Settings of the Virtual Machine

Remove Network from HyperV Configuration

  1. Save the configuration of the Virtual Machine and Start it
  2. Login to Windows and open command prompt

  3. At the command prompt, type the following command and hit return: (If you do not run this command, you’ll not see the required adaptor in Step 8)

set devmgr_show_nonpresent_devices=1

  1. Again within the command prompt, type the following and hit return:

start devmgmt.msc

  1. Under View menu of Device Manager, click on Show hidden devices.

Show Hidden devices

  1. Expand the Network Adaptors and you’ll notice some Virtual Adaptors listed and are little dimmed (Like they are inactive) as compared to others. Usually named as “Microsoft Virtual Machine Bus Network Adapter #

Remove Adaptor

  1. Right click on each adaptor and remove (uninstall) the adaptor from this window. Repeat this step until you delete all inactive Microsoft Virtual Machine Bus Adaptors.
  2. Shutdown the Virtual Machine, and Add the network adaptor again under the Hyper V Virtual Machine Settings.

  3. Start the Virtual Machine, and assign the IP to the Virtual, it will now work fine.

I hope this article is helpful. Please feel free to reply with your comments, or post your query here if you still need help. For immediate support, click here.

The following two tabs change content below.
Passionate for Latest Gadgets, a Computer geek by Hobby, and luckily Profession too. Started my career in 2005 with IBM, worked with Microsoft later. Back in 2009, started Pledge Technologies ( (parent company to Grishbi). We, at Pledge Technologies, provide IT Consulting to SMBs across US & UK. Specialized in Microsoft Technologies like AD, Exchange, etc., and lot of experience of Office 365 Migration for various clients. Grishbi is a platform where we express what we learned today, and share it with world.
%d bloggers like this: