Using Your Windows 8 Wireless Connection Inside Hyper-V


As a Microsoft developer, I prefer to leverage Microsoft tools whenever possible, thus, I was ecstatic to hear about Hyper-V support in Windows 8 Professional. It is by far one of the most exciting features in the new operating system.

Traditionally, I have leveraged VMWare player from my laptop to compartmentalize my client development environments. I have found that dedicating a VM to each client keeps my laptop clean and reduces overhead of all the various applications we need as developers. Recently, I embarked to setup a new Hyper-V VM on Windows 8 and discovered that Hyper-V does not automatically create a wireless adapter with the guest VM. So, despite having a Wi-Fi connection on my laptop, my new VM could not access the Internet.

After some research and tinkering, I was able to configure Hyper-V to use my laptop’s wireless connection. I thought it would be helpful to document the process as a way to help others looking to switch to Windows 8’s Hyper-V.

The Hyper-V Virtual Switch is a software-based layer-2 network switch built into Windows 8’s Hyper-V Manager. The switch allows you to connect virtual machines to virtual or physical networks. In this case, we will be setting up an internal virtual network adapter to support communication between the laptop running Windows 8 and the VM running Windows Server 2012.

  1. Launch Hyper-V Manager from your App Menu
  2. In the Actions area in right-hand navigation, click “Virtual Switch Manager”
  3. When the Virtual Switch Manager window opens, select “New virtual network switch” on the left, select “Internal” on the right, and then click the “Create Virtual Switch” button
  4. Give the new switch a name like “Virtual WLAN” and click “OK”
  5.  In Windows 8 sys tray, right-click on the wireless icon and click on “Open Network and Sharing Center.” You will see the new Unidentified Network connected to the vEthernet (Virtual WLAN) adapter.
  6. Back in Hyper-V Manager, select your VM (make sure it is turned off) and on the lower left side, click “Settings”
  7. The Settings window will default to Add New Hardware, select “Legacy Network Adapter” and click “Add
  8. In the Legacy Adapter details, select the “Virtual WLAN” adapter we configured earlier and click “OK
  9. Go back to Windows 8’s Network and Sharing Center and click on the “Wi-Fi” link (or the name of your laptop’s wireless adapter) listed in the Connections
  10. In the adapter status window, click “Properties”

  11. In the Properties window, click the Sharing tab, check the “Allow other network users…” box, select “vEthernet (Virtual WLAN)” (or the name of your wireless adapter), and click “OK” to close the window
  12. Click Close to exit the Wi-Fi status window
  13. To confirm you have it setup correctly, click on the “Change adapter settings” link. You should see the word Shared beside your wireless connection.

Now, whether you are trying to get some work done at the airport or giving a demo at the client’s office, your Hyper-V VM can share your laptop’s wireless connection.

