572

I have installed Ubuntu subsystem on Windows 10 (after enabling feature in settings), but where is the Ubuntu file system root directory located in the drive?

13
  • 43
    PLEASE NOTE We (the WSL team) STRONGLY recommend you do NOT spelunk into the Linux distro data folders ). If you do, data loss and/or corruption is VERY likely We are working to improve this interop scenario and will announce any progress on our blog: blogs.msdn.microsoft.com/commandline Nov 14, 2017 at 18:34
  • @RichTurner I've found there's a very specific (and annoying) reason - corporate policies marking the .ssh folder with the wrong permissions repeatedly means needing to mark the structure as "off limits" to the corporate scripts. But generally - I'd agree with you. Mar 1, 2018 at 11:56
  • Although it looks like on boxes with more recent updates - this no longer happens. Mar 1, 2018 at 12:04
  • 4
    @DannyStaple If you need to change the permissions on files/folders in your Linux distro from Windows, use wsl.exe, e.g. wsl chmod 600 ~/.ssh/id* - do not copy files into these folders via the Windows filesystem. Mar 2, 2018 at 2:14
  • 1
    @mehrdad WSL implements a P9 fileserver, exposing/marshalling files from/to the distro's filesystem as any P9 fileserver would. This way there is no NTFS metadata to marshal. Please watch Craig Loewen & Ben Hillis' session at Build 2919 for more info May 30, 2019 at 2:58

6 Answers 6

650

For Ubuntu installed from the Windows store:

Each distribution you install through the store is installed to that application's appdata directory. For example: C:\Users\<username>\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState - benhillis

For WSL2 you can access to home directory from windows (Windows 10 build 18342) like this :

\\wsl$

In earlier iterations of Windows Subsystem for Linux, the Ubuntu file system was at %localappdata%\Lxss (e.g., C:\Users\Username\AppData\Local\Lxss - replace the Username with your Username on Windows). See the WSL blog post on File System Support:

The primary file system used by WSL is VolFs. It is used to store the Linux system files, as well as the content of your Linux home directory. As such, VolFs supports most features the Linux VFS provides, including Linux permissions, symbolic links, FIFOs, sockets, and device files.

VolFs is used to mount the VFS root directory, using %LocalAppData%\lxss\rootfs as the backing storage. In addition, a few additional VolFs mount points exist, most notably /root and /home which are mounted using %LocalAppData%\lxss\root and %LocalAppData%\lxss\home respectively. The reason for these separate mounts is that when you uninstall WSL, the home directories are not removed by default, so any personal files stored there will be preserved.

CAUTION

Creating/modifying any files within the Linux subsystem using Windows apps & tools can cause Data corruption and data loss in Ubuntu subsystem! (Thanks to Rich Turner for suggesting these words of caution!) This is absolutely not supported. From the same blog post:

Interoperability with Windows

While VolFs files are stored in regular files on Windows in the directories mentioned above, interoperability with Windows is not supported. If a new file is added to one of these directories from Windows, it lacks the EAs needed by VolFs, so VolFs doesn’t know what to do with the file and simply ignores it. Many editors will also strip the EAs when saving an existing file, again making the file unusable in WSL.


Your Windows file system is located at /mnt/c in the Bash shell environment.

enter image description here

Source: Dustin Kirkland's blog, howtogeek

23
  • 14
    Lxss was hidden on my file system... caused a bit of head scratching for an infuriating minute or two. Now I've created a shortcut, but I still can't seem to unhide it.
    – Ogaday
    Jun 16, 2016 at 14:04
  • 3
    @Ogaday you can't unhide it using the properties window because it's marked as a system directory. You can unhide it using attrib -s -h lxss which will unmark it as a system directory also. Aug 3, 2016 at 10:59
  • 4
    It looks like the location has either changed or different between systems as mine is in a different location. I've posted below with my location. Aug 10, 2016 at 18:36
  • 9
    @souravc Could you please add an important note to the top of your answer, STRONGLY recommending against creating/modifying any files within LXSS using Windows apps & tools: Data corruption and loss is very likely if you do! Nov 7, 2016 at 23:16
  • 9
    Please read the post mentioned above: blogs.msdn.microsoft.com/commandline/2016/11/17/…. It's safe to access the Windows filesystem from WSL which is why we mount your drives under /mnt/<drive>/, but is NOT safe (yet) to access Linux filesystem from Windows which is why we don't provide easy access to the distro filesystems. Nov 14, 2017 at 18:32
54

This seems to have changed since Bash was originally introduced, and does not apply to distributions from the Windows Store, or maybe it is not consistent for all systems as my home directory is located in another location:

%localappdata%\lxss\home\{username}

or:

C:\Users\{user}\AppData\Local\lxss\{username}

Where {user} is your Windows Username and {username} is your UNIX Username set during install.

So the root directory would be:

%localappdata%\lxss

Note that the root directory may not be visible in Windows Explorer from the %localappdata% directory. You should be able to access it anyways by typing it in the 'address bar' of Explorer.

