Get started with Windows Subsystem for Linux on Arm
Introduction
Configure and run WSL with various Linux distributions
Run graphical Linux applications
Enable systemd in WSL
Use SSH to connect to WSL
Connect to WSL using RDP and VNC
Developing with VS Code on WSL
Import file systems into WSL
Backup a WSL filesystem
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Advanced
Reading time:  1 hr 30 min
Last updated:  12 Aug 2026
Skill level:
  Advanced
Reading time:
  1 hr 30 min
Last updated:
  12 Aug 2026
Author:Jason Andrews, Arm
Arm IP:Cortex-A
Tags: Migration to Arm Windows Linux WSL Visual Studio Code
Author:
  • Jason Andrews, Arm
Arm IP:
Cortex-A
Tags:
Migration to Arm Windows Linux WSL Visual Studio Code

Who is this for?

This Learning Path is for software developers with Windows on Arm computers doing Linux or cloud native development.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Configure and run Windows Subsystem for Linux (WSL) with various Linux distributions
  • Run graphical Linux applications on Windows
  • Use ssh to connect to WSL
  • Use Windows RDP (remote desktop) and VNC to connect to a Linux desktop
  • Learn multiple options for running VS Code
  • Import other file systems into WSL
  • Export the WSL file system as a backup

Prerequisites

Before starting, you will need the following:

  • A Windows on Arm computer such as the Lenovo Thinkpad X13s running Windows 11.

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll configure Windows Subsystem for Linux (WSL) on Windows on Arm, select a Linux distribution, and enable systemd. First, you’ll launch graphical Linux apps, decide when to use SSH or the Windows drive mount for file transfer, and set up an XFCE4 desktop with xrdp. Then, you’ll restart the distribution and verify that systemd and xrdp are active.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I enable systemd in my WSL distribution and confirm it’s running?
Edit /etc/wsl.conf to include [boot] with systemd=true. In Windows Command Prompt or PowerShell, run wsl --terminate Ubuntu-22.04 and then wsl -d Ubuntu-22.04. Verify with systemctl list-unit-files --type=service.
What should I see when I start a graphical Linux app from WSL?
A new app window opens on the Windows desktop and shows a small penguin icon on the taskbar. You can pin the app to the taskbar and add icons to the Windows applications menu.
Do I need SSH to copy files between Windows and WSL on the same machine?
No. Windows drives are mounted under /mnt/c, so you can copy directly, for example, cp /mnt/c/Users/<username>/Downloads/<filename>. Use SSH only when connecting to WSL from a different machine.
How do I set XFCE4 as the default desktop for RDP and check that xrdp is ready?
Set the session with echo xfce4-session > ~/.xsession, then restart the service with sudo service xrdp restart. Check status with systemctl status xrdp, and start the service if it’s not running.
Which distribution name should I use when restarting WSL after enabling systemd?
Use the registered distribution name shown in WSL, such as Ubuntu-22.04. Run wsl --terminate Ubuntu-22.04 followed by wsl -d Ubuntu-22.04 to restart it with systemd enabled.
Next