Most Kali Linux install failures are not Kali problems. They are one wrong VM setting, a skipped network step in the installer, or GRUB written to the wrong place. This guide walks the full installation in the order that avoids those errors: download, verify, build the VM, install, update, snapshot.
Kali Linux inside VMware is the standard way professionals build a security lab: your real PC stays untouched, and the lab can be paused, copied or rolled back at any time. The video above shows this exact installation live. Below is the same route in writing, with the honest reasons behind each setting - including the two or three places where most first-time installs actually fail. Kali Linux is a professional security testing system. Use it only on computers and networks you own, or where you have clear written permission to test. That one rule is what separates a security professional from a criminal.
Kali is a security tool, so the copy you download matters more than with any other system. Download the installer ISO only from the official site, kali.org - never from a random mirror, torrent or "pre-activated" pack.
certutil -hashfile kali-linux-installer.iso SHA256A mismatch means the file is corrupt or tampered with. Delete it and download again. Installing from an unverified copy of a security distribution defeats the entire point.
In VMware Workstation choose Create a New Virtual Machine, point it at the Kali ISO, and set the guest operating system to Linux - Debian 64-bit (Kali is built on Debian; there is no "Kali" entry and none is needed). Then set:
Also make sure virtualization (VT-x or AMD-V) is enabled in your host BIOS or UEFI, or no 64-bit guest will start at all.
Power on the VM and choose Graphical install. Language, location and keyboard are personal preference. The screens that decide success or failure are these:
When the installer asks about a network mirror, say Yes and accept the default Kali mirror. This step downloads the package lists and any missing pieces, and it is the screen most people panic on.
If it fails, the cause is almost never the mirror itself - it is that the VM had no working network at that moment. Check the VM is on NAT, that your host PC is online, then go back one step and retry. If it still fails, you can continue without the mirror and repair the package sources after the first boot; the dedicated mirror guide on this channel's site covers that path in depth.
Near the end, the installer asks where to install the GRUB boot loader. The correct answer for a normal VM is the whole virtual disk - shown as /dev/sda - not a partition like /dev/sda1.
Choosing a partition is the classic reason a "successful" install reboots into a black screen or a grub rescue prompt: the firmware looks at the start of the disk, finds no boot loader there, and stops. Pick the disk, let the installer finish, and remove the ISO from the virtual CD drive when it reboots.
Log in with the user you created. The graphical tools, clipboard and screen resizing come from open-vm-tools, which the Kali installer sets up for a VM automatically. Now do the one big housekeeping job before touching any security tool:
sudo apt updatesudo apt full-upgrade -y and let it finish - the first upgrade is large, this is normalThat snapshot is your undo button for the whole lab. Whatever you break later while learning, you are thirty seconds away from a clean machine again.
Every screen of the Kali Linux VMware installation, shown live step by step.
Watch Full VideoYes. Kali Linux is completely free and open source, maintained by Offensive Security. Download it only from kali.org so you know the copy is genuine.
The documented floor is about 2 GB of RAM and 20 GB of disk, but that is a minimum, not a comfortable setup. 4 GB of RAM, 2 CPU cores and 40 GB or more of disk is the honest recommendation for learning without frustration.
The most common cause is GRUB installed to a partition instead of the whole virtual disk, or the ISO still attached confusing the boot order. Reinstall GRUB to /dev/sda from the installer rescue mode, and detach the ISO before rebooting.