WSL command line does not have --mount option

[nitivachhani]

PS C:\windows\system32> wsl --mount
Invalid command line option: --mount
Copyright (c) Microsoft Corporation. All rights reserved.

Usage: wsl.exe [Argument] [Options...] [CommandLine]

Arguments for running Linux binaries:

If no command line is provided, wsl.exe launches the default shell.

--exec, -e <CommandLine>
    Execute the specified command without using the default Linux shell.

--
    Pass the remaining command line as is.

Options:
--distribution, -d
Run the specified distribution.

--user, -u <UserName>
    Run as the specified user.

Arguments for managing Windows Subsystem for Linux:

--export <Distro> <FileName>
    The filename can be - for standard output.

--import <Distro> <InstallLocation> <FileName> [Options]
    Imports the specified tar file as a new distribution.
    The filename can be - for standard input.

    Options:
        --version <Version>
            Specifies the version to use for the new distribution.

--list, -l [Options]
    Lists distributions.

    Options:
        --all
            List all distributions, including distributions that are currently
            being installed or uninstalled.

        --running
            List only distributions that are currently running.

        --quiet, -q
            Only show distribution names.

        --verbose, -v
            Show detailed information about all distributions.

--set-default, -s <Distro>
    Sets the distribution as the default.

--set-default-version <Version>
    Changes the default install version for new distributions.

--set-version <Distro> <Version>
    Changes the version of the specified distribution.

--shutdown
    Immediately terminates all running distributions and the WSL 2 lightweight utility virtual machine.

--terminate, -t <Distro>
    Terminates the specified distribution.

--unregister <Distro>
    Unregisters the distribution.

--help
    Display usage information.

[onomatopellan]

Make sure you are in Insider Build 20211 or superior for mount.

[bertsons]

to configure settings for windows insider programmer, you need to give data to microsoft such as the websites you visit... are you kidding?

[MasterLamp]

Haha 2021 and now easy way to get an EXT4 mount on this pile of NT lines.

[bckelley]

so you can't use --mount if it's not 20211??

Edition Windows 10 Pro
Version 21H1
Installed on ‎3/‎1/‎2022
OS build 19043.1586
Experience Windows Feature Experience Pack 120.2212.4170.0

[ChrisGuyML]

Correct!

This means you need to be a part of the insider program at the deepest level (Dev Channel).
I doubt Microsoft will ever release it on Windows 10 Retail.

At least it works, I was able to copy directories from my Ext4 drive to an NTFS without any issues the other day. That being said it still needs work to smooth out the rough edges.

My question is: Why is it so hard to port Ext4 to Windows? It's not like Microsoft doesn't have the source code for Ext4, heck I have the source code if they can't find it. Ext2/3/4 should be formats that Windows understand natively and be an option for non-Windows OS partitions at a minimum. If I can mount an NTFS drive in Linux, I should be able to do it the other way around.

[Hashbrown777]

@ChrisGuyML it's supposed (read: at least originally intended) to work on retail, that's the point of putting it in dev channel in the first place

We have a ticket to push them on this if you'd like to join in; #7940

[mettletujun]

This is my windows version. But my 'wsl --mount' is a invalid command. Why?

[rajhlinux]

Because your OS build is 19042 from Beta or Release Preview channels. You need to be in Insider Dev channel to get OS build 20231 with mount support.

How does one get the installation for this "Dev" OS build 20231? Google is showing me windows 11 dev channel...

[rajhlinux]

I have OS build 19042.630. how to get OS build 20231 or how can I access linux files from windows explorer. please help.

You can access the linux files opening the path \\wsl$\ in explorer or also calling explorer.exe . from bash. To get builds >=20231 you need to be part of the Windows Insider.

Please make a through guide on how to do this, your explanation is very vague.

[rajhlinux]

Windows is shit

Then that means your "Shit" too for using Windows. Hell, I don't like windows either, but I don't cry about it since I whip out my $4K MacBook which has MacOS, FreeBSD, Windows and Ubuntu. There are many ways to skin a cat, it's not end of the world on a Windows system.

[achillelrc]

cool life bro

[ivan0kurnia]

Windows is shit

I know! It's November 1st and Windows 11 is already out there. Release it for fun's sake!

[gobshiny]

comment in error

[theAkito]

How long until this gets released? I hate Insider Preview builds.

[onomatopellan]

Big features have been postponed until September (Windows 10 21H2).

[Hashbrown777]

21H2 has come and gone. If youd like to track this, #7940

[YuenSzeHong]

this is my window version, still no --mount

[UPDATE] found the --mount option after a WSL update

[benhillis]

@YuenSzeHong - are you sure? Can you share the output of "wsl.exe --help"?

[YuenSzeHong]

found the option after a wsl update

[GottfriedHofmann]

I am on Windows 10 21H2 (Build 19044.1348) and still no wsl --mount.
Running wsl --update does not help.

[YuenSzeHong]

