There are too many rough edges right now but I am hopeful. Also please note that this feature comes with the limitation that only physical disks can be attached to WSL 2. Local filesystem is blind to what docker's doing in that storage space. I also can't wait for Terminal to be my goto terminal (wsltty is best right now). Note, that I don't mean that I wanna browse them inside the file explorer - I know it can be done by typing in the explorer \\wsl$\. Windows Defender Real-time slow down… protection. By default, wsl --mount attempts to mount the disk as ext4. Finding the Linux File System from Windows with Environment Variables Hitesh Patel Visual Effects Supervisor/Shoot Supervisor/Aerial Unit Director I just installed WSL2 on my home computer for the first time and something i notice that i don't see on my work computer is that WSL2 has dramatically lower network speed (wget or git clone tested).Speeds on WSL seem to be about 10-20 kb/s wheras windows download speed seem to be correlating to my ISP spec of 100/10 Mbps or … To specify a filesystem, or for more advanced scenarios, check out Mount a disk in WSL 2. The tip above may speedup things a little bit, but not so. If you will be using your WSL Linux distribution to access project files on the Windows file system, [...] you will achieve faster performance across the OS files systems by using WSL 1. WSL allows you to work with both file systems as if they were one. There is one more thing bringing your performance down: ... including WSL. While I have experimented already with WSL 1 for some time, I switched to WSL 2 since it became generally available in Windows 10 Version 2004 (apparently it was backported to 1903 and 1909). I can't wait for WSL 2 to really perfect the workflow. [ 0.363323] 9p: Installing v9fs 9p2000 file system support [ 0.363336] FS-Cache: Netfs '9p' registered for caching [ 0.398989] 9pnet: Installing 9P2000 support Please see this Github thread for further discussion on this issue. The Microsoft documentation mention this behavior:. ... Accessing Windows files from Linux is considerably slower than using the native Linux file system. At this time, it’s not possible to attach a single partition. If your project files are stored on the Windows filesystem and accessed/launched from WSL2, then yes, it's "normal" (or rather, known). The slow filesystem operations can definitely be annoying at times especially when working in git repositories or with nodejs packages. The file system is one of the most useful things to share with WSL. Can't start WSL 2 distribution and only see 'WSL 2' in output 2. mount wsl file system with umask 0022 /etc/wsl.conf [automount] enabled = true options = “metadata,umask=22,fmask=11” 3. try to open shell as administrator 4. check internet speed on both wsl 1 and wsl 2 with same endpoint 5. try with the latest windows insider preview build… there may be … Windows build number: 10.0.19041.84 Dist: Ubuntu 18.04 LTS. My main reason for switching to WSL2 was much better Linux support (kernel and syscall stuff), and for a long time everything was fine. By contrast, mounting a local directory in your container, docker needs to coordinate with the underlying filesystem, making sure any changes you make in the container are properly reflected locally; this adds significant overhead and is super slow on WSL. This could be slow and several features weren’t available. The Windows 10 file system is mounted as a directory in Linux while your Linux file system will be mounted as a folder in Windows. If I would have to guess I would say the files are stored in the same hard-drive that the os is stored. I've installed wsl2 on my windows machine and I was not able to figure out where the files are actually stored. ... check Use the WSL 2 …