How to Install Kali Linux in VirtualBox: Complete Setup Guide

Installing Kali Linux in VirtualBox takes one 3.9 GB download, a single extraction, and six settings that decide whether the desktop fills the window. The install is rarely what fails. What fails sits outside it, in the firmware setting nobody opened, the Windows feature still holding the processor, or the guest tools that never arrived, and each of those has a check that names it in under a minute.

What a Kali VirtualBox VM Actually Gives You

A Kali virtual machine is the whole distribution in a file, isolated from your host, with snapshots you can roll back. Kali ships two ways to reach that file, and the difference is who does the configuring. The pre-built VirtualBox image already has the desktop, the tool set, and the guest tools applied, so getting in is a file copy rather than an installation.

The ISO installer instead asks you for a hostname, a partition layout, a desktop environment, and a tool metapackage, then spends half an hour pulling packages over the network. Both paths produce the same rolling distribution on the same kernel.

If you have only used containers so far, a virtual machine is a different isolation model. I checked the release page, and the pre-built archive and the installer carry the same 2026.2 version, so neither download is out of date.

The costs are concrete. The guest shares your host’s processor and memory, hardware access goes through VirtualBox rather than directly, and your WiFi adapter stays with the host unless you pass it through on purpose. Snapshots are the reason to accept that trade, and one taken after the first login turns a broken tool into a ten second rollback.

What You Need Before You Start

VirtualBox 7.2.16 is the current release, and Kali Linux 2026.2 is the current point release, which I confirmed from kali.org/get-kali and the VirtualBox download page. The version sits in the filename, so a Kali image dated 2025 is the previous one. Kali also needs a 64-bit processor with hardware virtualization, and that feature is usually present in the chip but switched off in firmware.

On Windows a second thing holds the same hardware. Hyper-V, the Virtual Machine Platform feature, Credential Guard, and Device Guard all take the virtualization extensions for the Windows hypervisor, and VirtualBox cannot have them while any of those is on. The error you get in that case names the processor feature, not the Windows feature that owns it, which is why the search results look unhelpful.

On Linux the processor reports the capability directly.

lscpu | grep -i virtualization

A line reading VT-x or AMD-V means the extensions are available to VirtualBox. A missing line means they are switched off, and the firmware menu is where you turn them on. On Windows, Task Manager reports the same fact under Performance, then CPU, as Virtualization: Enabled or Disabled.

Secure Boot is worth checking at the same time. Kali’s kernel is unsigned and Secure Boot refuses to load it, so disabling Secure Boot is a firmware setting you change rather than anything inside the guest.

Kali’s own documentation sizes the default build at 2 GB of RAM and 20 GB of disk, or 8 GB once you run something like Burp Suite. Its release images use an 80 GB dynamically allocated VDI, which only consumes host space as the guest fills it.

Download Kali 2026.2 from kali.org/get-kali: the VirtualBox card gives you kali-linux-2026.2-virtualbox-amd64.7z, and the installer card gives you the ISO. Extract the archive with 7-Zip, which is a package on Linux and a download on Windows.

How to Install Kali Linux in VirtualBox

The pre-built path is four steps and no installer at all. The ISO path is longer, and it is the one to take when the image does not give you the layout or the package set you need.

Import the Pre-Built Kali Image

Verify the archive before you unpack it, because a truncated download and a corrupted one look identical once the extraction starts. The checksum below is the one kali.org publishes for 2026.2, and I checked it against the same value in the mirror’s own SHA256SUMS file, so a mismatch here is your download rather than a stale page.

sha256sum kali-linux-2026.2-virtualbox-amd64.7z

Then extract it. On Linux, 7z comes from the p7zip package and works with or without the full 7-Zip client. On Windows, right-click the archive and choose Extract Here.

7z x kali-linux-2026.2-virtualbox-amd64.7z

I extracted this archive and got a 3 KB .vbox and a 16 GB .vdi, and nothing else. The .vbox is the machine definition and the .vdi is the virtual disk, and only the .vbox has to be registered.

In VirtualBox choose Machine, then Add, and point it at the .vbox file.

Boot the machine and log in with kali as both the username and the password. Change that password on the first login, before the guest is attached to a network you do not control.

Install From the ISO Instead