you need to have build 22xxxxx to get this feature
(window 11 builds)

[ajohnsen]

Will this one ever get released to windows 10 builds as well?

[Hashbrown777]

#7940

[ivan-gorin]

The --mount feature was introduced in windows insider 20211, over a year ago, when will this feature come to release builds of windows 10?

[Hashbrown777]

#7940

[name161]

Hello guys, same question.
Has a plan to introduce this feature to Windows 10?

[Hashbrown777]

#7940

[Guitlle]

Wow, so a very basic thing such as mounting file systems is still missing in windows subsystem for linux ... this sucks so much

[alimoezzi]

Almost 2022 and no --mount 😑

[trostn]

2022 an no --mount!

[Hashbrown777]

#7940

[JuanJ67m]

April 2022 and still not --mount

[Hashbrown777]

@JuanJ67m I don't think anyone's watching an answered discussion post, you're better off just subscribing the open feature request I posted for any response from the WSL team [if you hadn't]

[brianddk]

The usbipd-win project will allow you to mount USB devices on older systems. But some assembly is required. It's been around for over a year, but just recently (2 weeks ago) got a place in the official MS doc tree.

USBPID Minimum Requirements

• Windows 10 Version 1903 or higher, with Build 18362 or higher (for WSL-2)
• Distribution running WSL Linux kernel 5.10.60.1 or higher
• WSL-2

I had to build my own WSL Linux kernel to add usb_storage, but there were pretty good instructions. To add usb_storage just modify the menuconfig step in the build guide and select "USB Storage" as well as the other options.

Obviously this only gives you access to USB Removable Media, but it is something.

cc: @trostn, @realsarm, @Guitlle, @pavelslunin, @ivan-gorin, @ajohnsen,

[brianddk]

Can you provide a list of commands which are required to be executed in order to make this extension working on Windows 10? To be honest I don't care about the technical details how it works in details

@rekire , it's not for the faint at heart. Kernel recompilations are usually considered "advanced". Be warned, in my experience, this will kill any VirtualBox installs you may have on your host.

1. Install WSL-2
2. Install usbipd-win
3. Build the Kernel
4. In the menuconfig step, ensure you enable CONFIG_USB_STORAGE
5. Enter the WSL instance with the new kernel wsl --distribution wsl2-usbip --user <user>
6. (in WSL) manually restart udev sudo service udev restart (usbipd bug)
7. (in Windows) attach USB storage usbipd.exe wsl attach --distribution wsl2-usbip --busid=<BUSID>

Drive should now be active in your WSL instance.

[Hashbrown777]

So does this share the filesystem or the device (as a blk)? Is this just getting the equivalent of internally mounted (but still already mounted by windows) /mnt/(drive letter) or will this let us use linux mount directly for things like LUKS as [win11] wsl --mount bare provides?

[brianddk]

@Hashbrown777 , Yes, LUKs works, but only in the WSL instance and is not "exported" to windows AFAIK

So does this share the filesystem or the device (as a blk)? Is this just getting the equivalent of internally mounted (but still already mounted by windows) /mnt/(drive letter)

IDK, the win-usbipd team can likely fill in the details on their github project. The access seems to be raw and not related to the \\.\PhysicalDrive instances. This is more of a USB bus filter driver so it hijacks the IO even before the windows kernel starts carving things up.

will this let us use linux mount directly for things like LUKS

Yes... That was the reason I actually went searching for this solution. The LUKs mount will NOT be exportable to the Windows Kernel. All access stays in the WSL-2 sandbox.

[Hashbrown777]

once mounted in linux you should always be able to access it through windows via \\wsl$, especially with the fixes to #6711

This is interesting, I'll take a look then

[jaredhagel]

Hi @brianddk - I think it's likely Microsoft won't backport this --mount option on Windows 10, so I'm looking into simplifying this process for Windows 10. Do you know if it's possible to have WSL2 automount a USB drive after it's attached using the Windows usbipd wsl attach --busid ID command? Right now I need to manually attach it by running the sudo mount -s /dev/sdX1 /media/usb0 command within WSL2. I'm a little surprised it isn't auto-mounted by default.

[Guitlle]

Thanks, great work. One step forward. I ended up figuring out how to install linux in my laptop so I will not use WSL anymore

[juniberry]

This totally M$ in a nutshell, one step forward, two steps backwards.

[ipatrol]

Apparently something this simple isn't considered a priority. I'm not trying to mount a USB drive, I'm trying to mount the existing partition on my hard drive so I can move files around. Linux supports NTFS partitions already!

[AlphaJack]

Like mount -t drvfs D: /mnt/d, supposing your parition is the D: drive on Windows and /mnt/d is an empty folder under the WSL filesystem?

[theAkito]

@AlphaJack Thanks a bunch. Worked perfectly for me.

[Hashbrown777]

@AlphaJack that only mounts [windows]mounted disks, not partitions. You wont be able to mount things like, say, btrfs partitions, since windows wont be able to mount them first to give them a drive letter.

