Installing Windows 11 in a VM used to mean fighting the hardware checks — no TPM, no Secure Boot, install blocked. That’s no longer necessary. VirtualBox 7.0 added a virtual TPM and the EFI plumbing Windows 11 expects, so you can build a VM that passes the requirements cleanly instead of hacking around them.
This walkthrough builds that VM properly: EFI on, a virtual TPM 2.0 chip, Secure Boot enabled, sensible specs, the ISO mounted, and Guest Additions afterward so the desktop is actually usable. The registry bypass is here too, but as a fallback for older setups, not the main path.
What Windows 11 checks for
Before clicking anything, know what the installer is looking for. Windows 11 enforces a short list of requirements, and a VM has to present each one:
Windows 11 requirements and how VirtualBox supplies them
| TPM 2.0 | Virtual TPM in VirtualBox 7.0+, enabled in System settings |
|---|---|
| Secure Boot | Enabled in the VM's EFI motherboard settings |
| UEFI firmware | Turn on EFI for the VM (not legacy BIOS) |
| 64-bit CPU, 2+ cores | Assign 2 or more CPUs to the VM |
| 4 GB RAM minimum | Allocate 4 GB at the floor; 8 GB is better |
| 64 GB disk minimum | Create an 80 GB+ virtual disk to leave headroom |
The two that block people are TPM 2.0 and Secure Boot, and both depend on EFI being on. Get EFI enabled first and the rest falls into place.
Before you start
What you need
- VirtualBox 7.0 or later installed on the host
- A Windows 11 ISO (download from Microsoft's official site)
- Host CPU virtualization (VT-x / AMD-V) enabled and available to VirtualBox
- At least 8 GB RAM free on the host so the VM can have 4 GB comfortably
- 80 GB or more of free disk for the virtual hard disk
That third point matters. If VirtualBox can’t get hardware virtualization from the CPU — often because Hyper-V or another Windows hypervisor has claimed it — the VM will run slowly or refuse to start, regardless of how you configure Windows 11. If you hit that, work through VirtualBox VT-x is not available (Hyper-V conflict) before going further.
Step 1: Create the VM
In VirtualBox, click New and give the VM a name. If you point it at your Windows 11 ISO here, VirtualBox 7 offers Unattended Install — you can use it, but for learning the requirements it’s clearer to skip unattended setup (tick “Skip Unattended Installation”) and configure things by hand.
Set the type to Microsoft Windows and version to Windows 11 (64-bit). Then set the resources:
- Memory: 4096 MB minimum, 8192 MB if the host allows.
- Processors: 2 or more.
- Disk: create a new VDI, dynamically allocated, 80 GB or larger.
Step 2: Enable EFI, TPM 2.0, and Secure Boot
This is the part that makes Windows 11 happy. With the VM created but not started, open its Settings.
Under System → Motherboard:
- Tick Enable EFI (special OSes only).
- On VirtualBox 7.x, enable Secure Boot in the same panel.
Then the TPM. Still under System (Motherboard tab in 7.0, depending on build), find the TPM dropdown and set it to 2.0.
System settings for a Windows 11 VM
| Enable EFI | On — required for TPM and Secure Boot |
|---|---|
| TPM | v2.0 |
| Secure Boot | Enabled |
| Pointing Device | USB Tablet (smoother mouse before Guest Additions) |
| Processors | 2 or more |
| Video Memory (Display tab) | 128 MB for a responsive desktop |
Step 3: Mount the ISO and install
Go to Settings → Storage, select the empty optical drive, and attach your Windows 11 ISO. Then start the VM.
When you see “Press any key to boot from CD or DVD,” press a key quickly — the EFI boot window is short. Windows Setup loads, and from here it’s the normal flow: language, Install now, edition, and the license terms. Choose Custom when asked about install type, select the 80 GB virtual disk, and let it copy files.
Because the VM presents TPM 2.0, Secure Boot, EFI, and enough resources, you shouldn’t see the “This PC can’t run Windows 11” wall at all. If you do, shut the VM down and recheck Step 2 — something in EFI/TPM/Secure Boot didn’t take.
The bypass (only if you can’t enable the TPM)
If you’re stuck on VirtualBox 6.x or for some reason can’t expose a TPM, you can still get
Windows 11 installed. At the “This PC can’t run Windows 11” screen, open a command prompt
with Shift + F10, launch regedit, and add a bypass key.
Key: HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig
Values (DWORD, set to 1):
BypassTPMCheck = 1
BypassSecureBootCheck = 1
BypassRAMCheck = 1Create the LabConfig key if it doesn’t exist, add the DWORD values, close regedit, and click
back to retry. Setup skips the checks and continues.
Step 4: Install Guest Additions
Once Windows 11 is on the desktop, install Guest Additions. Without them the VM is stuck at a small fixed resolution, the mouse can feel off, and there’s no shared clipboard.
In the running VM’s menu, choose Devices → Insert Guest Additions CD image. Open the
virtual CD in File Explorer and run VBoxWindowsAdditions.exe, accept the prompts, and reboot
when it finishes.
After the reboot you get:
- Dynamic resolution — resize the VM window and the desktop follows.
- Shared clipboard and drag-and-drop (enable under Devices → Shared Clipboard).
- Shared folders between host and guest.
- Better display performance.
Wrapping up
Windows 11 in VirtualBox is straightforward once you stop fighting the requirements and supply them instead. On VirtualBox 7.0 and later, enable EFI, switch the TPM to 2.0, turn on Secure Boot, give the VM 4 GB or more of RAM and an 80 GB disk, and the installer passes its checks without any registry edits.
Keep the bypass in your back pocket for old builds that can’t expose a TPM, but reach for it last. Finish by installing Guest Additions so the desktop scales and the clipboard works, take a clean snapshot, and you’ve got a Windows 11 lab VM you can rebuild on a whim. For more VM walkthroughs and fixes, browse the virtualization guides.
