NAT Switch now built into Hyper-V! – Windows 10 Fall Creators Update

With the new Windows 10 Fall Creators Update, Microsoft finally added a built-in NAT Switch into Hyper-V! This gives Hyper-V Virtual Machines access to the computer’s network. The new switch automatically assigns IP address to your Virtual Machines, so no need to run your own DHCP server anymore!

I’m happy that Microsoft finally introduced this as it was already available in other 3rd Party solutions and a good argument why some people didn’t want to migrate to Hyper-V. Now they can! I wasn’t able to find an official statement of Microsoft on this new feature, but I’m sure it will be published soon.

What do you think of this new feature? Are you going to migrate from VMware or other solutions to Hyper-V? Let me know in the comments section!

Unhappy. I was perfectly fine with my configuration, the addition of a default virtual switch created configuration errors in my VMs. I now get an error when attempting to create a virtual switch (access denied) and I need my VMs on specific IPs.

Default Switch would have been a nice option for those that wanted it….

Yes, I agree with you as I also had some problems with this Virtual Switch. Also if you remove Hyper-V and add the feature back, it will create a V2 default virtual switch without removing the old one. Ugh!