7
  • 1
    My machine can't find: "C:\Users\{user}\AppData\Local\Lxss\{username}" or "%localappdata%\Lxss\home\{username}" but "C:\Users\{user}\AppData\Local\lxss\{username}" works. I.E. use "lxss" NOT "Lxss" Aug 17, 2016 at 15:52
  • My system has the rootfs subdirectory, but rootfs/home is empty while ./home has my user account and files. It seems safest to just go to %localappdata%\lxss and then explore around from there to see which layout you have, plus directly browsing to that address avoids issues with the lxss directory being hidden.
    – jla
    Dec 1, 2016 at 16:07
  • 1
    @JoeCodeswelluser601770 That's odd. Windows filesystems are normally case insensitive. I can enter %localappdata%\Lxss or %localappdata%\lxss and both go to %HOMEPATH%\AppData\Local\lxss
    – jla
    Dec 1, 2016 at 16:10
  • 8
    Note that this folder (lxss) did not appear in my windows explorer listing of folders in AppData\Local, even with hidden folders view enabled. I had to manually paste add the folder lxss to the explorer bar to get to the files here e.g. edit the folder "url" to there
    – Colin D
    Dec 20, 2016 at 20:52
  • Alternatively, you can go to the Desktop, right-click "New->Shortcut" and paste a path like C:\Users\yourname\AppData\Local\lxss\home\yourname
    – Colin D
    Dec 20, 2016 at 20:57
17

If you install Linux from MS Market:

they placed distros under:

$ cat /proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Lxss/\{861c29b4-ebe2-49a5-8a22-7e53a27934a0\}/BasePath
C:\Users\user\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState

Default distro defined by:

bash# cat /proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Lxss/DefaultDistribution
{861c29b4-ebe2-49a5-8a22-7e53a27934a0}

Linux root is deeper:

c:/Users/user/AppData/Local/Packages/46932SUSE.openSUSELeap42.2_022rs5jcyhyac/LocalState/rootfs

PS. I used Cygwin to explore registry keys.

If using PowerShell for the same goal, the commands would be:

# obtain the value of the ID of the default Linux distribution (and store it in a variable to avoid escaping characters issues):
$DEFAULT_LXSS_ID = (Get-ItemPropertyValue -Path REGISTRY::HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Lxss\ -name DefaultDistribution)

# which will have a value like:
echo  $DEFAULT_LXSS_ID
{bde539d6-0c87-4e12-9599-1dcd623fbf07}

# display the directory containing the rootfs Windows directory (mapped to the / Linux directory)
Get-ItemPropertyValue -Path REGISTRY::HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Lxss\$DEFAULT_LXSS_ID -name BasePath | Format-List -property "BasePath"
%LocalAppData%\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState

PPS. https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-not-change-linux-files-using-windows-apps-and-tools/

3
  • 1
    It's really good that you made this more-useable (for a bigger variety of different situations) by noting that "[you] used Cygwin to explore registry keys." Sep 29, 2020 at 18:26
  • 2
    This is the answer that helped me the most. Somehow I had set a custom location for the Basepath during inital setup. I was able to read that location by manually looking it up in the windows registry editor.
    – Zciurus
    Dec 30, 2020 at 15:13
  • 1
    HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss\{GUID}/BasePath. Very nice. That registry value helped me find the location of my distro. Thanks! Dec 13, 2022 at 17:52
7

You can quickly open Bash from a File Explorer window of the opened folder by typing bash in the location bar.

It's enough.

Also you can add a context menu item. I personally don`t recommend it if not needed, because adding shortcuts to the context menu uses more RAM.

https://www.howtogeek.com/270810/how-to-quickly-launch-a-bash-shell-from-windows-10s-file-explorer/

3
  • Does not work for me. It opens command prompt and launches bash.
    – blablatros
    May 28, 2017 at 19:38
  • @blablatros yes but in folder in bash in witch you had explorer open when writing in explorer bar bash and pressing enter. Try in My Documents folder opened Windows Explorer folder and in location bar write bash and it will open ubuntu bash in that folder already :)
    – Kangarooo
    Jun 17, 2017 at 2:24
  • 1
    @Kangarooo: I want to access the files through the windows 10 gui as well as vice versa. In my answer above, i found out how to locate the bash directory through the Windows 10 files explorer, and so I proceeded to copy some files from my external hard drive into that directory. However, when I opened the bash terminal and pressed ls -a, it didn't show the files I added. Bash was not recognizing the files I dropped in through windows file explorer, which for me has completely defeated the purpose of installing bash on windows.
    – user453720
    Jun 25, 2017 at 14:00
5

The only thing that worked for me was %localappdata%\lxss\home\{username}, where the {username} is your BASH username you gave it during the installation. For some reason, after showing hidden folder's lxss refuses to appear in C:\Users\WINDOWS-USER\AppData\Local\, and also giving the full C:\ path with windows and BASH username does not work either.

And please create a desktop shortcut for what works.

0
4

For those who are looking for the image location:

C:\Users\\[username]\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\ext4.vhdx

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .