Creating a Windows virtual machine with Oracle VirtualBox is easy, but the configuration you choose matters. A poorly sized VM may feel sluggish, and a Windows 11 guest also needs modern firmware and security features that older tutorials often ignore.
This guide assumes VirtualBox 7.2 is already installed. If you still need it, start with our VirtualBox 7.2 installation guide for Windows. Our VirtualBox 7.2 introduction is also useful if this is your first virtual machine.
Start with an official Windows ISO
VirtualBox does not include Windows or a Microsoft license. You need a legitimate installation ISO.
Microsoft provides Windows 11 directly from its official Windows 11 download page, and Microsoft specifically notes that the ISO can be used to create a virtual machine.
Windows 10 installation media is still available from Microsoft’s official software download pages, but general support for Windows 10 ended on October 14, 2025. For a new general-purpose VM, Windows 11 is usually the better long-term choice when licensing and compatibility permit it.
Windows 11 minimum requirements inside a VM
Microsoft’s Windows 11 minimums include:
- two CPU cores on a compatible 64-bit processor;
- 4 GB of RAM;
- 64 GB of storage;
- UEFI firmware with Secure Boot capability;
- TPM 2.0.
Those are minimums, not an ideal lab configuration. If the host has enough resources, 8 GB of RAM and an 80 GB or larger virtual disk provide a much more comfortable starting point.
Do not starve the host. Oracle explicitly recommends leaving enough memory for the host operating system and advises against assigning more than half of the host’s processor threads to a single VM.
Create the VM in VirtualBox 7.2
Open Oracle VirtualBox Manager and click New. VirtualBox can display the wizard in Basic or Expert mode, so the layout may differ slightly, but the same core settings are available.
Name, location, and ISO
Use a descriptive name such as Windows 11 Lab. VirtualBox also uses the VM name when organizing files, so descriptive names make larger labs easier to manage.
Choose a VM Folder on a drive with enough free space. SSD or NVMe storage is strongly preferable when possible.
Select the Windows ISO. VirtualBox attempts to identify the operating system automatically and preconfigure several settings based on the image.
Unattended installation or manual installation?
VirtualBox 7.2 supports Unattended Installation for compatible Windows images. The wizard can collect a user name, password, host name, Windows product key, and other information, then install the guest with minimal interaction.
If you want to go through Windows Setup yourself, clear Install OS Using Unattended Installation. The ISO remains attached to the VM, and Windows installs just as it would after booting a physical PC from installation media.
Manual installation is useful for learning. Unattended installation is valuable when building repeatable labs or creating several similar systems.
Oracle documents both workflows in its official Creating a New Virtual Machine guide.
Memory and virtual CPUs
For Windows 11, allocate at least 4 GB of RAM and two virtual CPUs. If the host has 16 GB or more, 8 GB of guest RAM is often a better practical choice.
Two vCPUs satisfy the minimum requirement. Four may make sense on a host with eight or more processor threads, especially if no other heavy VMs are running.
Giving a VM more resources than it needs is not automatically beneficial. If Windows on the host begins paging heavily or becomes unresponsive, the VM has been sized too aggressively.
Create the virtual disk
For a VM that will remain in VirtualBox, VDI is the simplest native disk format. Other formats, including VMDK, are available for interoperability use cases.
A dynamically allocated disk grows on the host as data is written, up to the maximum capacity you define. Windows inside the VM still sees the configured virtual capacity.
Windows 11 requires at least 64 GB. An 80 GB or 100 GB virtual disk gives updates and applications more breathing room.
UEFI, TPM 2.0, and Secure Boot
Before installing Windows 11, verify the VM’s firmware and security settings.
VirtualBox 7.2 supports:
- UEFI/EFI firmware;
- a virtual TPM 2.0 device;
- Secure Boot.
Microsoft requires Windows 11 systems to use UEFI firmware that is Secure Boot capable and to provide TPM 2.0. VirtualBox can adjust some settings automatically when the selected guest type is Windows 11, but it is still worth reviewing them before installation begins.
For a new Windows 11 VM, use UEFI and TPM 2.0 rather than deliberately building a legacy BIOS configuration unless you have a specific compatibility reason.
Use NAT as the default network mode
Older tutorials often recommended Bridged Networking immediately. That is unnecessary for most desktop VMs.
NAT is a better default for a lab or workstation VM. The guest can reach the Internet through the host, but it does not automatically appear on the physical LAN as another directly reachable system.
Use Bridged Adapter when the VM genuinely needs its own presence on the local network, such as a server that other devices must access.
VirtualBox also provides Host-Only, Internal Network, and NAT Network modes for more specialized labs.
Graphics and 3D acceleration
VirtualBox selects an appropriate graphics controller for the guest operating system. 3D acceleration can improve some desktop workloads after Guest Additions are installed, but it is not required to create or install Windows.
If a VM develops graphical artifacts or instability, disabling 3D acceleration is a reasonable troubleshooting step. Oracle notes that Direct3D support for current Windows guests relies on the WDDM driver supplied with Guest Additions.
Leave integration features off until Guest Additions are installed
Shared clipboard, drag and drop, and shared folders are convenient, but they depend on Guest Additions for proper integration.
They also create additional communication paths between host and guest. That is usually acceptable on a normal development VM, but it is not ideal for malware analysis or hostile-content labs.
Leave those features at their default settings during initial creation and enable them later only when they are useful.
Start the VM and install Windows
Once the ISO and virtual hardware are ready, select the VM and click Start.
If you selected unattended installation, VirtualBox begins the automated workflow using the information entered in the wizard. If you selected manual installation, Windows Setup appears normally.
A manual installation follows the same general process as a physical PC: choose language and edition, accept Microsoft’s license terms, select the virtual disk, and allow Windows to copy files and restart.
If you specifically need Windows 10, our Windows 10 installation guide remains available, although Windows 10 reached end of general support on October 14, 2025.
Install Guest Additions after Windows
A newly installed Windows guest can run with generic drivers, but Guest Additions provide much better VirtualBox integration.
From the VM window, choose Devices → Insert Guest Additions CD Image, run the Windows installer inside the guest, and restart when prompted.
Guest Additions provide better mouse integration, dynamic display resizing, VirtualBox graphics drivers, shared clipboard support, and shared folders.
Create a clean baseline snapshot
After Windows is installed, fully updated, and Guest Additions are working, consider creating a baseline snapshot before experimenting with additional software or configuration changes.
Remember that a snapshot is not a backup. If the physical storage containing the VM is lost, the VM and its snapshots can be lost together.
A reasonable Windows 11 starting configuration
For a modern host with enough resources, a practical starting point is:
- RAM: 8 GB;
- vCPU: 2 to 4;
- disk: 80 GB dynamically allocated or larger;
- firmware: UEFI;
- TPM: 2.0;
- Secure Boot: enabled when required by the installation flow;
- network: NAT;
- Guest Additions: install after Windows;
- shared clipboard/folders: enable only when needed.
This is not a universal prescription. A host with only 8 GB of total RAM should not give all 8 GB to the guest, and a server-oriented lab may need a very different balance of CPU, memory, storage, and networking.