If you have other virtualization questions or are looking for more great tips, please send us a tweet @CrederaMSFT on Twitter. Also, be sure to follow Credera on LinkedIn for more great tips.



  • Joshua

    Thank you! Just wanted to add that I didn’t have the drop-down menu for the home networking connection under the wi-fi properties at first. I unchecked it and closed the properties. Opened it again and my drop down menu was there! Internet is working great on my virtual machine.

  • Karl Zachry

    (posted without being anonymous)

  • Chase Grisham

    This method did not work for me, however bridging the two connections did work.

  • Cliff Bradshaw

    This worked perfectly for me! Nice job sir.

  • M Nawaz

    Very helpful tips to get started with Hyper-V. It worked for me.

  • Dustin Mobley

    Has anyone got this to work using Windows 8 Hyper-V but with a Windows 7 VM?

  • Emad Elwany

    This was very useful, thanks for sharing!

  • Yury Averkiev

    Thanks! I’ve been fighting this problem for days. Tried many suggestion, but it’s your blog post that has finally helped me to solve this issue.

  • Brian Strickland

    Thank you!!!! I’ve done this with a wired setup easily but this was the first time I had to use a wireless connection and couldn’t figure it out. thank you again!

  • GCamacho

    I only get the home sharing option on my Ethernet nic not my wireless nic

  • Thomas E Boland

    ICS is a good choice if you don’t need access to the VM from the network. If your VM is another client (like Win7 or Ubuntu Desktop) ICS is a good choice. If the VM is a server (like CentOS or similar) that you want to host websites, have file shares, mySql servers, you name it, to the local network. you should bridge the Virtual Switch and the Wi-Fi connections instead of ICS.

  • netbob

    Both scenarios did not work for me. Enabling ics refused to give me the drop down for the virtual WLAN adapter created in hyper v. Even unchecking and going back in did not work. Bridging the wifi and virtual WLAN adapters also did not work. I have to manually unbridge the wifi device and then it’s a hit or miss that I might have to bounce the notebook. If its worth anything, the wifi is a qualicomm atheros ar9485. Supposedly there is another solution that allows access to your hyper v vm’s in win 8 both from internal private ip’s as well as from devices externally. (most likely it’s windows 8.1 that will have to resolve this.)

  • Steven Sanchez

    This article has nothing to do with WiFi -it’s exactly the same for a wired connection.
    And BTW, make the virtual switch “External” if you want your VM to grab a separate IP straight from your router.

  • mr9d011

    unable to access internet on my physical machine when i used to apply above suggested method,provide a way out for this issue if you have any???

  • mr9d011

    i have applied your method but after that i got no internet access on my physical machine,wht could be the issue?

  • Steven Sanchez

    Check “Allow management operating system to share. ..” under the “External Network” option. If that doesn’t do it, then maybe your router is configured to only allow 1 IP address per MAC address.

  • Daniel Mackay

    Top post mate! Initially I couldn’t find the ‘Home Network Connection’ drop down, but I found out it was because the internal switch was still connected via a non-legacy network adapter. Once I removed that and reconnected the legacy adapter I could then select the ‘Home Network Connection’ from the sharing tab. For anyone having trouble with sharing drives, you can simply connect via remote desktop and add access to your drives via that. Thanks again!

  • Marcia Dorer

    Thank you so much….what a life saver!

  • Nathanael Schulte

    Every time I set up a bridged connection over WiFi, I get consistent issues where the guest OS keeps dropping the network connection, and sometimes it kicks me off the WiFi network too. Any ideas about that?

  • James Worden

    Thank you for this straight forward approach. I really wish I had seen this about 3 days ago!

  • Karen Magno

    This was very helpful. I have internet access on my virtual machine but I cannot seem to browse to the host machine which is Windows 8. Any ideas? Thanks.

  • Evan S

    The “Home Networking Connection” drop-down box; I don’t have it.

    I tried what Joshua posted, but that did not make it appear. Help please!

  • Evan S

    Could you please explain in detail how you fixed this? I’m not sure I follow you. Thank you.

  • Daniel Mackay

    I followed the instructions above, and provided the additional comments above during the process. Which part are you having trouble with?

  • Evan S

    I don’t understand the following:

    “I found out it was because the internal switch was still connected via a non-legacy network adapter. Once I removed that and reconnected the legacy adapter I could then select the ‘Home Network Connection’ from the sharing tab.”

    What exactly did you do to resolve the issue? I’m sorry. I’m not as technical as you are and I don’t follow the solution.

  • Jason

    Thank you!

  • AD

    The only post out in the internet that proved helpful, thanks a lot for this info owe you one.

  • Stephan

    There is a bug in IPv6 that creates a packet flood (neighborhood unsolicited). Try diabling Ipv6

  • Nathanael Schulte

    Thanks for the suggestion! Turn it off on the virtual adapter, the physical adapter or both?

  • Michael Lacey


  • Steven Rasmussen

    The virtual adapter did not show up at first. After trying to bridge the 2 connections (unsuccessfully) I tried again and this time the connection show in the dropdown so I was able to share the internet with it. Works great now! Thanks

  • SQLGuru

    To further this post…..I use Hyper-V because I’m a consultant and like to keep my different clients’ work apart from the others and VMs are a great way to do it. However, I sometimes need to use a VPN to access client resources (when not onsite). The key is to set up the VPN *INSIDE* the VM. Your VM can’t access the VPN from your host OS (you can’t even set up a Virtual Switch to bridge the connection).

  • itoctopus

    Fo those who have Windows 8 Professional but don’t have Hyper-v (such as myself), then you can download it here:

    Figured this would save time for someone…

  • disqus_xXNqoAVYoH

    You are a legend!

  • jedierikb


  • Michael Peters

    I’ve combed the channels for a resolution to why my VMs broke after updating to Windows 8.1 and this has been the only resource guide that did the job. Thank you!

  • Michael Schlotfeldt

    You are a life saver!! I have fighting to get this work all day. Your directions worked perfectly.

  • Colin Dente

    Thank you for this. I have found many other supposed solutions to this issue, but none have worked – your clear explanation has solved my problem. Excellent stuff!

  • xmcmullen

    Fantastic write-up. Cheers!

  • Francesco Milano

    Thanks a lot man! It works great!

  • Srinivas G

    Thanks a lot. It worked for me. Before seeing this post I thought that I selected a wrong VM. But now I am happy using Microsoft Hyper-V.

  • Ngoc Bui

    Thank you very much indeed. This is really helpful

  • Victor Egbe

    Great. This has just helped me get this done. Thank you very much.

  • dctech1000

    Thank you very much !

    I suffered through this and was just about starting to feel silly for having splurged on Win8 Pro upgrade but then followed your advice.

    Anyhow, the steps are a little modified:
    Hyper-V Manager -> Virtual Switch Manager -> New Virtual Switch -> Internal
    Name: Virtual Switch c
    Connection Type: Internal

    1b. RESULT
    In the Network Connections, the following show up:
    * vEthernet (Virtual Switch C)
    * vEthernet (VMSwitch C) // not sure about this last one

    2. Share Wi-FI Connector
    Network Connections -> select Wi-Fi -> Properties -> Sharing
    Check Allow other networks to connect this computers internet connection
    In drop down, selected vEthernet (Virtual Switch C)

    3. Start up the VM (Ubuntu)
    Everything works !

    Thank you again !!

  • Dane

    Thank you! I’m still learning and this was the best simple direct guide that came up.

  • Patrick Frederiksen

    Thanks alot! I tried out several different solutions today, trying to figure this out, but nothing worked. Then I stumbled upon this article and wupti! Problem solved!

  • DreamensioN

    Great post Rick – thanks a lot! Just the info I was looking for to share my VM with my mobile 4G access hot spot. Using the internal network also still allows me to RDP into my VM!