An Introduction to the Windows Subsystem for Linux (WSL2)

WSL2 is one of the most important bridges Microsoft ever built for curious Windows users.

Not because it turns Windows into Linux.
And not because it eliminates every reason to run a full Linux system.

It matters because it removes a lot of the friction between:

"I want to understand Linux"

and

"I am not ready to reorganize my whole computer to do it."

That is a very big difference.

The steps and terminology below are checked against Microsoft's official documentation; menu names and behavior can vary by operating-system release and hardware.

WSL2 matters because it changes the cost of experimenting with Linux

For a long time, trying Linux seriously on a Windows machine often implied one of three things:

• dual-booting;
• using a virtual machine;
• or giving a second machine to the experiment.

All of those paths can still make sense.
But they all carry more weight.

That is one reason WSL2 feels so important to me.

It lets Windows users begin using a real Linux environment for command-line tools and workflows without making the first step feel like a full operating-system decision. It is one of the calmest ways to start learning Linux while keeping your existing Windows life intact.

Microsoft’s own framing makes the big idea clear

Microsoft’s official installation page describes WSL as something you can install with:

wsl --install

and then use with a Linux distribution such as Ubuntu, Debian, SUSE, Kali, Fedora, Alpine, and others.

That alone already tells you something meaningful.

WSL2 is not positioned as a weird niche developer hack anymore.
It is presented as a first-class Windows feature for running a Linux environment and toolchain in a much more direct way than older workarounds.

WSL2 is the current default, and that is not just branding

Microsoft’s comparison page says WSL2 is the current default version when installing a Linux distribution. The same documentation explains that WSL2 uses an actual Linux kernel inside a lightweight managed virtual machine and provides full system call compatibility.

That is the architectural difference that really matters.

WSL1 used a translation approach.
WSL2 uses a real Linux kernel.

For a beginner, the cleanest takeaway is simple:

WSL2 feels more like real Linux because under the hood it is much closer to real Linux behavior.

That is why so many Linux tools, runtimes, and workflows make more sense in WSL2 than they ever did in the earlier model.

As of Monday, August 10, 2026, the easiest official install path is still wsl --install

Microsoft’s installation guide says that if you are running Windows 10 version 2004 and higher, build 19041 and higher, or Windows 11, you can install what you need by opening PowerShell as administrator, running:

wsl --install

and then restarting your machine.

Microsoft also says that this command enables the necessary WSL features and installs Ubuntu as the default Linux distribution unless you choose another one.

This is one of the nicest parts of the whole WSL story.

The first-time setup is no longer something you have to piece together from scattered optional-feature guides and old blog posts.

If Ubuntu is not the distro you want, Microsoft already gives you the next step

The same Microsoft documentation says you can use:

wsl --list --online

to see available distributions, then install one directly with:

wsl --install -d <DistroName>

That makes WSL feel much more intentional.

You are not trapped in one default forever.
You are just being given a sensible first landing point.

And honestly, that matters a lot for beginners.

The best first Linux step is usually the one that works before it asks you to become opinionated.

Why WSL2 is usually better than WSL1

Microsoft’s comparison page is pretty clear here.

It says the primary differences between WSL1 and WSL2 include:

• the use of an actual Linux kernel in WSL2;
• full system call compatibility in WSL2;
• and stronger performance for Linux-side file-intensive work.

Microsoft even calls out common operations such as:

• git clone
• npm install
• apt update
• apt upgrade

as being noticeably faster with WSL2.

This is one of the reasons WSL2 feels like such a breakthrough for real workflows.

It is not only “Linux commands inside Windows.”
It is Linux commands inside Windows in a way that finally behaves seriously enough for meaningful development and tool usage.

The biggest beginner misunderstanding is where to keep project files

This is the nuance that saves people a lot of frustration.

Microsoft’s comparison page also says that WSL2 loses ground in one important area: performance across the Windows and Linux filesystems.

