Guided path: Virtualization & VBS
Step 1 of 3
Virtualization
Hypervisor layers, virtual machines, and how Windows isolates guests from the host.
Official Microsoft docs
Closest official references related to this topic on Microsoft Learn.
Why it matters
Hyper-V, WSL2, and cloud workloads all depend on hardware virtualization and the Windows hypervisor stack.
Mental model
The hypervisor sits below the OS kernel (or splits it). Guests think they own hardware; the host multiplexes CPUs, memory, and devices.
Windows building blocks
Names and paths you can look for in Task Manager, Explorer, or documentation.
- ServiceHyper-V Host Compute Service
Manages VM lifecycle on client SKUs
- Filevmcompute.exe / vmwp.exe
Worker processes for VMs
Go one level deeper
Extra detail for readers who want more precision before opening a child topic.
- Enlightened guests use synthetic NIC/storage; emulated devices exist for compatibility.
- VBS uses the hypervisor even when you are not running a traditional VM desktop.
How it works
- 1CPU virtualization extensions let the hypervisor trap sensitive operations.
- 2The root partition runs the management OS; child partitions run guests.
- 3Synthetic devices (VMBus) avoid emulating every hardware detail.
Key terms
- Hypervisor
- Software layer that schedules virtual CPUs and isolates guest memory.
- Partition
- An isolated execution environment managed by Hyper-V.
- VMBus
- High-speed channel between Hyper-V guest and host services.
WSL2 is a lightweight VM
WSL2 runs a Linux guest on Hyper-V infrastructure while integrating with the Windows desktop experience.
Common misconception
Virtualization is not the same as containers. Containers share one kernel; VMs run separate kernels.
Go deeper
You should read next
Ranked from your current topic, related links, branch depth, and any active guided path.
intermediate
Hyper-V & partitions
Root vs child partitions, vCPUs, and synthetic devices.
Next step in your guided path
expert
VBS, HVCI & isolation
Virtualization-based security features that protect credentials and kernel code.
Go deeper in this branch
intermediate
HAL & boot
Hardware abstraction and the path from firmware to the running kernel.
Related topic