Manage Learn to apply best practices and optimize your operations.

Default Switch Makes Hyper-V Networking Dead Simple

In the wake of Windows 10 Fall Creators Update (Version 1709), lots of interesting wrinkles are emerging. A raft of Hyper-V changes in this release are spelled out in a new Virtualization Blog post from Microsoft. Dated 11/13/17, it’s entitled “What’s new in Hyper-V for Windows 10 Fall Creators Update?” Among the various new items it spells out, there’s an item that reads “Hyper-V has a Default Switch for easy networking.” Having just tried it out myself, I can affirm that this Default Switch makes Hyper-V networking dead simple.

Default Switch Makes Hyper-V Networking Dead Simple

When picking a virtual NIC in Hyper-V, Default Switch is your new go-to option.

How Is It That Default Switch Makes Hyper-V Networking Dead Simple?

As the foregoing screenshot shows, an option named “Default Switch” now shows up whenever you’re asked to select a network interface or to identify network-based resources. It comes as part of the runtime environment, by default as it were. Having struggled to identify the right NIC on a Hyper-V host with two GbE interfaces (where only one was connected), I’ve had bonehead problems with Hyper-V networking on earlier versions of the software. But with this new default option, you can pick simple, basic networking as a menu item as soon as you turn Hyper-V on. It doesn’t get a whole lot simpler than this, nor easier to use. Highly recommended!

What Else Is New in Version 1709 Hyper-V?

According to the “What’s new” blog post , these other new features for Hyper-V are present in Version 1709:

  • Quick Create Gallery: a quick create button in Hyper-V Manager can reference a gallery of pre-defined OS images, to which you can add your own items. This capability is still under construction, though, as the following 11/8 post to the same blog explains “Create your custom Quick Create VM gallery.” I’m waiting for the promised documentation to show up to avoid hand-crafting the necessary JSON documents.
  • Easy to revert VMs to their start state: Hyper-V now creates a checkpoint each time you start a VM. That means you will always have a reasonably current checkpoint to which you can revert for all your VMs.
  • Host battery state visible in VMs: means that you can tell how much battery life is left from inside a VM running on a battery-powered PC.
  • Virtual machines are easier to share: A new “Share” button packages and compresses VMs to make them easier to move to another Hyper-V host using the Virtual Machine Connection facility.

Good stuff.

[Note added 12/7/17: Based on a member’s report of issues in getting default switch working on an existing/prior installation of Hyper-V in the Fall Creators Update/Version 1709, it looks like if you encounter problems trying to get it to work, one quick and easy fix is to do the following:
1. Disable Hyper-V
2. Restart PC
3. Re-enable Hyper-V
This sequence is reported as working for at least two people: my colleague and occasional co-author Kari Finn, and the original poster who reported the problem at TenForums.com.]

Join the conversation

1 comment

Send me notifications when other members comment.

Please create a username to comment.

Unbelievably, this post helped me.  I just created a totally vanilla installation: Win 10 Pro Workstation w/Hyper V, then a VM with Win 10 Pro Workstation.  Both 1909. Using the default virtual switch.  The VM had no networking.  There a 100 tips out there in the web about how to fix this: the only one that worked for me was suggesed above: stop the hyper-v service and reboot.  Hyper-V service was running again after the reboot, I started the VM, and network access!  Remarkable, and thank you!
Cancel

-ADS BY GOOGLE

SearchVirtualDesktop

SearchWindowsServer

Close