- Published on
Fix Kali Linux Black Screen Blinking Cursor on Boot (VMware/VirtualBox)
Quick Answer: Kali Blinking Cursor Fix
Kali boots in a VM, the screen goes black, and a blinking cursor remains. This is a common Kali Linux boot issue in VMware or VirtualBox, and the fix is short and direct.

The fix is compact. The overview comes first, followed by the full step-by-step walkthrough with screenshots.
Quick Fix Overview (TTY + startx)
- Switch to a TTY login screen with
Ctrl+Alt+F2(orF3,F4,F12depending on the keyboard layout). - Log in.
- Run
sudo startxand enter your password.
That is the overview. The detailed walk-through with screenshots follows.
Step 1: Jump to a TTY Login Screen
When the cursor shows up, press Ctrl + Alt + F2 (if that does not work, try F3 or F12).

You should land on a text login screen.
Step 2: Log In
Use the existing Kali username and password.

Once you log in, you will see a terminal prompt.
Step 3: Start the Desktop Manually (startx)
Run this command:
sudo startx
Then enter the password again.

Back to the Desktop
The GUI should load normally.

Why This Works (Short Version)
The blinking cursor typically means the display manager did not finish starting the desktop session. startx manually starts the graphical session and restores the desktop.
If the issue comes back after reboot, this fix still works, but it can indicate the display manager needs attention. This section focuses on the fastest recovery.
Common Causes of the Kali Blinking Cursor
- The display manager fails to start the graphical session after boot.
- The VM graphics stack does not initialize cleanly.
- A driver or update leaves Xorg in a half-started state.
This guide focuses on the fastest recovery. A permanent fix typically involves display manager repair and VM graphics settings.
FAQ
Does this work on bare metal Kali Linux? It can, but this specific boot issue is most common in VMware and VirtualBox.
Is startx safe to run? Yes. It starts the graphical session manually when the display manager fails.
Will I need to do this every boot? Not always, but repeated failures usually point to the display manager or VM graphics configuration.