VirtualBox installs on almost any PC, but a virtual machine that actually feels usable needs more than the minimum. This page gives the honest host requirements - what to check, what to switch on, and where the real limits are - before you blame the software for a slow VM.
Most disappointing first VMs are not a VirtualBox problem - they are a host problem. The processor's virtualisation feature was off, the host only had 8 GB of RAM and gave 6 of it away, or the virtual disk filled the last free corner of a nearly full drive. Five minutes of honest checking first saves all of that. Here is exactly what a host PC needs, in plain words.
Every modern processor can run virtual machines directly in hardware - Intel calls the feature VT-x and AMD calls it AMD-V. VirtualBox depends on it completely; without it, modern versions will not start a 64-bit guest at all.
Almost every processor sold in the last decade includes this feature, including budget ones. If yours genuinely lacks it, no setting in VirtualBox can replace it - that is a hard hardware wall, not a software fault.
RAM is shared, not multiplied: every megabyte the VM uses is a megabyte your real Windows cannot. The rule that keeps both machines healthy is simple - give the VM at most half your total RAM, and always leave the host at least 4 GB for itself.
VirtualBox even colour-codes the memory slider: the red zone means you are taking RAM the host needs. It is not decoration - a host pushed into swapping makes the VM slower than giving it less RAM would have.
The same sharing logic applies to processor cores. If your CPU shows 8 logical processors in Task Manager, giving the VM 2 to 4 is the sweet spot for a desktop guest. Giving it all 8 leaves the host nothing to schedule its own work with, and the whole PC feels worse, not better.
One more honest note: a single-core old CPU can still run a VM, but Windows setup will take a long time and the desktop will lag. Virtualisation makes VMs efficient; it cannot invent performance the hardware does not have.
A Windows virtual disk needs room to live. Microsoft's own floor for Windows 11 is 64 GB of storage, and a working VM with updates and a few programs comfortably uses 60 to 80 GB. With a dynamically allocated VDI the file starts small and grows as the guest writes data - but it never shrinks back on its own when you delete files inside the VM.
Two practical rules: put the VM on your fastest drive if you have an SSD (a VM on a spinning hard disk is the single most common reason for a painfully slow virtual machine), and keep at least 20 GB free beyond the VM's size so the file can grow without hitting a full disk mid-update.
Put together, the comfortable host for a Windows VM is: virtualisation-capable CPU, 16 GB RAM, an SSD, and 100 GB free. The workable minimum is 8 GB RAM with a 4 GB VM and patience. Below that, VirtualBox will still install and run - but manage your expectations. It is a free tool that shares the PC you already own; it is not a way to get a second fast computer out of a very old one.
Watch the full tutorial - how the machine is prepared, the VM created with sensible values, and Windows installed inside it.
Watch Full VideoOpen Task Manager, go to Performance and then CPU, and read the Virtualization line. Enabled means you are ready. Disabled means the feature exists but is switched off in BIOS or UEFI settings - enable it there and restart.
Yes, with a 4 GB virtual machine and realistic expectations. Windows inside will run office work and learning tasks fine, but it will not feel fast, and you should close heavy programs on the host while the VM is running.
It works, but the virtual disk lives in a file, so the guest is only as fast as the drive holding that file. On a spinning hard disk a Windows VM feels very slow, especially during boot and updates. An SSD is the single biggest upgrade for VM performance.