I’m mainly a Windows user, but I’ve always kept one foot in Linux. For years, that meant having at least one laptop set up to dual-boot Windows and Linux, just in case I needed a real Linux environment for a specific project, experiment, or troubleshooting job. I still use Linux that way in other places, too. Zorin OS and Linux Mint are great for keeping older Windows PCs useful long after Windows itself starts feeling too heavy for them.
But that’s different from needing Linux on my main machine every day. Most of the time, I didn’t need a whole separate Linux desktop. I wanted the tools that make Linux so useful for certain jobs. Dual-booting gave me that, but it also added reboots, partitions, boot menus, and a split workflow I didn’t always want to deal with.
That’s why WSL changed things for me. I still like Linux, and I still use it when it makes sense. I just don’t need to partition my main Windows laptop to keep Linux nearby anymore. With WSL available in Windows, the Linux tools I actually wanted are now part of my normal workflow instead of something I have to reboot into.
The terminal was the part I kept coming back for
The more I used Linux, the more I realized I wasn’t always booting into it because I wanted a completely different desktop. Sometimes I did, especially on older PCs where Linux made the machine feel usable again. But on my main Windows PC, the thing I kept reaching for was the Linux toolset. I wanted a real terminal environment, package managers, SSH, Git, scripts, and command-line utilities that made certain jobs faster and cleaner than they felt in Windows.
Windows Subsystem for Linux (WSL) basics
Trivia challenge
Think you know your way around WSL? Put your Linux-on-Windows knowledge to the test.
SetupCommandsHistoryFeaturesCompatibility
In which year did Microsoft first officially release Windows Subsystem for Linux (WSL)?
Correct! WSL was first released in 2016 as part of the Windows 10 Anniversary Update. It was initially introduced as a beta feature aimed at developers who wanted to run Linux tools natively on Windows.
Not quite. WSL first arrived in 2016 with the Windows 10 Anniversary Update. It started as a beta feature and quickly gained traction among developers looking to bridge the gap between Windows and Linux workflows.
What is the key architectural difference between WSL 1 and WSL 2?
Correct! WSL 2 ships with a real Linux kernel running inside a lightweight, managed virtual machine, which dramatically improves system call compatibility and file I/O performance compared to WSL 1’s translation layer approach.
Not quite. WSL 2 introduced a genuine Linux kernel running inside a lightweight VM, replacing the system call translation layer used by WSL 1. This change brought much better compatibility with Linux software and improved I/O performance.
Which PowerShell or Command Prompt command is used to install WSL on a modern Windows 10 or Windows 11 system?
Correct! Running ‘wsl –install’ in an elevated PowerShell or Command Prompt window handles the full installation automatically, including enabling required features and installing Ubuntu as the default distribution.
Not quite. The correct command is ‘wsl –install’, which was introduced to simplify the setup process. It automatically enables the necessary Windows features and installs the default Ubuntu distribution in one step.
Which of the following Linux distributions is installed by default when you run ‘wsl –install’ without specifying a distro?
Correct! Ubuntu is the default distribution installed when you run ‘wsl –install’ without any additional flags. Microsoft and Canonical have maintained a close partnership, making Ubuntu the go-to choice for most WSL newcomers.
Not quite. Ubuntu is the default distribution that gets installed with a plain ‘wsl –install’ command. You can specify other distros using the ‘–distribution’ flag, but Ubuntu is the out-of-the-box choice thanks to Microsoft’s partnership with Canonical.
How do you list all installed WSL distributions and their current running state from the command line?
Correct! The command ‘wsl –list –verbose’ (or ‘wsl -l -v’) shows all installed distributions along with their state (Running or Stopped) and the WSL version they are using, making it very handy for managing multiple distros.
Not quite. The correct command is ‘wsl –list –verbose’ or its shorthand ‘wsl -l -v’. This output tells you each distro’s name, whether it is currently running or stopped, and which WSL version (1 or 2) it is configured to use.
What does WSLg add to the WSL experience, introduced broadly in Windows 11?
Correct! WSLg (Windows Subsystem for Linux GUI) allows you to run graphical Linux applications directly on your Windows desktop without needing a third-party X server. Apps appear in the taskbar and behave like native Windows windows.
Not quite. WSLg stands for Windows Subsystem for Linux GUI, and its purpose is to let you run graphical Linux applications natively on the Windows desktop. No external X server like VcXsrv or Xming is needed — it all works out of the box.
Which Windows 10 build was the minimum requirement to use WSL 2 when it first launched?
Correct! WSL 2 requires at minimum Windows 10 version 1903 (build 18362) for x64 systems. This build introduced the virtualization infrastructure that WSL 2’s lightweight VM depends on.
Not quite. WSL 2 requires at least Windows 10 version 1903, which corresponds to build 18362, for 64-bit systems. Earlier builds lacked the necessary virtualization support that WSL 2’s real Linux kernel relies on.
What is the recommended way to access Windows files from within a WSL distribution’s terminal?
Correct! Windows drives are automatically mounted inside WSL under /mnt/, so your C: drive is accessible at /mnt/c. This makes it easy to read and write Windows files directly from the Linux command line without any extra configuration.
Not quite. WSL automatically mounts your Windows drives under the /mnt/ directory. For example, your C: drive appears at /mnt/c, allowing seamless access to Windows files straight from the Linux terminal without manual setup.
Your Score
/ 8
Thanks for playing!
That made dual-booting feel like overkill. I wasn’t always looking to leave Windows behind. I just wanted the parts of Linux that fit into my workflow. Once I started looking at it that way, the appeal of WSL made a lot more sense. It gave me access to the Linux tools I actually wanted without forcing me to stop what I was doing, reboot into another OS, and pick up my work somewhere else.
WSL makes Linux instructions and remote access much easier
The two places WSL makes the biggest difference for me are remote access and Linux-based tutorials. If I need to connect to a home server, Raspberry Pi, NAS, VPS, or another remote machine, I can do it from a clean Linux environment inside Windows instead of adding another utility or rebooting into a different OS. It also makes technical guides easier to follow because so many of them assume Linux commands, package managers, Bash, and Linux-style paths. With WSL, I can follow those instructions much more directly from the Windows PC I’m already using.
WSL gave me Linux without leaving Windows
I can drop into Linux without dropping everything else
The biggest difference with WSL is that Linux stopped feeling like a separate place I had to go. I can be working in Windows with my browser, notes, email, writing tools, and file manager open, then launch a Linux distro from Windows Terminal when I need it. That is a much different workflow than saving what I’m doing, rebooting, choosing another OS, and hoping I remembered where everything was stored.
That matters because most of the Linux work I do is task-based. I might need SSH, Bash, Git, a package manager, or a Linux command from a tutorial, but I don’t always need a full Linux desktop to get there. WSL gives me that middle ground. It’s not the same as running Linux directly on hardware, and I still use full Linux installs when they make sense. But for my main Windows PC, WSL gives me the Linux access I actually need without making me leave the Windows setup I already use every day.
WSL still isn’t the same as a full Linux PC
Some Linux jobs still need the real thing
WSL works because it fits the way I use Linux most of the time, but I don’t want to oversell it. It’s still not the same as booting directly into a full Linux install. If I need deeper hardware access, a clean bare-metal setup, or something that depends on specific low-level Linux behavior, I’d still rather use Linux the traditional way.
That line has gotten blurrier, especially now that WSL can handle many GUI apps through WSLg. But the point still stands. WSL is great when I want Linux available inside Windows. It’s not the setup I’d choose when Linux itself needs to be the whole environment.
I’m still a Linux fan, but I don’t need a dual-boot setup anymore
I haven’t stopped using Linux. I still like it, and I still think it’s one of the best ways to keep older Windows PCs useful with distros like Linux Mint or Zorin OS. But that’s different from needing a dual-boot setup on my main Windows machine. For the way I actually work now, WSL gives me the Linux tools I want without asking me to leave Windows behind.
That’s why dual-booting stopped making sense for me. It solved a real problem for a long time, but it also added friction I don’t need anymore. Windows Terminal and WSL turned Linux from a separate destination into something I can reach for when I need it. That may not replace a full Linux PC for everyone, but for my day-to-day workflow, it’s the middle ground that finally stuck.
