6.1 Minimal Installation Requirements

6.1 Minimal Installation Requirements

Quick Answer: A hard-disk installation of Kali Linux needs a 64-bit (amd64) machine with at least 2 GB of RAM and 20 GB of disk space; 8 GB of RAM and 60 GB or more is realistic for daily use. Build bootable media with dd, balenaEtcher, or Rufus in DD image mode, and disable Secure Boot on UEFI systems before you start.

Kali Linux is a complete Debian-based distribution, not a lightweight live-only toolkit, so it has the same kinds of hardware expectations as any modern desktop Linux. The good news is that the requirements are modest, and the default Xfce desktop keeps the base system responsive even on older hardware. Before you download anything, confirm that your target machine matches the baseline below.

Hardware Baseline

RAM. The 2 GB figure covers the default Xfce desktop plus the kali-linux-default metapackage; at the low end a headless, SSH-only Kali installs in as little as 128 MB of RAM (512 MB recommended) and 2 GB of disk, and the exam does ask for that lower tier. Two gigabytes is enough to complete the graphical installer and run a default desktop, but real workloads grow quickly: Burp Suite is a Java application, Wireshark captures can balloon, and running Metasploit with its PostgreSQL database adds steady overhead. If the machine will also host a target VM, 16 GB is not excessive.

Disk space. Twenty gigabytes fits the base system plus the kali-linux-default toolset, but little else. Wordlists, extra metapackages such as kali-linux-large, snapshot-style backups, and ordinary package updates all consume space. Sixty to eighty gigabytes on an SSD is a comfortable working figure.

Architecture. The mainstream installer and live images on kali.org are 64-bit x86 (amd64); kali.org additionally publishes arm64 installer and live ISOs for UEFI-based ARM machines such as Apple Silicon virtual machines. Do not try to boot the amd64 ISO on a Raspberry Pi or other ARM board — ARM devices use dedicated prebuilt images, covered in section 6.4. Confusing the amd64 installer with ARM images is a classic exam trap.

Verify the Download First

Never install from an unverified ISO. After downloading from kali.org, compute the checksum and compare it with the value published on the download page:

sha256sum kali-linux-2026.2-installer-amd64.iso

If the hash does not match exactly, discard the file and download again — a corrupted or tampered image produces bizarre installer failures that waste far more time than a re-download. Kali signs its repositories with GPG, and checksum verification is the equivalent integrity check for the installation media itself.

Creating Bootable Installation Media

You have three mainstream options; know all three for the exam.

Option 1: dd (Linux and macOS)

First identify the USB device — writing to the wrong device will destroy that disk's data without warning:

lsblk                       # Linux: find the USB device, e.g. /dev/sdb
diskutil list               # macOS: find it, e.g. /dev/disk4

Unmount any auto-mounted partitions, then write the image to the whole device, not a partition:

sudo dd if=kali-linux-2026.2-installer-amd64.iso of=/dev/sdb bs=4M status=progress conv=fsync

Three details matter here. of=/dev/sdb targets the entire disk — of=/dev/sdb1 writes into a partition and produces unbootable media. status=progress shows a live progress meter so you are not staring at a silent prompt. conv=fsync flushes writes to the physical device before dd exits, so the stick is actually complete when you pull it. On macOS, using the raw device /dev/rdiskN instead of /dev/diskN is significantly faster, and you should run diskutil unmountDisk /dev/diskN first.

Option 2: balenaEtcher (Windows, macOS, Linux)

balenaEtcher is a free cross-platform GUI: select the ISO, select the USB target, click Flash. It validates the write automatically, which makes it the safest choice for beginners and the tool least likely to produce silently corrupt media.

Option 3: Rufus (Windows) — the DD-Mode Trap

When you write a Kali ISO with Rufus, it prompts you to choose between ISO image mode and DD image mode. You must choose DD image mode. ISO mode rearranges the image contents in a way that frequently produces media that fails to boot or fails mid-install. This is one of the most commonly tested media-creation facts.

UEFI, Secure Boot, and Booting the Media

Kali's installer boots on both legacy BIOS and UEFI (Unified Extensible Firmware Interface) systems, but one firmware feature will stop you cold: Secure Boot. Kali does not support Secure Boot, so you must disable it in the firmware setup utility (typically reached with F2, Del, or F12 during power-on). With Secure Boot left enabled, the machine will refuse to boot the Kali media, sometimes with only a cryptic signature error.

Practical boot sequence:

1. Power on and open the one-time boot menu (F12, Esc, or F9 depending on vendor).
2. Select the USB entry — on UEFI systems prefer the entry prefixed with UEFI: so the install lands in UEFI mode.
3. If the machine dual-boots Windows with BitLocker, suspend BitLocker before changing firmware settings or you may trigger a recovery-key prompt.

Exam traps to remember: Rufus in ISO mode instead of DD mode, Secure Boot left enabled, dd pointed at a partition (sdb1) instead of the disk (sdb), and attempting to use the amd64 ISO on ARM hardware.