This is a passthrough of the fs, not the device. I don't know why you would do that, isn't /mnt/(drive letter) always populated by default?

[Jahfry]

I'm on 21H2 / 19044.1466 (latest available to me).

I'm not upgrading my OS to an insider build for --mount.

Upgrading to Win11 isn't a viable option for this PC.

I need to read an XFS partition on a large drive to salvage data.

Really thought this would be a basic part of WSL2 without all the hoops. I'll just do this in a standard VM. Putting this in as feedback for getting this feature into the Win10 version without needing an unstable version.

[brianddk]

If you can house the drive in a USB carrier you can get USB access to drives in WSL2 today using usbipd-win. Not a perfect solution, but might get you what you need.

[Hashbrown777]

Putting this in as feedback for getting this feature into the Win10 version without needing an unstable version

#7940

[bartash]

I have a machine that can't run Windows 11 so now I am stuck.
I had high hopes for wsl but when it can't even mount a native linux fs then I despair.

[ChrisGuyML]

You need to join "The Windows Insider Program, "Settings/Windows Update/Windows Insider Program" menu, select "Dev Channel" in "Choose your insider settings" then press the "Check for Updates" button. You may need to set some additional developer options first, but you'll be prompted if that's the case.

You'll be running Windows 10 with Windows 11 Insider Preview on a non-compliant machine, but you'll have the full WSL2 available. This is the option available for now.

[ChrisGuyML]

My perspective is that WSL2 is the most significant addition to Windows.

The integration of Linux under Windows means that Linux development can be shifted to Windows with all the support tools, such as Visual Studio, available making this the ideal development platform. That being said, the full WSL 2 platform needs to be available under Windows 10 Pro release as many companies, mine included, have strict update policies that don't include "Insider Program Development" releases. Upgrading hardware is also done on a fixed schedule, so moving to Windows 11 isn't an option for the next couple of years.

The only other Linux wish is for the C++/CLI language, that would make the switch to C# much faster as it was under Windows.

[Hashbrown777]

Yep, I've created an issue at #7940 if you wanted to follow if it progresses

[stopal]

Is there an explanation why after nearly 2 years this still isnt in the stable build?
no rant, just a honest question ;)

[TristisOris]

please confirm that win10 will never get --mount option.
21H2 still nothing.

[EdisAganovic]

2023. almost... One more reason for me to hate Microsoft more and more...

[Hashbrown777]

Biswa96 Nov 17

The WSL from Windows Store now supports latest Windows 10. Please make sure that your machine is fully up to date. The Windows Update required is KB5020030.

@cglmrfreeman https://aka.ms/wslstorepage
#7940 I don't think it'll come to Windows by default any time soon

[biggestsonicfan]

Oh that's not helpful. I didn't know I needed the store version...

[Hashbrown777]

Oh that's not helpful. I didn't know I needed the store version...

That's why Biswa started the thread with that vital piece of information...

I mean, you dont "need" it, like you already see you have wsl installed through Windows' optional features. This particular issue, though, is a feature that was literally just implemented/fixed. If you expect that to trickle down through windows update immediately then that's not going to happen; you'll need to get the bleeding edge version from a more direct source.

That's the same with all software that goes to end-users via package managers. On linux a common thing you'll hear for a bug is "here's a fix I made now, you'll need to compile from source [until it makes its way upstream and then through the repositories]".
OpenSSH on windows, as another example I've come across, has an issue with PKCS11 that was resolved earlier this year, but through windows update you can only get version 8.1, so you'll need to install ssh through that github to get 8.9.

The alternative was to use Windows Insider to be on the Dev channel of windows update.
For wsl specifically though, the store version has been advertised for a good while, and billed not as an alternative but actually the proper way to get it.

[biggestsonicfan]

Revisiting this by uninstalling the "Windows Subsystem for Linux" in Windows' optional features, installing the store version, only to find out the store version is required to have the optional feature installed. I was under the impression they were two separate channels of development, not a bandaid patch on top of the optional feature.

[Hashbrown777]

It's because the optional feature installs other OS infrastructure that WSL requires that isn't in Win10 by default, things that aren't under the WSL project at all and thus aren't in the "Windows Store version". That's why it requires a restart where the WSL software itself doesn't. So it's not that the store version patches the regular wsl install in any way, the two WSL versions are separate installs, and you can run them independently.

If you managed to delete the non-store wsl specifically (or somehow manually installed the other prerequisite OS stuff without the WSL software) the store version would continue to work.
Windows 11, for example, does not require the optional feature, as it comes with the required infrastructure baked into the OS itself, and the store version will just work.

At any rate I don't think of them as different 'channels of development', they're different releases; going back to the openssh example (which is also an optional feature, albeit the Win10 settings window, not the win7 exe where wsl sits) they have a source git repo, and the version pushed through windows update is much older but is expected to receive the current version in the future.