Which AI Tools Setup Path Wins on Windows

Video: How to Install Linux AI Tools on Windows (WSL) + Fix 5 Common Errors

Oct 19, 2026 · based on the channel Unstuck

AI Tools that ship as Linux binaries are best run on Windows through WSL, because the Windows Subsystem for Linux gives you a real Ubuntu userland where `curl ... | sh` installers work unchanged, while native Windows ports often lag behind or do not exist at all. The practical path is: enable WSL, install Ubuntu, add the missing `unzip` package, repair DNS, then log in to the tool. The walkthrough below follows the same sequence used in the Unstuck breakdown, and if you get stuck on a specific error message you can paste it into the early-access helper at Unstuck early access to get a plain-language fix.

Why AI Tools installers ask for WSL instead of Windows

Most AI Tools distributed as command-line utilities target Linux and macOS first, and their install scripts assume a POSIX shell, `curl`, and standard archive tools. When an installer prints "Windows is not supported. Use WSL.", it is not a bug — the vendor simply has not built a native Windows binary. Composio CLI is the example used in the video, but the same rule applies to a large share of agent frameworks, MCP servers, and Python-based AI utilities that ship a one-line shell installer. WSL 2 runs a genuine Linux kernel in a lightweight virtual machine, so the installer sees Ubuntu, not Windows, and the tool behaves exactly as it would on a Linux server. The alternative — hunting for unofficial Windows builds or running everything inside Docker Desktop — adds moving parts without removing the Linux dependency.

Step 1: Enable WSL and clear error 0x80370102

Installing WSL takes one command from an elevated shell. Open PowerShell as Administrator and run `wsl --install`; on current Windows builds this enables the Virtual Machine Platform and WSL features and pulls Ubuntu as the default distribution. Reboot if prompted. If the install fails with error 0x80370102, the cause is almost always hardware virtualization disabled in BIOS/UEFI or a missing Virtual Machine Platform component. Check that Intel VT-x or AMD-V (SVM) is enabled in firmware settings, confirm the "Virtual Machine Platform" and "Windows Subsystem for Linux" optional features are ticked in "Turn Windows features on or off", then retry. On machines where Hyper-V is blocked by another hypervisor, disabling that conflicting layer resolves the same code.

Step 2: Finish Ubuntu setup and add unzip

A fresh Ubuntu install needs its package index refreshed and one commonly missing utility added. After creating your UNIX username and password, run `sudo apt update && sudo apt install -y unzip`. The `unzip` package matters because many AI Tools installers download a zipped release and unpack it silently; without it the script dies midway with a confusing error rather than a clear "missing dependency" message. Installing it up front saves a debugging round.

Step 3: Fix "Could not resolve host" with a WSL DNS override

"Could not resolve host" means WSL cannot resolve DNS, so every download inside the installer fails even though the Windows browser works fine. The durable fix is to stop WSL from auto-generating `/etc/resolv.conf` and pin a public resolver. In Ubuntu, append the setting with `printf '\n[network]\ngenerateResolvConf = false\n' | sudo tee -a /etc/wsl.conf`, then from PowerShell run `wsl --shutdown` so the change takes effect. Back in Ubuntu, remove the stale file with `sudo rm -f /etc/resolv.conf` and write a new one: `echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf`. Verify with `curl -sI https://github.com | head -1` — an HTTP status line means DNS is healthy. If you use a VPN on WSL 2.0 or newer, prefer `C:\Users\you\.wslconfig` containing `[wsl2]` with `networkingMode=mirrored` and `dnsTunneling=true`, followed by `wsl --shutdown`; do not combine that with `generateResolvConf = false`, or the two settings fight each other.

Step 4: Resolve "command not found" and duplicated config keys

A successful install can still end in "command not found" because the shell has not reloaded its configuration. Run `source ~/.bashrc` (or open a new terminal) so the PATH entry the installer added is picked up. If the installer appended its export line twice, you get a duplicated config key in `.bashrc`, which can produce warnings or override your PATH with an older path; open the file, delete the repeated block, and source it again. Checking `echo $PATH` before and after confirms whether the tool's directory is actually present.

Step 5: Log in and verify the tool runs

Authentication is the last gate: most AI Tools CLIs ask for an API key or launch a browser-based OAuth flow on first run. Complete the login inside Ubuntu, then run the tool's version or help command to confirm the binary resolves and the network path works. If login hangs, re-test connectivity with the same `curl -sI` check — a DNS regression after a reboot is the usual culprit, and `wsl --shutdown` plus a fresh terminal restores it.

Useful links

• Unstuck early access — paste an AI tool error and get the fix in plain words.
• https://github.com — used in the video to verify that DNS resolution works inside WSL.

Bottom line

Running Linux-only AI Tools on Windows is a solved problem once WSL is enabled and three failure points are handled: virtualization for error 0x80370102, a pinned DNS resolver for "could not resolve host", and a reloaded shell for "command not found". The whole setup is a handful of commands and rarely needs repeating after the first success. The Unstuck channel walks through this exact sequence in its WSL install and error-fix video, which is worth watching if you prefer seeing each command typed out. If a different error blocks you, the Unstuck early access form is the fastest route to a targeted answer.

Source: How to Install Linux AI Tools on Windows (WSL) + Fix 5 Common Errors · Markdown version