That means if your workflow depends heavily on tools in one environment constantly operating on files stored in the other, you can feel slowdowns in the wrong direction.

Microsoft’s own advice is basically to keep files on the same operating system as the tools doing the work.

That is the practical rule I would memorize:

• if Linux tools are doing the work, store the project on the Linux side;
• if Windows tools are doing the work, store the project on the Windows side.

This one insight explains a huge amount of beginner WSL confusion.

WSL1 still has a few honest exceptions

Microsoft’s version-comparison guide does not pretend WSL1 is useless now.

In fact, it explicitly says there are a few situations where WSL1 may still be preferable, especially when your project files must remain on the Windows filesystem and the workflow depends heavily on fast access across that Windows/Linux boundary.

That is good guidance because it keeps the story honest.

WSL2 is not “better in every sentence.”
It is the better default.

Those are different claims.

And the difference matters because good infrastructure choices usually come from understanding exceptions, not just repeating the default recommendation loudly.

The first commands worth knowing are not complicated

Microsoft’s basic WSL commands page keeps the early command set pretty clean.

These are the commands I think matter most first:

• wsl --install
• wsl --list --online
• wsl --list --verbose
• wsl --set-default-version 2
• wsl --set-version <distribution> 2
• wsl --shutdown

That is already enough to give the environment some shape.

You can:

• install;
• inspect what is available;
• see what you already have;
• control which WSL version a distro uses;
• and shut the system down cleanly when needed.

That is not trivia.
That is a working foundation.

WSL2 is often the right first step before bigger Linux commitments

This is where the emotional value of WSL2 becomes most obvious.

A lot of people are interested in Linux, but not yet ready for:

• a dual-boot setup;
• a dedicated Linux laptop;
• or a full switch in daily workflow.

WSL2 lets them begin earlier.

It gives Windows users a way to:

• learn Linux commands;
• use Linux package managers;
• experiment with development tools;
• understand the filesystem differences;
• and get comfortable with Linux conventions before making larger decisions.

That is why I think WSL2 often belongs earlier in the story than dual-booting. If someone later decides to go further, something like trying Linux from a live USB may still make sense. But WSL2 is often the first place where Linux stops being a concept and starts becoming a habit.

WSL2 is also a good teacher because it reveals how different Windows and Linux really are

This is something I genuinely like about it.

The environment is convenient, but it does not completely hide the conceptual differences.

You still start noticing things like:

• path differences;
• tooling differences;
• file-permission assumptions;
• package-manager habits;
• and why some Linux-native workflows feel cleaner when they stay on the Linux side.

That makes WSL2 more than a feature.
It becomes an on-ramp.

And if that on-ramp eventually leads you to explore Linux-native ideas more deeply, even topics like trying Linux from a live USB start making more conceptual sense too.

Conclusion

WSL2 is one of the most practical ways for a Windows user to begin using Linux because it lowers the barrier to entry without flattening the experience into a toy. Microsoft’s current official guidance reflects that clearly: wsl --install is the simplest path on supported Windows versions, WSL2 is the default for new Linux installations, and its real Linux kernel plus full system call compatibility make it the stronger choice for most modern Linux workflows.

Its one major caveat is also the one worth remembering most:
keep your files close to the operating system doing the work.

Once that clicks, WSL2 stops feeling like a novelty.
It starts feeling like one of the smartest features Windows ever borrowed from curiosity.

FAQ

What is WSL2 in simple terms?

WSL2 is Microsoft’s modern Windows Subsystem for Linux architecture that runs Linux distributions on Windows using an actual Linux kernel inside a lightweight managed virtual machine.

Is WSL2 better than WSL1?

Usually yes. Microsoft recommends WSL2 as the default because it offers full system call compatibility and much better Linux-side performance for many common development and package-management tasks. WSL1 still has a few niche advantages when cross-filesystem access patterns matter more than Linux-native behavior.

For additional context, see How to Map a Network Drive in Windows for Easy File Sharing and Why Total Commander Still Has a Cult Following Among Techies.