Create and configure a virtual switch with Hyper-V — by Microsoft Learn

intermediatepageLink only (©)

Explains the three virtual switch types (external, internal, private) and how to create one in Hyper-V Manager or with New-VMSwitch. It also covers sharing the host adapter with the management OS, VLAN IDs, and a NAT option for Windows clients; creating an external switch can briefly interrupt the host's network connection.

Quick steps

Hyper-V Manager, Actions, Virtual Switch Manager, choose a type and Create Virtual Switch
External switch in PowerShell: New-VMSwitch -Name <switch-name> -NetAdapterName <netadapter-name>
Internal or private: New-VMSwitch -Name <switch-name> -SwitchType Internal (or Private)

Paraphrased from the source. Menus can differ by version, so check the original for full details.

Read the full article on learn.microsoft.com

Source: Create and configure a virtual switch with Hyper-V by Microsoft Learn. Licence: Link only (©).

Source reviewed: 2026-11-02
Link checked: 2026-11-02
Tested hands-on: Not by Oddbyte.Me

hyper-vvirtual switchvm networkingnat

More in Sandbox & Virtualization

how to change connection type of default switch on Hyper-v — by Leon Laude on Microsoft Q&A

beginnerforum

The answer explains that the Hyper-V Default Switch is an internal switch that uses NAT automatically and cannot be modified. If your VMs need a different connection type, create an External virtual switch and attach them to it.

Install Hyper-V in Windows and Windows Server — by Microsoft Learn

beginnerpage

Shows how to enable Hyper-V on Windows 10/11 Pro or Enterprise (Control Panel, PowerShell or DISM) and how to add the role on Windows Server via Server Manager or PowerShell. Hyper-V cannot be installed on Home editions, and other hypervisors such as VirtualBox or VMware may misbehave while it is running.

Install Windows Sandbox — by Microsoft Learn

beginnerpage

Lists the requirements for Windows Sandbox (virtualization enabled, 4 GB RAM minimum, two cores) and how to turn it on from Windows Features or PowerShell. If the option is greyed out, the machine does not meet the requirements; inside a VM you must enable nested virtualization on the host.