Start a new machine with Machine, then New. Set Type to Linux and Version to Debian (64-bit) because VirtualBox has no Kali entry, and the distribution is Debian underneath. Attach the ISO when the wizard offers it, and decline the unattended install, which writes its own answers and skips the desktop and metapackage choices.

Partitioning is the other decision. Guided, using the entire disk, is correct for a virtual machine, because the disk is a file you can throw away. If you want to plan that part properly, the partitioning and filesystem guide covers the manual layout.

The VirtualBox Settings That Decide Whether Kali Is Usable

Defaults will boot Kali, but they will not make it comfortable. I compared the settings Kali publishes for its own VirtualBox images against a default machine, and the table is that list with one addition for the network.

Accelerated 3D is the setting people change for the wrong reason. Turning it on to chase a smoother desktop is a common move, and Kali’s own guest guide asks for it to stay off because it produces rendering faults. The symptom of getting this wrong is a desktop that flickers, draws half of a window, or refuses to repaint at all, and turning the setting back off fixes it.

Install the Guest Tools So the Desktop Fits

Without the guest tools the Kali desktop stays at a fixed 800×600 whatever size the window is, the clipboard does not cross between host and guest, and shared folders do not mount. Kali has installed the tools automatically since 2019.3, so on a healthy machine this step is already done.

When it is not done, or when a kernel upgrade has broken it, force the reinstall.

sudo apt update
sudo apt install -y --reinstall virtualbox-guest-x11
sudo reboot -f

The package is virtualbox-guest-x11 and it is built against the running kernel, which is why a kernel upgrade can leave the desktop broken with no error anywhere. Re-running the same three commands is the repair, and if apt itself refuses to finish, a dpkg error code 1 is the usual cause.

Share Folders and the Clipboard With Your Host

Once the guest tools are working, set Shared Clipboard and Drag and Drop to Bidirectional in Settings, General, Advanced. The clipboard only crosses while the guest tools are installed, so this settings change on its own does not do anything.

For a folder, open the running machine’s window and choose Devices, then Shared Folders. Add the host folder and give the share a short name, then mount it inside Kali.

sudo mkdir -p /mnt/share
sudo mount -t vboxsf sharename /mnt/share

To mount the same folder at every boot, add the entry to the fstab file, which takes the shape of the share name, the mount point, the vboxsf filesystem, and the word defaults. Mounting a host drive from Linux covers the same idea for a fixed disk.

sharename /mnt/share vboxsf defaults 0 0

Fix the Failures That Stop the Install

Five failures account for most of the dead ends people hit, and four of them name themselves before you change anything. The fifth one is not a failure at all.

The green turtle deserves a longer note, because it is the one failure that looks like performance rather than a fault. It means VirtualBox is running the guest through software emulation, and no amount of RAM or processor allocation helps while it is there. I read the whole thread on that error, and the reporter cleared it only after disabling Hyper-V, Credential Guard, and Device Guard, toggling virtualization in firmware, and accepting two prompts on the next boot.

The missing WiFi adapter is the other one worth understanding rather than fixing. VirtualBox gives the guest an emulated network adapter attached to a NAT or bridged network, which is enough for updates, package installs, and anything that talks over IP.

It is not enough for wireless scanning, because there is no radio in the guest to put into monitor mode. For that you pass a physical adapter through from Devices, then USB, and install its driver inside Kali, and if networking rather than wireless is what is broken, the DNS and networking guide is the faster route back.

Snapshot, Update and Clone Your VM

A Kali virtual machine is a fixed point release of a rolling distribution, so it starts one update behind whatever the archive holds today, and the first login is the moment to capture that state rather than to start installing tools. A snapshot costs nothing, and a tool that breaks the system becomes a rollback instead of a rebuild.

• Take a snapshot from Machine, Tools, Snapshots so a wrecked guest is a rollback rather than a reinstall
• Run apt update followed by apt full-upgrade inside the guest to move the point release onto the current archive
• Clone the machine from Machine, Tools, Clone when you want a second lab without repeating the setup
• Keep copies of the VM folder outside the snapshots, because a snapshot is stored beside the disk it protects

For a machine you intend to keep, exporting it as an appliance gives you a single file you can move to another host, which is a different job from a snapshot. When you are ready to go further inside Kali, the command reference is the next step rather than more work on the virtual machine itself.

Of everything here, the firmware check is the one I would do first, because every other setting is recoverable and a processor that never got its virtualization extensions switched on is why most of these machines never start.

Frequently Asked Questions