By the end of this guide you will have VirtualBox installed and a Kali Linux virtual machine imported and running — an isolated environment for security practice that leaves your host system untouched.
Prerequisites
- Windows 11 Pro (64-bit)
- At least 8 GB RAM, so you can give the VM 4 GB and leave the host enough
- 30 GB free disk space (the VM's disk grows as you install tools — more headroom is better)
- Hardware virtualization (VT-x or AMD-V) enabled in BIOS/UEFI
- 7-Zip, for extracting the archive
- No prior virtualization experience required
Steps
1. Download VirtualBox.
Get it from the official site, virtualbox.org/wiki/Downloads. Use the Windows hosts package. Avoid third-party mirror and download sites — a virtualization host is not something to install from an unverified source.
2. Install VirtualBox.
Run the installer with default options. Expect: a brief network interruption partway through, which is normal — the installer adds virtual network adapters.
3. Download the Kali VirtualBox image.
Get it from kali.org/get-kali/ and choose the VirtualBox 64-bit image, a .7z archive of several GB. Note the SHA256 value shown on the download page.
4. Verify the checksum before extracting.
Open PowerShell in your download folder and run:
Get-FileHash kali-linux-*-virtualbox-amd64.7z -Algorithm SHA256
Expect: a hash that matches the value on Kali's page exactly. If it doesn't match, delete the file and download again — do not extract it.
5. Extract the archive.
Right-click the .7z file and extract it with 7-Zip. Expect: a folder containing a .vbox file and a large .vdi disk image.
6. Add the VM to VirtualBox.
Open VirtualBox, click Add (the machine menu, not File → Import Appliance), and select the .vbox file from the extracted folder. Expect: the VM appears in the left-hand list.
If your download extracted to a single .ova file instead of a .vbox + .vdi pair, use File → Import Appliance and select the .ova. Kali ships the prebuilt image in either form depending on the release; the rest of this guide is the same once the VM is in the list.
7. Check the allocated resources.
Right-click the VM, open Settings, then System → Motherboard for RAM and System → Processor for CPU cores. Keep RAM at or below half your host's total, and leave at least two cores for the host. Expect: the sliders stay in the green range.
8. Start the VM.
Select it and click Start. Expect: a boot sequence, then the Kali login screen.
9. Log in.
Use the default credentials, kali / kali. These are specific to Kali's prebuilt VM image — a Kali installer ISO sets its own credentials during install instead.
Verification
The VM boots to the Kali desktop and the terminal opens. Run this inside the VM:
ip a
You should see an interface with an address, confirming networking works. A VM that boots but has no network is only half-configured.
If the desktop is stuck at a small resolution or clipboard sharing doesn't work, the Guest Additions version in the image doesn't match your VirtualBox. It's not a failure — the VM is running. Reinstalling Guest Additions from the VirtualBox Devices menu fixes the display and clipboard when you want them.
Troubleshooting
VirtualBox only offers 32-bit options, or the VM fails to start.
Hardware virtualization is disabled. Reboot into BIOS/UEFI and enable VT-x (Intel) or AMD-V (AMD). The setting is usually under CPU or Advanced.
The VM starts but is extremely slow, or throws a VT-x error on Windows 11.
Hyper-V is holding the virtualization layer, and VirtualBox can't use it at the same time. Disable Hyper-V, Windows Hypervisor Platform, and Virtual Machine Platform in "Turn Windows features on or off," then reboot. Memory integrity under Windows Security → Device security → Core isolation also enables Hyper-V silently; turn it off too.
The checksum doesn't match.
Delete the file and download it again. A mismatch means the download was corrupted or the file was tampered with. Do not extract or import it either way.
The extraction fails or the folder looks incomplete.
Extract to a path with no spaces or non-English characters, and make sure you have twice the archive size free — 7-Zip needs room for both the archive and the expanded disk image.
Closing
The point of the VM is separation. Anything you install, break, or get compromised by inside Kali stays inside Kali, and the host system is never touched.
Drafted and revised with Claude; every step tested by me.
Top comments (0)