VMBook field guide

Hyper-V Manager on Windows 11: what it manages and what it misses

Understand Hyper-V Manager on Windows 11, its native strengths, and how VMBook adds QEMU, WSL and remote hosts without taking Hyper-V machines over.

Why this becomes a problem

Windows developers often have three separate worlds: WSL distributions for daily tools, Hyper-V machines for Windows-native virtualization, and QEMU images for appliances or other processor architectures. Opening a different console for each makes it harder to see what is running, where its disk lives and which engine owns it.

How VMBook approaches it

VMBook uses PowerShell to list and operate Hyper-V machines in place. It can start, stop, save, checkpoint, clone and inspect them while Hyper-V remains authoritative. WSL and QEMU objects appear beside them with their real type, and remote computers can be grouped by office or data center.

Recommended workflow

  1. Keep Hyper-V networking and advanced settings in native tools.
  2. Give automation only the PowerShell permissions it needs.
  3. Use checkpoints for short rollback windows, not as independent backups.
  4. Convert an offline copy only when a machine truly needs to leave Hyper-V.

Limits and checks

VMBook is not System Center Virtual Machine Manager and does not claim Hyper-V clustering, enterprise role delegation or production orchestration in version 0.1.

Primary documentation

Frequently asked questions

What problem does this guide solve?

Hyper-V Manager is the native console for Hyper-V hosts and machines. It is the right authority for Hyper-V virtual switches, checkpoints and platform-specific settings, but it does not provide one inventory for QEMU, WSL, libvirt, Proxmox and ESXi.

How does VMBook help?

VMBook uses PowerShell to list and operate Hyper-V machines in place. It can start, stop, save, checkpoint, clone and inspect them while Hyper-V remains authoritative. WSL and QEMU objects appear beside them with their real type, and remote computers can be grouped by office or data center.

What should I verify before using it?

VMBook is not System Center Virtual Machine Manager and does not claim Hyper-V clustering, enterprise role delegation or production orchestration in version 0.1.

Download VMBook free Browse all guides

VMBook connecting desktop, server and compact hosts across processor architectures
One machine model across desktops, servers and processor architectures.
VMBook control plane connecting virtual machines across three data-center sites
Remote hosts grouped into sites, with each host in control of its machines.