How to Set Up Virtual Machines on Windows with Hyper-V

Hyper-V is Windows’ native hypervisor, built directly into Windows 10/11 Pro, Enterprise, and Education editions — no third-party virtualization software required for a fully capable VM host.

Step 1: confirm hardware virtualization support is enabled

systeminfo | find "Virtualization"

Confirm virtualization extensions are enabled in BIOS/UEFI first — Hyper-V cannot function without them regardless of software configuration.

Step 2: enable the Hyper-V feature

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Or via Control Panel: Programs → Turn Windows features on or off → Hyper-V. A restart is required after enabling.

Step 3: open Hyper-V Manager

Start menu → Hyper-V Manager

Step 4: create a virtual switch for networking

Hyper-V Manager → Virtual Switch Manager →
  New virtual network switch → External
  (bind to your actual physical network adapter)

An External switch bridges VM traffic onto your real network, giving VMs their own visible IP addresses; Internal and Private switches provide more isolated networking for VMs that don’t need direct external access.

Step 5: create a new virtual machine

Hyper-V Manager → Action → New → Virtual Machine

Follow the wizard: assign memory, attach the virtual switch created in Step 4, and create a new virtual hard disk (or attach an existing one).

Step 6: attach an installation ISO and boot

VM Settings → DVD Drive → attach an .iso file

Start the VM and proceed through the guest OS’s normal installation process, same as installing on physical hardware.

Step 7: install Hyper-V Integration Services inside the guest

Modern Windows and Linux guests generally include integration services already; older or minimal guest images may need them installed separately for proper mouse integration, clipboard sharing, and clean shutdown support from the host.

Step 8: use checkpoints for a safe rollback point

Hyper-V Manager → select VM → Checkpoint

Checkpoints (Hyper-V’s term for snapshots) let you revert a VM to an earlier state — useful before a risky change inside the guest, the same safety-net pattern as FreeBSD’s ZFS boot environments applied at the VM level instead.

Step 9: manage VMs from PowerShell for scripting or remote administration

Get-VM
Start-VM -Name "MyVM"
Stop-VM -Name "MyVM"

Why Hyper-V being a type-1 hypervisor matters practically

Unlike a hosted (type-2) hypervisor running as an application on top of the OS, Hyper-V runs beneath Windows itself, with the Windows you’re using also technically running as a guest under Hyper-V’s own root partition once enabled — this architecture is why VMs under Hyper-V generally achieve better performance and hardware access than application-level virtualization software, at the cost of Hyper-V needing to be enabled at the OS level rather than simply installed as a regular program.