WSL for Beginners: Learn Linux Without Wiping Your Laptop

WSL lets you run Linux on Windows without wiping your laptop, dual-booting, or turning your daily driver into a science project.

For help desk techs and Windows admins, that is the useful part. You can keep Outlook, Teams, RMM tools, vendor portals, and the rest of your normal Windows life, while still getting a real Linux terminal for practice and light work.

Here is the short version:

Question	Beginner answer
What is WSL?	Windows Subsystem for Linux: Linux userland running inside Windows.
Do you need it to learn Linux?	No, but it is one of the easiest ways to start from a Windows machine.
Is it a full Linux server?	Not exactly. It is great for learning and many dev/admin tasks, but production servers still have differences.
Which distro should beginners install?	Ubuntu is the safest default.
What should you practice first?	Navigation, files, packages, permissions, logs, SSH, and basic troubleshooting.

This guide explains what WSL is, how to install it, when it is useful at work, where beginners get tripped up, and what to practice after the first install screen stops making you feel productive.

What is WSL?

WSL stands for Windows Subsystem for Linux. It lets you run a Linux distribution, like Ubuntu, directly from Windows.

After installing it, you can open a terminal and run commands like:

pwd
ls -la
cd /var/log
sudo apt update
ssh user@server

Those are real Linux commands. You are not just looking at a fake terminal skin that says Linux on the box.

The important beginner mental model:

Windows is still your main operating system.
WSL gives you a Linux environment inside it.
Your Linux files and Windows files are connected, but they are not the same thing.
You can use WSL to practice commands, install Linux tools, run scripts, and SSH into servers.

If you are a Windows admin trying to learn Linux, WSL is a low-friction bridge. You do not have to rebuild your laptop just to learn what /etc, chmod, grep, and systemctl mean.

WSL 1 vs WSL 2 in plain English

You may see references to WSL 1 and WSL 2.

For most beginners today, use WSL 2.

WSL 2 runs Linux with a lightweight virtual machine under the hood. That sounds heavier, but it gives you better Linux compatibility and is the normal default now.

Basic difference:

Version	What to know
WSL 1	Older compatibility layer. Fast Windows filesystem access, but less complete Linux behavior.
WSL 2	Current default. Better Linux compatibility, uses a lightweight VM.

If a tutorial tells you to use WSL 1 for a specific niche reason, fine. Otherwise, do not overthink it. Install the default WSL setup and move on with your life. The ticket queue is not getting shorter while you compare subsystem architecture.

How to install WSL on Windows

Open PowerShell or Windows Terminal as administrator and run:

wsl --install

That usually installs WSL and the default Ubuntu distribution.

Then restart if Windows asks you to. Yes, the oldest troubleshooting step in IT is still undefeated.

After rebooting, open Ubuntu from the Start menu or Windows Terminal. It will ask you to create a Linux username and password.

That username is for your Linux environment. It does not have to match your Windows username, though keeping it recognizable is not a bad idea.

To check what you installed, run this in PowerShell:

wsl --list --verbose

You should see something like:

  NAME      STATE           VERSION
* Ubuntu    Running         2

If the version says 2, you are on WSL 2.

Your first WSL commands

Once Ubuntu opens, start boring on purpose. The first commands are not flashy, but they build the mental map you need for everything else.

pwd

Shows where you are.

ls

Lists files in the current directory.

ls -la

Lists files with details, including hidden files.

cd /home

Changes directories.

cd ~

Goes back to your Linux home directory.

whoami

Shows your current Linux user.

cat /etc/os-release

Shows which Linux distro you are running.

This is not glamorous, but this is how real admin work starts. Before you fix something, you need to know where you are, who you are, and what system you are on.

Where are my Windows files in WSL?

Inside WSL, your Windows drives show up under /mnt.

Your C: drive is usually here:

/mnt/c

So your Windows user folder may be something like:

/mnt/c/Users/YourName

Example:

cd /mnt/c/Users
ls

That connection is handy, but here is the beginner mistake: doing heavy Linux work directly inside /mnt/c can be slower and can create permission weirdness.

A good rule:

Use your Linux home folder for Linux projects and practice.
Use /mnt/c when you need to copy files to or from Windows.
Do not randomly chmod -R Windows folders from WSL unless you enjoy creating your own afternoon.

Your Linux home is usually:

/home/yourlinuxuser

You can jump there with:

cd ~

How to update packages in WSL Ubuntu

If you installed Ubuntu, you get the apt package manager.

Before installing packages, update the package list:

sudo apt update

Then install a tool:

sudo apt install curl

Remove a package:

sudo apt remove curl

Search for packages:

apt search htop

Beginner mistake: treating sudo apt update like it upgrades everything. It does not. It refreshes the package list.

To actually upgrade installed packages:

sudo apt upgrade

The short memory hook:

apt update = refresh the menu.
apt upgrade = order the newer food.
apt install = install something new.

Not a perfect analogy, but good enough to keep you from confidently doing the wrong thing in a ticket.

What WSL is good for at work

WSL is useful when your normal workstation is Windows but the work keeps brushing up against Linux.

Common help desk and junior sysadmin uses:

1. SSH into Linux servers

ssh user@server

This is one of the biggest wins. You can practice and use SSH without installing a separate client.

2. Test Linux commands safely

If a runbook says:

grep "error" /var/log/app.log

