Kali Linux on WSL2: Complete Setup Guide 2026 (Install, Win-KeX & Config)

Full Kali Toolset on Windows

Install nmap, Metasploit, Burp Suite, hashcat, BloodHound, and the rest through Kali's own apt repository — no manual porting, no Cygwin, no missing dependencies.

Near-Zero Overhead

The WSL2 VM starts in a second and consumes only what its processes use. You keep Windows as your daily driver and drop into Kali in the same taskbar.

Seamless File Interop

Reach Windows files at /mnt/c from Kali and reach the Kali filesystem at \\wsl$\kali-linux from Explorer. Pipe output between the two worlds freely.

Optional Linux Desktop

Win-KeX layers a full XFCE desktop on top of the WSL instance in window, seamless, or RDP-backed enhanced-session mode when a GUI tool needs a real display.

Disposable Lab Instances

Export a configured Kali to a tarball and re-import it in seconds. Snapshot before a messy engagement, roll back after, or clone identical instances per project.

VS Code Native Dev

The VS Code WSL extension runs its server inside Kali, so you edit and debug exploit code and scripts with Linux paths and Linux Python while the editor UI stays on Windows.

This installs the WSL platform and its kernel. Passing --no-distribution installs the engine only, so you can then choose Kali explicitly rather than the default Ubuntu.

Reboot if the installer asks. After the reboot, WSL2 is the default backend on Windows 11; on Windows 10 confirm it in the next step.

Force version 2 as the default so any distro you install runs on the real kernel, then list what Kali images are available online.

Pull and register the official Kali WSL image. The download is deliberately small — the base image ships with almost no tools so it stays lightweight; you add metapackages later.

The first launch runs Kali's setup, which prompts for a non-root username and password. That account is added to sudo. Launch Kali by name from Windows Terminal or run it from PowerShell.

WSL2 needs both the WSL feature and the Virtual Machine Platform. Enable them with DISM (works everywhere) or the PowerShell equivalent, then reboot.

On older Windows 10 the in-box kernel is out of date or missing. Download and run the standalone kernel update package, then pin WSL2 as the default.

• 1
  Download the kernel MSI from https://aka.ms/wsl2kernel and run it as administrator.
• 2
  On modern Windows, prefer wsl --update instead — it fetches the Store-based kernel automatically.

With the features on, install Kali from the Microsoft Store app, or sideload the appx package on machines where the Store is present but you prefer the CLI.

For a truly disconnected build, export an already-configured Kali from another machine to a tarball, copy it across, and import it into a chosen folder. This is also how you relocate an instance off the system drive.

Win-KeX ships as the kali-win-kex package. Update first, then install. Do this inside the Kali shell, not PowerShell.

Window mode opens the full XFCE desktop in a single, resizable window. The -s flag adds sound support. The first run prompts you to set a VNC password used for the local display session.

Seamless mode drops the desktop shell and floats individual Kali windows directly on your Windows desktop, so a tool like Wireshark appears as if it were a native app.

Enhanced Session Mode (ESM) delivers the desktop over RDP for a richer, higher-fidelity experience similar to Hyper-V enhanced sessions. The --ip flag is the documented ARM workaround; keep -s for sound.

To shut a session down, close the Win-KeX window, or from the Kali shell run kex --stop. Use kex --help to see every flag your installed version supports.

If you also want containers, install Docker Desktop for Windows and enable its WSL2 integration. Docker then runs its engine in the shared WSL2 backend and exposes the docker CLI inside Kali — no Docker install inside Kali required.

• 1
  Install Docker Desktop, then open Settings → General and confirm "Use the WSL 2 based engine" is ticked.
• 2
  Open Settings → Resources → WSL Integration and toggle on kali-linux.
• 3
  Restart Docker Desktop, then test the CLI from within Kali.

Always fully update on first launch — the base image lags the repo. Then set the root password (needed for a few tools) and, if you imported and are stuck as root, create a proper user.

The WSL image is intentionally bare. Metapackages pull in curated tool bundles. Pick based on disk budget: default matches the standard Kali image, large adds far more, headless skips GUI apps (ideal for a console-only WSL box), and everything is enormous.

You can always cherry-pick. Kali packages the whole offensive catalogue, so a headless box plus a handful of named tools is often the leanest setup.

Fix the small things that cause noisy warnings: locale, timezone, and confirming ZSH (Kali's default shell) is active for your user.

Left unbounded, WSL2 will claim a large share of RAM. Create .wslconfig in your Windows user profile to cap it. Edit from Kali via the /mnt/c path or from Windows in Notepad.

Modern WSL supports systemd, which many Kali services (PostgreSQL for Metasploit, Docker-in-Kali, bluetooth, ssh) expect. Turn it on in /etc/wsl.conf and, if you imported as root, set your normal user as the default login.

If DNS resolution breaks after editing configs (a common symptom of a stale /etc/resolv.conf), confirm the setting and let WSL regenerate it.

Installing Kali auto-adds a Windows Terminal profile. Set it as your default or bind a hotkey so Kali is one keystroke away.

• 1
  Open Windows Terminal → Settings (Ctrl+,) → Startup → set default profile to Kali if you like.
• 2
  Under the Kali profile → Appearance, pick a scheme; the "Kali" preset ships with recent Terminal builds.
• 3
  Launch a specific working directory: wsl -d kali-linux --cd ~.

The VS Code WSL extension runs the editor's backend inside Kali, so extensions, the integrated terminal, the debugger and Python all use the Linux environment while the window stays on Windows.

• 1
  In Windows VS Code, install the WSL extension (publisher: Microsoft).
• 2
  From a Kali shell, change into a project and launch the editor bound to Kali.

Windows drives mount under /mnt inside Kali; the Kali filesystem is reachable from Explorer via the \\wsl$ UNC path. Use them to move loot, wordlists and reports between the two sides.

With interop enabled, you can call Windows executables from Kali. This is handy for opening report artifacts or pushing text to the Windows clipboard.

WSL2 does not expose the host Wi-Fi radio, so wireless auditing needs an external adapter passed through with usbipd-win. Install it on Windows, then bind and attach the device to Kali.

Default NAT gives Kali its own subnet, which complicates reverse shells and inbound listeners. Mirrored mode makes WSL share the host's network interfaces and IPs, so a listener on Kali is reachable at the Windows IP.

WSL2 supports GPU compute passthrough. With a current NVIDIA or AMD Windows driver installed, hashcat inside Kali can use the GPU with no extra driver install inside Linux — the vendor driver is projected in.

Update the distro from inside Kali and the WSL engine from Windows. Snapshot before risky work by exporting the whole instance to a tarball you can re-import.

The ext4.vhdx grows as you install tools but does not shrink when you remove them. Reclaim space by compacting it. With sparseVhd enabled (Phase 07) WSL reclaims some automatically; for a manual compaction use one of the following.

The overwhelming majority of WSL2 problems come from a handful of causes: features not enabled, virtualization off, a stale kernel, or config typos. This table maps the message you see to the fix.