Kali Linux GRUB Boot Loader Install Failed or PC Boots to Grub Rescue
The install reaches 100 percent, you reboot - and instead of a Kali login you get a black screen, a blinking cursor, or the dreaded grub rescue prompt. Nine times out of ten, the boot loader was written to a partition instead of the disk. Here is the honest explanation and the recovery.
Technical AnshuVMware WorkstationBoot fix
Watch the full video - the GRUB step is shown in the install walkthrough
GRUB is the small program that starts Linux. The Kali installer asks where to put it, and that single answer decides whether the machine boots or stalls before Kali even begins. This page covers choosing the right target during install, and what to do if you are already staring at a rescue prompt. 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.
The one choice that decides whether the VM boots
Installer asks .... "Install the GRUB boot loader to:"
WRONG .............. /dev/sda1 (a partition - firmware never looks there)
RIGHT .............. /dev/sda (the whole virtual disk)
Result of wrong .... black screen or grub rescue> after reboot
Always the disk, never a partition, for a normal single disk VM
1
Why the Disk, Not the Partition - the Simple Picture
When a computer (or VM) powers on, its firmware looks at the very start of the disk for boot code. It does not look inside partitions. Installing GRUB to /dev/sda puts that code exactly where the firmware searches.
Installing GRUB to /dev/sda1 writes perfectly good boot code to a place nothing checks at power-on. The install reports success, the reboot fails. Same software, wrong address - that is the whole mystery.
2
Getting It Right During Installation
At the GRUB step, when asked whether to install to the master boot record / primary drive, confirm Yes
On the device list, select the entry that is the whole disk - typically /dev/sda - not any numbered partition under it
In UEFI mode, the installer instead writes to the EFI system partition automatically; let it, and do not force a device by hand unless you know why
In a VMware VM with one virtual disk there is exactly one correct answer, which is why this step should be boring. If it is not boring, stop and re-read the device names slowly.
3
Already at grub rescue? The Recovery Path
If the VM already boots to grub rescue>, the cleanest fix for a fresh install uses the Kali ISO you already have:
Attach the ISO to the VM again and boot from it
From the installer boot menu, choose the Advanced options and then Rescue mode
Follow the prompts, select your installed root partition when asked, and choose the option to reinstall the GRUB boot loader
Give it the whole disk - /dev/sda - as the target
Reboot, and detach the ISO
Honest shortcut: if the install is ten minutes old and holds nothing you care about, reinstalling and choosing the disk this time is often faster than rescue mode. Both are legitimate; pride is the only reason to refuse the reinstall.
4
The Other Boot Blockers That Look Like GRUB Failure
Before deep surgery, rule out the look-alikes:
The ISO is still attached and the VM keeps booting the installer instead of the disk - detach it or fix the boot order
Firmware was switched between BIOS and UEFI after installing - GRUB was written for one mode and the VM now starts in the other
Secure Boot is enabled on the VM or host path and is rejecting the boot loader - for a learning VM, leave virtual Secure Boot off
The snapshot was taken mid-install - reverting to it restores a half-written disk
5
Preventing It Next Time
Two habits make this whole page unnecessary. First, slow down at exactly one screen - the GRUB target - and read the device name out loud. Second, after the first successful boot, take the clean snapshot immediately, before updates and experiments. A boot problem that appears later is then a thirty-second revert, not a rescue operation.
Honest note: dual-booting Kali on a real PC alongside Windows is a different and riskier conversation, where GRUB choices can affect the other system. Inside a VM - the setup this guide covers - the disk is disposable and the rules above are all you need.
Watch the Complete Installation in the Video
Every screen of the Kali Linux VMware installation, shown live step by step.
It is GRUB's emergency shell. GRUB started, but could not find its configuration or the system it was supposed to boot - most often because it was installed to a partition, or its files were moved or damaged.
I installed GRUB to /dev/sda but the VM still will not boot. What next?
Check the look-alikes first: ISO still attached, firmware mode changed after install, or Secure Boot rejecting the loader. If all are clean, use rescue mode from the ISO to reinstall GRUB, which rebuilds both the code and its configuration.
Does reinstalling GRUB delete my Kali system or files?
No. Reinstalling the boot loader only rewrites the small boot code and its menu. Your installed system, user account and files are untouched.
This guide is based on the Technical Anshu Kali Linux on VMware video - Stuck on a step? Ask in the video comments - you will get a reply