A home lab is one of the best ways to test software, learn Windows administration, or prepare for a certification—without breaking your everyday PC. With Windows 11 Pro, Enterprise, or Education, you already have a powerful hypervisor built in: Hyper-V. It lets you run multiple virtual machines on the same physical computer, each isolated from the others.
This guide walks through setting up a basic Hyper-V home lab on Windows 11. You’ll learn what hardware you need, how to enable Hyper-V, how to plan a safe internal network, and how to create and manage your first VM. Whether you’re preparing for an IT role or just want a sandbox for risky experiments, this roadmap will get you started with confidence.
Quick checklist
- Windows 11 Pro, Enterprise, or Education (Home edition does not include Hyper-V)
- A 64-bit CPU with SLAT and VM Monitor Mode extensions
- At least 4 GB of RAM for the host, plus enough for each VM you plan to run (16 GB or more recommended)
- Enough free disk space for virtual machine files (SSD strongly preferred)
- Enabled virtualization in BIOS/UEFI
- Administrator account on the PC
What you need
Before you begin, make sure your PC meets the minimum requirements for Hyper-V. It’s not available on Windows 11 Home, so you’ll need Pro, Enterprise, or Education. Hyper-V requires a 64-bit CPU with SLAT, VM Monitor Mode extensions, and hardware virtualization—many CPUs support these, but you must verify your specific CPU and firmware settings.
In the BIOS or UEFI settings, ensure that virtualization technology (often called Intel VT-x or AMD-V) and hardware-enforced Data Execution Prevention (DEP) are enabled. Second Level Address Translation (SLAT) is a CPU feature that is present if supported; it does not need to be enabled separately. To verify compatibility, run systeminfo.exe in Command Prompt and check the 'Hyper-V Requirements' section, which will list 'Virtualization Enabled In Firmware', 'Second Level Address Translation', 'VM Monitor Mode Extensions', and 'Data Execution Prevention Available'.
RAM is usually the biggest constraint. Each VM you run needs its own memory, so with 16 GB of RAM you can comfortably run two or three lightweight VMs. Disk space is also important: each Windows VM can easily take 20–40 GB, so plan for at least 100 GB free on your drive.
Practical tip: If your PC is short on RAM, start with a minimal Linux distribution like Ubuntu Server or Alpine Linux—they can run with as little as 512 MB to 1 GB.
Enable Hyper-V
To enable Hyper-V on Windows 11, open the Start menu and type 'Turn Windows features on or off'. In the dialog that appears, check the box next to 'Hyper-V' and click OK. Windows will install the required components and ask you to restart. After rebooting, you’ll find the Hyper-V Manager app in your Start menu.
Related guide: Active Directory home lab setup.
For a more controlled setup, you can also use PowerShell as an administrator. Run the command:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
Then restart the computer. Whichever method you choose, make sure virtualization support is enabled in firmware first, or Hyper-V will not start.
Verify Hyper-V is working
After installation, open Hyper-V Manager. In the left pane, you should see your computer’s name. Click on it, and in the right pane you’ll see information about the Hyper-V host, including the version and whether virtual machines can be created. If you see an error about virtualization, go back and check BIOS settings.
Practical tip: Windows 11 Home users can consider third-party alternatives like VirtualBox or VMware Workstation Player, but those are outside the scope of this guide.
Plan the virtual network
One of the most common mistakes in a home lab is using the wrong virtual switch. Hyper-V lets you create virtual switches that connect VMs to your physical network, to each other only, or to both. For a safe practice environment, you usually want an internal or private switch.
An internal switch allows VMs to talk to each other and to the Hyper-V host, but not to your main LAN. To give VMs internet access while keeping them off the physical network, you must additionally configure a NAT network on the host—either by using the built-in Default Switch (NAT/DHCP) or by setting up a custom Internal switch with NAT. Without NAT, an internal switch provides no internet connectivity.
To create a switch, open Hyper-V Manager, click 'Virtual Switch Manager' in the Actions pane, choose 'New virtual network switch', select the type, and give it a name. Then when you create a VM, attach its virtual network adapter to that switch.
Creating an internal lab network
For most lab scenarios, start with an internal switch called 'LabInternal'. Connect your VMs to it. To provide IP addresses and optional internet access, configure the host's internal adapter with a static IP and set up NAT (e.g., using PowerShell), or use the built-in 'Default Switch' which provides NAT/DHCP automatically. Alternatively, you can manually assign static IPs within a private range like 192.168.100.x. This keeps your lab traffic isolated from your home network.
Practical tip: If you need internet access for a specific test, use the built-in 'Default Switch' (NAT/DHCP) or configure an Internal switch with NAT. This provides internet while keeping your VM off the physical LAN. Only use an external switch if you specifically need direct LAN exposure and understand the risks.
Create the first VM
In Hyper-V Manager, click 'New' > 'Virtual Machine' in the Actions pane. The New Virtual Machine Wizard will guide you through the process. Give your VM a name, choose a location to store its files, and select a generation. For most modern operating systems, Generation 2 is recommended because it supports UEFI and secure boot; for Windows 11 guests, Generation 2 is required. Decide carefully—the generation cannot be changed after creation.
Related guide: test Windows updates in a VM first.
Next, assign memory. For a Windows 11 VM, you must allocate at least 4 GB (Microsoft requirement). For Windows 10 or lightweight Linux, you can start lower (e.g., 2 GB). You can enable Dynamic Memory, which lets Hyper-V adjust the memory allocated to the VM within a range, but for consistent performance, fixed memory is often simpler, especially when meeting exact OS requirements.
On the Configure Networking screen, select the virtual switch you created earlier. Then create a virtual hard disk. For a Windows 10 VM, a 40 GB default is common, but for Windows 11 guests, set the virtual disk size to at least 64 GB. You can increase it later, but meeting the OS requirement avoids initial failures. Finally, choose how to install the operating system: from an ISO file, a network installation server, or a bootable USB drive. Once created, you can start the VM and complete the OS installation.
Installing an operating system
After creating the VM, connect to it by double-clicking it in Hyper-V Manager. Then click the Start button and proceed with the OS installation as you would on a physical computer. You’ll need an ISO file of the OS, which you can obtain from official sources like Microsoft’s evaluation center or a Linux distribution’s website.
Practical tip: If you’re new to lab environments, start with a free OS like Ubuntu Server (no GUI) to get comfortable with the Hyper-V console before tackling Windows Server.
Choose RAM CPU and storage
Hyper-V gives you control over how many virtual CPUs and how much RAM each VM gets. For a basic lab, two virtual CPUs and 2–4 GB of RAM per VM are reasonable. The total resources assigned to running VMs should not exceed the physical resources of your host, or performance will suffer.
For storage, Hyper-V uses virtual hard disk files (VHDX). You can create dynamically expanding disks that grow as data is written, or fixed-size disks that allocate the full space upfront. Dynamic disks save space but can slow down when growing; fixed disks offer better performance. For a home lab, a dynamically expanding disk on an SSD is usually fine.
Remember to leave enough resources for the host OS itself. Windows 11 host needs at least 4 GB of RAM and a responsive CPU. A good rule of thumb is to reserve at least 4 GB of RAM for the host and leave at least one CPU core unassigned to VMs.
Sizing examples
A Windows 11 VM requires Generation 2, at least 4 GB RAM, 64 GB or more storage, two or more virtual processors, Secure Boot capability, and a virtual TPM (TPM 2.0) enabled, so size accordingly: 2 vCPU, 4 GB RAM, 64 GB dynamic VHDX, with Secure Boot and TPM enabled. A minimal Linux VM for command-line practice: 1 vCPU, 1 GB RAM, 10 GB dynamic VHDX. A Windows Server domain controller: 2 vCPU, 4 GB RAM, 60 GB dynamic VHDX. Adjust these based on your host’s capabilities.
Practical tip: Monitor resource usage in Task Manager on the host. If the host’s CPU or RAM is consistently above 80%, stop some VMs or reduce their allocations.
Use checkpoints carefully
Hyper-V checkpoints (formerly called snapshots) capture the state of a VM at a point in time. You can roll back to a checkpoint if something goes wrong. They are incredibly useful for testing risky changes like installing software, modifying the registry, or joining a domain.
However, checkpoints are not backups. They should not be used as a long-term backup strategy because they can grow large, impact performance, and cause issues if not managed properly. For a home lab, it’s fine to take a checkpoint before a major change and delete it once you’re satisfied with the result.
To take a checkpoint, select the VM in Hyper-V Manager and click 'Checkpoint' in the Actions pane. To revert, select the VM and click 'Revert'. Reverting will discard the VM's current state and restore it to the checkpoint.
Checkpoint vs. export
If you want to preserve the entire VM as a template or move it to another machine, use the Export feature instead. Export creates a copy of the VM files that you can import later. Checkpoints are only for rolling back changes on the same VM.
Practical tip: Avoid keeping checkpoints for more than a few days. They can bloat storage and slow down the VM. Delete them when you’re done testing by right-clicking the checkpoint and choosing 'Delete Checkpoint' (which merges changes).
Ideas for expanding the lab
Once you have the basics working, your home lab can grow. Here are a few practical scenarios you might explore:
Set up a Windows Server VM and promote it to a domain controller, then join a Windows 11 client VM to the domain to practice Active Directory management. This is a common exercise for IT certification candidates.
Create a network of VMs on an internal switch and practice troubleshooting with tools like ping, nslookup, and Wireshark. You can deliberately break things and learn how to fix them in a safe environment.
Test backup and restore procedures. Install backup software in a VM, take a backup, then delete critical files and practice restoring them. This builds confidence for real-world disaster recovery.
Practical tip: When experimenting with unknown software, take a checkpoint first so you can easily revert if it causes problems.
Frequently Asked Questions
Can I run Hyper-V on Windows 11 Home?
No, Hyper-V is not included in Windows 11 Home. You need Windows 11 Pro, Enterprise, or Education. If you have Home, consider upgrading or using an alternative hypervisor like VirtualBox or VMware Workstation Player.
How much RAM do I need for a home lab?
At minimum, Microsoft recommends 4 GB of RAM for the host, plus enough for the VMs you plan to run. For running two or three VMs simultaneously, 16 GB or more is recommended. Each VM’s memory is dedicated to it, so plan accordingly.
What is the difference between an internal and external virtual switch?
An internal switch allows VMs to communicate with each other and with the Hyper-V host, but not directly with the external physical network. To give VMs internet access while keeping them isolated from the physical LAN, you can combine an internal switch with NAT or use the built-in Default Switch. An external switch connects VMs directly to your physical LAN and the internet. For a safe lab, use an internal switch (with NAT if internet access is needed) or a private switch unless you specifically need direct LAN exposure.
Are Hyper-V checkpoints safe for backing up VMs?
No, checkpoints are not a backup solution. They capture a point-in-time state for quick rollback, but they can grow large and affect performance. For actual backups, use Hyper-V export or dedicated backup software.
Can I run Hyper-V alongside other virtualization software?
Hyper-V can conflict with some third-party hypervisors like VirtualBox or VMware Workstation because they require exclusive access to virtualization extensions. Running them simultaneously is not recommended. If you need both, consider using a different boot configuration or separate machines.
Final Thoughts
A Windows 11 home lab with Hyper-V is a powerful, low-cost way to build IT skills. By carefully planning your virtual network, sizing your VMs appropriately, and using checkpoints wisely, you can create a safe environment for experimentation. Start small, back up your work, and gradually expand as you become more comfortable. The experience you gain today will pay off in real-world troubleshooting and administration tasks tomorrow.
Official References
- Install Hyper-V (Microsoft Learn)
- System requirements for Hyper-V on Windows and Windows Server (Microsoft Learn)
- Create a virtual machine in Hyper-V (Microsoft Learn)
- Create and configure a virtual switch with Hyper-V (Microsoft Learn)
- Set up a NAT network (Microsoft Learn)
- Using checkpoints to revert virtual machines to a previous state (Microsoft Learn)
