Open-source project
yuk7/ArchWSL avatar
yuk7/ArchWSL

ArchWSL: the launcher filename is the WSL instance name

ArchLinux based WSL Distribution. Supports multiple install.

7,391 stars203 forksMakefileMIT

At a glance

What is it?
ArchWSL is a distribution that puts Arch Linux on the Windows Subsystem for Linux, built by assembling a launcher from one repository with a root filesystem from another. Its distinguishing feature is that the executable's filename becomes the WSL instance name, so copying and renaming the launcher gives you several Arch instances side by side. The warnings are about the folder you extract into and about WSL1.
Who is it for?
Use it if you want a rolling Arch environment next to your existing Linux subsystem instances and you are comfortable with a distribution that ships as a filesystem image rather than a package. Do not install it into Program Files, and on WSL1 expect a mandatory first-run fix to the C library before pacman works.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 32 days ago.
What is it written in?
Mainly Makefile, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • yuk7/ArchWSL7,391 ★ · -9
Star history
Repository2026-09-222026-11-15
yuk7/ArchWSL7.4k7.4k

-9 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The launcher filename becomes the WSL instance name

The zip install is four steps and the third one is the interesting design. You download the installer zip, extract every file to the same directory, and run the executable, which extracts the root filesystem and registers it with WSL. The documentation then explains that the name of that executable is used as the name of your WSL instance, which means that if you copy the executable several times and rename each copy you can have multiple different ArchWSL installations at the same time without any conflict. So the multi-install support in this project's description is implemented through naming rather than through an installer dialog. The practical consequence is that the filename becomes part of your setup.

The extraction folder needs write access, and Program Files does not qualify

The zip instructions are specific about where the files go. Extract all files in the zip to the same directory, and extract to a folder that you have full access permission to, with the explicit example that Program Files cannot be used. The requirement is listed next to a download step and a run step, so it is easy to skim past. If you are scripting an installation across a fleet of machines, that sentence is the one to encode: choose a path under your own profile rather than a shared application directory.

WSL1 needs its C library replaced on the first run, and that is not optional

There is one warning on the page set in capitals, and it is the failure mode you cannot work around later. If you use the first version of the subsystem, you must replace the glibc package on the first run of the instance, and the setup documentation covers how. That is why the optional-looking next step, initialising the pacman keyring, is also mentioned: the documentation says it is not required, but you will need it if you intend to use pacman at all. Taken together, the two lines mean that an ArchWSL instance on WSL1 needs one manual repair before it is usable, and every user of pacman needs one manual step afterwards.

Three install routes, three different privilege stories

The routes differ less in what you end up with than in what they ask of you. The zip route needs no administrator rights and only needs a writable folder. The appx route needs you to install the certificate file into the Trusted People store of the local machine first, which the documentation points out requires administrator privileges, and then you double-click the appx to install. The third route is a package manager:

dos
scoop bucket add extras 
scoop install archwsl 

That is the whole install for the Scoop path, and it is the shortest of the three by a wide margin. So the choice is mostly about how much of your machine you are willing to change permanently: a copy in your own directory, a certificate in a machine-wide trust store, or a package manager entry. All three converge on the same launcher and the same instance naming rule, so the routes are interchangeable once installed, which is also what makes the update section able to describe two of them and ignore the third.

The build assembles two other projects' release artefacts

The Makefile is short and it explains the architecture of this project better than any diagram would. It does not compile anything itself. It asks the GitHub API for the newest release of a separate filesystem repository, filters the assets for a file named like a root filesystem archive, downloads it, and separately asks another repository, wsldl, the launcher this distribution is based on, for an icon bundle that contains the launcher executable. Then it assembles them: the executable is copied to a build directory under a fixed name and the filesystem archive is copied beside it, and the whole directory is packed into a zip. The consequences are two. A release here depends on two upstream repositories publishing compatible artefacts at that moment, and the clean target has to delete both downloads and the intermediate launcher because none of them are built here.

Updates overwrite two files rather than upgrading in place

The update section is deliberately thin, and the reason is the packaging. On the zip route you download the installer zip again, extract the executable and the root filesystem archive, and overwrite the ones you already have. On the appx route you download the appx and double-click it. So an update is a file replacement, not a package upgrade, and it applies to the filesystem image as well as to the launcher. That is the direct consequence of the distribution model: the root filesystem arrives as a tarball rather than as something pacman maintains incrementally, which keeps the image reproducible at the cost of making every update a full replacement. If you have stored data inside the instance, the overwrite path is the place to check before you run it, since the documentation does not discuss merging anything back.

The launcher is also the command line interface for an instance

Once an instance exists, the same executable is how you drive it. With no arguments it opens a new shell with your default settings and inherits the current directory, with the exception that the Windows user profile variable is changed to the home variable inside the instance. A run subcommand executes a command line in that instance and inherits the current directory, and a second variant accepts a command line that includes a Windows path and converts it before running. A config subcommand takes a setting and an optional value, with settings for the default user and for the default user id. So there is no separate management tool: naming, launching, path translation and default-user configuration are all one executable, which is a coherent design for something whose whole state is a filename and a registered instance.

Editorial conclusion

Use it if you want a rolling Arch environment next to your existing Linux subsystem instances and you are comfortable with a distribution that ships as a filesystem image rather than a package. Do not install it into Program Files, and on WSL1 expect a mandatory first-run fix to the C library before pacman works. Before you start, read the setup documentation linked from the README, decide between the zip, appx and Scoop routes by whether you want an administrator step, and check that the keyring initialisation you skip is not something you need for pacman.

Frequently asked questions

How do I install ArchWSL?

Three ways. Download the installer zip, extract every file to the same folder where you have full access permission, since Program Files cannot be used, and run the launcher executable to extract the root filesystem and register with WSL. Or download the appx and its certificate, install the certificate into Trusted People with administrator rights, then double-click the appx. Or use Scoop with the bucket add and install commands. On WSL1 you must replace the glibc package on the first run of the instance.

how to install arch wsl

The requirements are Windows 10 version 1709 FCU x64 or later, or Windows 11 x64, with the Windows Subsystem for Linux feature enabled. After the install, initialising the pacman keyring is optional but necessary if you plan to use the package manager, and the setup documentation linked from the README covers both that step and the WSL1 glibc replacement.

Can I install ArchWSL more than once?

Yes, and that is the design rather than a workaround. The launcher executable's filename is used as the WSL instance name, so copying the executable and renaming each copy gives you several ArchWSL installations running at the same time without conflict. Each instance is then driven through the same executable, which opens a shell, runs a command line, runs one with a Windows path converted, and configures the default user or uid.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. yuk7/ArchWSL on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/yuk7-archwsl.svg)](https://hysenlabs.com/projects/yuk7-archwsl)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/yuk7-archwsl.svg)](https://hysenlabs.com/projects/yuk7-archwsl)

Was this useful?