Skip to content
Kali Linux / VMware

Install Kali Linux on VMware Workstation

Build a manageable learning VM, understand the network choices and verify the installation before using it for authorised lab work.

By Zahid Rafiq · Revision prepared October 2026

Revision scope: the original walkthrough used VMware Workstation 15 in 2021. This revision explains a current installation approach without claiming it has been tested on your hardware. Installer screens and release names can change.

1. Choose your installation route

There are two useful ways to start: import an official prebuilt VMware image, or install from an ISO. A prebuilt image is quicker; the ISO route gives you a closer look at the installation and disk choices. This guide focuses on the ISO route.

Download from the official Kali website. For the ISO route, choose an installer image that matches your host architecture. Compare its SHA256 checksum with the value published for that release before using it.

Get-FileHash -Path 'C:\Downloads\your-kali-installer.iso' -Algorithm SHA256

The output should match the official checksum for that exact file. A matching checksum confirms the file agrees with the published value; obtain that reference through the official source.

2. Prepare the virtual machine

Confirm that hardware virtualisation is enabled on your host and that you have enough free disk space. Close unneeded applications if the host has limited memory.

Create a new VM in VMware Workstation. Select the ISO as installation media and choose the Debian 64-bit Linux guest type where offered for an amd64 Kali installer; follow Kali’s documentation for the release you download. Do not select Ubuntu simply because both are Linux distributions.

For a modest desktop learning lab, I suggest beginning with 2 virtual CPUs, 4 GB of RAM and a 40 GB virtual disk, provided your host can comfortably spare those resources. These are planning suggestions, not minimum requirements or measured performance guarantees.

Give the VM a clear name, such as Kali-Lab, and store its files where you can find and back them up. A dynamically allocated disk still needs real host space as it grows.

3. Choose the network deliberately

ModeWhat it meansUseful context
NATThe VM usually reaches external networks through the host’s translated connection.A convenient starting point for downloading packages. It does not isolate the VM from every reachable network.
Host-onlyA private virtual network generally shared with the host and other attached VMs.Useful for a local lab. The host remains reachable, so this is not a complete security boundary.
BridgedThe VM connects to the physical network as another device.Use only when the lab requires it and you understand which systems the VM can reach.

Start with NAT for installation and updates unless you have a reason to use another mode. For lab exercises, place test machines on a deliberately configured virtual network and check their reachability. A virtual machine’s network setting does not authorise testing of other systems.

4. Run the installer

  1. Power on the VM and choose the graphical installer if available.
  2. Select your language, location and keyboard layout.
  3. Choose a hostname such as kali-lab. Leave the domain blank unless your lab requires one.
  4. Create a normal user account and choose a unique password.
  5. At partitioning, confirm that the selected disk is the new virtual disk.
  6. For a simple fresh VM, guided partitioning using the whole virtual disk is a straightforward option. Review the proposed layout before writing changes.
  7. Select the desktop and tool collection you need. Installing every available tool is usually unnecessary for an introductory lab.
  8. Install the boot loader on the VM’s boot disk when prompted, then finish the installation and reboot.

The important check at partitioning is the target disk, not just the button label. Only proceed with a disk you created for this VM. After installation, disconnect the ISO or adjust the boot order if the installer starts again.

5. Verify the installation

Log in with the account you created. Check the OS information, network addressing and name resolution before assuming package installation will work:

cat /etc/os-release
ip -brief address
ip route
getent hosts kali.org

You should see the intended distribution, an address appropriate to the selected virtual network and a working route if you expect internet access. Name resolution can fail even when basic IP connectivity works.

Update packages

sudo apt update
sudo apt full-upgrade

Review the proposed package changes and available space before accepting the upgrade. Reboot when required and confirm that the system returns to the desktop.

Check guest integration

Guest integration helps with display resizing and other VMware features. If those features are missing, follow Kali’s current open-vm-tools instructions rather than downloading an arbitrary tools archive.

dpkg -l open-vm-tools open-vm-tools-desktop

This is a package-state check. The package names alone do not prove that clipboard, display or other integration features are working; verify the feature you need in the running desktop.

Take a clean baseline snapshot

Once the VM boots correctly, updates are complete and networking behaves as expected, shut it down and take a clearly named baseline snapshot. Record the Kali release, VMware version and network mode in your lab notes.

A snapshot makes it easier to return to an earlier VM state after an exercise. It is not a substitute for a separate backup of files you need to keep.

Troubleshooting

The VM will not start or reports a virtualisation error

Check the host’s virtualisation support, firmware setting and VMware compatibility. Read the exact error before changing host features; requirements vary with the host and VMware release.

The installer appears after every reboot

Confirm that installation completed, disconnect the ISO and check the VM’s boot order. If the disk is still not bootable, review the boot-loader installation.

Package updates fail

Check the chosen network mode, IP address, default route and DNS resolution. Also check disk space and the repository configuration before repeatedly retrying the update.

The desktop is slow or the display is too small

Check host resource pressure and guest integration. Increase resources only when the host has capacity, and verify the outcome rather than assuming more CPU or RAM will fix every issue.

References and revision notes

This revision adds a checksum check, explains network choices and separates installation from validation. It does not include new screenshots or a claim of firsthand testing; those should be added after running the updated lab.