Course Preview

Windows Subsystem for Linux

Windows Subsystem for Linux (WSL) runs Linux distributions and their command-line or graphical applications alongside Windows. It gives Windows users a Linux filesystem and tool environment without a separately managed traditional virtual machine or a dual-boot setup.

itWindows and Microsoft infrastructure | OpenSkills.info

Course pathWalk it in order

Look it upDip in anytime

Go furtherLeaves this page

Don't Panic — Windows Subsystem for Linux

Here is the whole idea in one sentence: Windows Subsystem for Linux (WSL) lets you run actual Linux distributions right next to your ordinary Windows programs, on the same machine, without picking a side. No dual-boot menu, no separate laptop, no remote server you SSH into just to run grep.

Before WSL, "I need Linux tools on Windows" meant one of three unpleasant choices: reboot into a different operating system, run a full virtual machine and pay for it in RAM and disk space, or tunnel into somebody else's Linux box over the network and hope the connection holds. WSL replaces all three for a large share of everyday development, scripting, and administration work, by putting a real Linux environment a few keystrokes away instead of a reboot away.

Three ideas carry the rest of the course. First, the layering: Windows is the host, WSL is the integration and lifecycle layer, and a distribution — Ubuntu, Debian, whichever you pick — is its own self-contained Linux user space with its own packages, users, and filesystem.

Second, there are two ways WSL can run a distribution. WSL 1 translates Linux system calls through Windows, while WSL 2 runs a genuine Linux kernel inside a small managed utility virtual machine. WSL 2 is the default, and for good reason, but it is a virtual machine, not a clever trick.

Third, where you put your files matters more than almost anything else here: keep a Linux-built project on the Linux side, keep a Windows-built project on the Windows side, and crossing that line costs you performance every time you do it.

Here is the part that catches people off guard: WSL 2 being "a real kernel in a VM" is not a free upgrade over WSL 1, it is a trade. That VM can hold onto memory it no longer needs — your machine can look like it is starving for RAM long after the Linux workload that used it has finished — and Windows will not take that memory back on its own. It is not a leak, it has a documented fix, but it surprises almost everyone the first time their machine gets sluggish for no visible reason.

Two more things worth carrying with you. Your Linux user account and your Windows account are genuinely separate, with separate permissions, so logging into one does not make you the other. And the two configuration scopes — one file inside Linux, one inside your Windows user profile — both need WSL restarted before a change takes effect, which trips up nearly everyone at least once before it becomes a reflex.

Start with the Cheatsheet if you want the WSL 1 versus WSL 2 decision made concrete, the Reference tab for the commands themselves, and the quiz once you are ready to check what stuck.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Systems Administratorsupporting

Sources