You can learn what grep does before running it on a real server with a manager breathing down the back of your neck through Teams.

3. Work with logs and text files

Linux is very text-file-heavy. WSL gives you a place to practice:

cat file.txt
less file.txt
grep "failed" file.txt
tail -f app.log

4. Use command-line tools that expect Linux

Many developer and infrastructure tools assume a Unix-like shell. WSL often makes those tools easier to use from a Windows machine.

Examples include:

curl
wget
jq
git
ssh
rsync

5. Learn Linux paths without touching production

Windows paths look like:

C:\Users\Stetson\Downloads

Linux paths look like:

/home/stetson/downloads
/var/log
/etc/ssh/sshd_config

WSL lets you build that muscle memory without needing a spare server first.

What WSL is not

WSL is useful. It is not the same as being logged into a production Linux server.

A few differences matter:

WSL runs inside Windows.
Some hardware, networking, and service behavior differs from a normal Linux machine.
Your company servers may use different distros, package managers, and security policies.
WSL is not where you should learn by making risky changes to real business data.

For example, service management can be different depending on your WSL version and configuration. On a normal Ubuntu server, you may use:

systemctl status ssh

In WSL, systemd support depends on setup and version. If a command behaves differently, that does not mean Linux is broken. It means your lab environment is not the same as the server.

That distinction matters when you are writing notes for an escalation. “It worked in WSL” is useful context. It is not final proof.

Beginner WSL mistakes to avoid

Mistake 1: Forgetting where you are

If you run:

pwd

and see:

/mnt/c/Users/YourName/Desktop

then you are working inside your Windows filesystem.

If you see:

/home/yourlinuxuser

then you are in your Linux home.

That difference affects paths, permissions, and sometimes performance.

Mistake 2: Using random commands from old forum posts

Do not paste destructive commands just because someone on a forum sounded confident in 2016.

Be especially careful with:

rm -rf
chmod -R
chown -R
sudo

If you do not know what a command changes, do not run it on anything important.

Mistake 3: Thinking Windows admin knowledge is useless

It is not. Your troubleshooting brain transfers.

You already know how to ask:

Is it DNS?
Is it permissions?
Is the service running?
Is the user in the right group?
Did the path change?
Did someone forget VPN again?

Linux uses different commands, but the troubleshooting shape is familiar.

Mistake 4: Never leaving tutorial mode

Reading WSL tutorials is fine. But if you never type the commands, you are basically watching someone else go to the gym.

Open the terminal. Make a folder. Create a file. Break a harmless test file. Fix it. That is how the command line stops looking like a punishment.

A simple WSL practice plan

Here is a beginner-friendly path for your first few sessions.

pwd
ls
ls -la
cd ~
mkdir wsl-practice
cd wsl-practice

Goal: stop feeling lost every time the prompt changes.

Session 2: files

touch notes.txt
echo "first line" >> notes.txt
cat notes.txt
cp notes.txt backup.txt
mv backup.txt notes-backup.txt

Goal: create, read, copy, and rename files.

Session 3: search text

echo "error: login failed" >> app.log
echo "info: login worked" >> app.log
grep "error" app.log

Goal: understand why grep shows up in so many support docs.

Session 4: packages

sudo apt update
sudo apt install htop
htop

Goal: install a package and run it.

Session 5: SSH basics

ssh user@hostname
ssh [email protected]

Goal: understand the shape of SSH before you are troubleshooting it under pressure.

If you want a structured place to practice this without turning your actual machine into a mess, Shell Samurai is built for exactly this: short command-line practice that feels closer to real support work than reading another wall of docs.

Practice beginner Linux commands in Shell Samurai so WSL becomes a useful tool instead of another terminal icon you avoid.

WSL troubleshooting checklist

If WSL does not behave, start here.

Check installed distros

In PowerShell:

wsl --list --verbose

Shut down WSL and restart it

wsl --shutdown

Then open Ubuntu again.

Update WSL

wsl --update

Check your Linux version

Inside WSL:

cat /etc/os-release

Check your current folder

pwd

This catches more beginner confusion than people want to admit.

Check networking from inside WSL

ping 8.8.8.8
curl https://example.com

If those fail, compare against Windows. Sometimes the issue is WSL networking. Sometimes the issue is corporate VPN being corporate VPN.

What to learn after WSL basics

Once WSL is installed and you can move around, learn the Linux skills that show up in real support work:

File navigation: pwd, ls, cd
File reading: cat, less, head, tail
Search: grep, find
Permissions: chmod, chown, sudo
Packages: apt update, apt install, apt remove
Logs: /var/log, journalctl, tail -f
Networking: ip, ping, ss, curl, dig
Remote access: ssh, SSH keys, known hosts
Processes: ps, top, kill

Do not try to learn all of that in one heroic Saturday. That is how people buy a Linux course, open it twice, and then let it haunt their bookmarks.

Pick one category. Practice it until you can explain it without reading the tab title.

Bottom line

WSL is one of the easiest ways for Windows admins and help desk techs to start learning Linux.

Use it to build confidence with commands, paths, packages, logs, and SSH. Just remember that WSL is a practice and work environment, not a perfect copy of every Linux server you will touch.

Start with boring commands. Notice where you are. Keep test files separate from real files. Practice a little daily.

That is how Linux stops being “that scary black window” and becomes another tool in the support toolbox.