How to Create a Virtual Switch in Hyper-V on Windows 10

Choose the communication you want before creating a Hyper-V switch: access to the physical network, a host-and-VM lab, or a VM-only lab. Then change one VM at a time and verify the host still has the connectivity you need.

Check the host and keep a way back

Hyper-V must already be enabled on a supported edition and compatible hardware, with administrator access. Microsoft lists Windows 10 Pro and Enterprise in its installation guidance; the Hyper-V role is not available on Home. Use the linked requirements if Hyper-V Manager is missing instead of installing an unofficial workaround.

Record existing switch names, the physical adapter in use, its IP/DNS arrangement and the VM's current switch. Keep local console access available before changing an external switch. A remote session carried by the adapter being changed can drop before you can undo the configuration.

Choose the switch type

An Internal switch alone is not the same as a configured NAT network. NAT, guest addressing, DNS and any DHCP service need their own plan. Microsoft's NAT guide explains that separate setup; do not copy an arbitrary subnet or delete existing NAT networks to make a lab work.

Create a virtual switch with Hyper-V Manager

1. Open Hyper-V Manager with administrator rights and select the intended host.
2. Open Virtual Switch Manager, choose the type and select Create Virtual Switch.
3. Give it a descriptive name, such as one identifying the lab and purpose.
4. For External, select the intended physical adapter. If the host must continue using that adapter, retain Allow management operating system to share this network adapter.
5. Check the settings against your plan, then select Apply > OK. Expect a connectivity warning for external networking changes.

Connect a VM to the switch

1. Record the VM's existing network-adapter selection.
2. Open the VM's Settings > Network Adapter.
3. Select the intended Virtual switch and apply the change.
4. Check that the guest's IP addressing and DNS match the destination network before testing the intended connection.

Use one noncritical VM for the initial check. Do not move a group of working VMs before you know the new network behaves as expected.

Verify host and guest separately

Recover from an unwanted connectivity change

If only the VM lost the access it previously had, restore its recorded switch selection and any guest settings you changed, then test again. This separates a guest-side mistake from a host-side problem.

If the host lost connectivity after an external-switch change, use the local console to inspect the physical-adapter selection and host-sharing setting. Restore the values you recorded. If you created a new switch on the wrong adapter, first account for any VMs now attached to it before removing only that new configuration. Do not delete all virtual switches, reset every adapter or remove working VPN/container networking as a shortcut.

If restoring the recorded configuration does not recover access, stop and give support the before/after switch and adapter details, the affected host/guest connections and any error. Keep private IP plans and other organisation details out of public screenshots.

Documentation review: 6 October 2026. Checked against the linked Microsoft documentation. This is an editorial configuration and verification workflow, not a claim of a Windows 10 device test. No update policy or virtual-switch configuration was changed on the author’s computer for this review.

Official reference

Microsoft — Create a switch and share an adapter with the hostOfficial reference Microsoft — External, Internal and Private network scopeOfficial reference Microsoft — NAT is a separate network configurationOfficial reference Microsoft — Hyper-V installation requirementsOfficial reference