Where is the Ubuntu file system root directory in Windows Subsystem for Linux and vice versa?
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?
windows-subsystem-for-linux
add a comment |
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?
windows-subsystem-for-linux
20
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
– Rich Turner
Nov 14 '17 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.
– Danny Staple
Mar 1 '18 at 11:56
Although it looks like on boxes with more recent updates - this no longer happens.
– Danny Staple
Mar 1 '18 at 12:04
2
@DannyStaple If you need to change the permissions on files/folders in your Linux distro from Windows, usewsl.exe
, e.g.wsl chmod 600 ~/.ssh/id*
- do not copy files into these folders via the Windows filesystem.
– Rich Turner
Mar 2 '18 at 2:14
add a comment |
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?
windows-subsystem-for-linux
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?
windows-subsystem-for-linux
windows-subsystem-for-linux
edited Aug 3 '18 at 15:28
Bruno Bronosky
50349
50349
asked Apr 21 '16 at 10:06
JulyJuly
1,848355
1,848355
20
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
– Rich Turner
Nov 14 '17 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.
– Danny Staple
Mar 1 '18 at 11:56
Although it looks like on boxes with more recent updates - this no longer happens.
– Danny Staple
Mar 1 '18 at 12:04
2
@DannyStaple If you need to change the permissions on files/folders in your Linux distro from Windows, usewsl.exe
, e.g.wsl chmod 600 ~/.ssh/id*
- do not copy files into these folders via the Windows filesystem.
– Rich Turner
Mar 2 '18 at 2:14
add a comment |
20
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
– Rich Turner
Nov 14 '17 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.
– Danny Staple
Mar 1 '18 at 11:56
Although it looks like on boxes with more recent updates - this no longer happens.
– Danny Staple
Mar 1 '18 at 12:04
2
@DannyStaple If you need to change the permissions on files/folders in your Linux distro from Windows, usewsl.exe
, e.g.wsl chmod 600 ~/.ssh/id*
- do not copy files into these folders via the Windows filesystem.
– Rich Turner
Mar 2 '18 at 2:14
20
20
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
– Rich Turner
Nov 14 '17 at 18:34
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
– Rich Turner
Nov 14 '17 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.
– Danny Staple
Mar 1 '18 at 11:56
@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.
– Danny Staple
Mar 1 '18 at 11:56
Although it looks like on boxes with more recent updates - this no longer happens.
– Danny Staple
Mar 1 '18 at 12:04
Although it looks like on boxes with more recent updates - this no longer happens.
– Danny Staple
Mar 1 '18 at 12:04
2
2
@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.– Rich Turner
Mar 2 '18 at 2:14
@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.– Rich Turner
Mar 2 '18 at 2:14
add a comment |
5 Answers
5
active
oldest
votes
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>AppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
- benhillis
In earlier iterations of Windows Subsystem for Linux, the Ubuntu file system was at %localappdata%Lxss
(e.g., C:UsersUsernameAppDataLocalLxss
- 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%lxssrootfs
as the backing storage. In addition, a
few additional VolFs mount points exist, most notably/root
and
/home
which are mounted using%LocalAppData%lxssroot
and
%LocalAppData%lxsshome
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.
Source: Dustin Kirkland's blog, howtogeek
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 '16 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 usingattrib -s -h lxss
which will unmark it as a system directory also.
– developerbmw
Aug 3 '16 at 10:59
3
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.
– NicholasJohn16
Aug 10 '16 at 18:36
8
@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!
– Rich Turner
Nov 7 '16 at 23:16
3
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.
– Rich Turner
Nov 14 '17 at 18:32
|
show 15 more comments
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%lxsshome{username}
or:
C:Users{user}AppDataLocallxss{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.
My machine can't find: "C:Users{user}AppDataLocalLxss{username}" or "%localappdata%Lxsshome{username}" but "C:Users{user}AppDataLocallxss{username}" works. I.E. use "lxss" NOT "Lxss"
– Joe Codeswell user601770
Aug 17 '16 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 '16 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%AppDataLocallxss
– jla
Dec 1 '16 at 16:10
8
Note that this folder (lxss) did not appear in my windows explorer listing of folders in AppDataLocal, 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 '16 at 20:52
Alternatively, you can go to the Desktop, right-click "New->Shortcut" and paste a path like C:UsersyournameAppDataLocallxsshomeyourname
– Colin D
Dec 20 '16 at 20:57
|
show 2 more comments
If you install Linux from MS Market:
- Free Ubuntu in Windows store
- Free Open Suse in Windows store
they placed distros under:
$ cat /proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Lxss/{861c29b4-ebe2-49a5-8a22-7e53a27934a0}/BasePath
C:UsersuserAppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
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_USERSoftwareMicrosoftWindowsCurrentVersionLxss -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_USERSoftwareMicrosoftWindowsCurrentVersionLxss$DEFAULT_LXSS_ID -name BasePath | Format-List -property "BasePath"
%LocalAppData%PackagesCanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgscLocalState
PPS. https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-not-change-linux-files-using-windows-apps-and-tools/
add a comment |
The only thing that worked for me was %localappdata%lxsshome{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:UsersWINDOWS-USERAppDataLocal
, 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.
wow good tip, had the same problem
– Nicolas Mommaerts
Feb 19 '18 at 12:08
add a comment |
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/
Does not work for me. It opens command prompt and launches bash.
– blablatros
May 28 '17 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 '17 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 pressedls -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.
– thinksinbinary
Jun 25 '17 at 14:00
add a comment |
protected by Community♦ Aug 11 '16 at 17:44
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
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>AppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
- benhillis
In earlier iterations of Windows Subsystem for Linux, the Ubuntu file system was at %localappdata%Lxss
(e.g., C:UsersUsernameAppDataLocalLxss
- 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%lxssrootfs
as the backing storage. In addition, a
few additional VolFs mount points exist, most notably/root
and
/home
which are mounted using%LocalAppData%lxssroot
and
%LocalAppData%lxsshome
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.
Source: Dustin Kirkland's blog, howtogeek
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 '16 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 usingattrib -s -h lxss
which will unmark it as a system directory also.
– developerbmw
Aug 3 '16 at 10:59
3
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.
– NicholasJohn16
Aug 10 '16 at 18:36
8
@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!
– Rich Turner
Nov 7 '16 at 23:16
3
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.
– Rich Turner
Nov 14 '17 at 18:32
|
show 15 more comments
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>AppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
- benhillis
In earlier iterations of Windows Subsystem for Linux, the Ubuntu file system was at %localappdata%Lxss
(e.g., C:UsersUsernameAppDataLocalLxss
- 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%lxssrootfs
as the backing storage. In addition, a
few additional VolFs mount points exist, most notably/root
and
/home
which are mounted using%LocalAppData%lxssroot
and
%LocalAppData%lxsshome
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.
Source: Dustin Kirkland's blog, howtogeek
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 '16 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 usingattrib -s -h lxss
which will unmark it as a system directory also.
– developerbmw
Aug 3 '16 at 10:59
3
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.
– NicholasJohn16
Aug 10 '16 at 18:36
8
@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!
– Rich Turner
Nov 7 '16 at 23:16
3
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.
– Rich Turner
Nov 14 '17 at 18:32
|
show 15 more comments
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>AppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
- benhillis
In earlier iterations of Windows Subsystem for Linux, the Ubuntu file system was at %localappdata%Lxss
(e.g., C:UsersUsernameAppDataLocalLxss
- 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%lxssrootfs
as the backing storage. In addition, a
few additional VolFs mount points exist, most notably/root
and
/home
which are mounted using%LocalAppData%lxssroot
and
%LocalAppData%lxsshome
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.
Source: Dustin Kirkland's blog, howtogeek
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>AppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
- benhillis
In earlier iterations of Windows Subsystem for Linux, the Ubuntu file system was at %localappdata%Lxss
(e.g., C:UsersUsernameAppDataLocalLxss
- 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%lxssrootfs
as the backing storage. In addition, a
few additional VolFs mount points exist, most notably/root
and
/home
which are mounted using%LocalAppData%lxssroot
and
%LocalAppData%lxsshome
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.
Source: Dustin Kirkland's blog, howtogeek
edited Oct 26 '17 at 6:22
muru
1
1
answered Apr 21 '16 at 10:34
souravcsouravc
27.7k1378108
27.7k1378108
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 '16 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 usingattrib -s -h lxss
which will unmark it as a system directory also.
– developerbmw
Aug 3 '16 at 10:59
3
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.
– NicholasJohn16
Aug 10 '16 at 18:36
8
@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!
– Rich Turner
Nov 7 '16 at 23:16
3
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.
– Rich Turner
Nov 14 '17 at 18:32
|
show 15 more comments
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 '16 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 usingattrib -s -h lxss
which will unmark it as a system directory also.
– developerbmw
Aug 3 '16 at 10:59
3
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.
– NicholasJohn16
Aug 10 '16 at 18:36
8
@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!
– Rich Turner
Nov 7 '16 at 23:16
3
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.
– Rich Turner
Nov 14 '17 at 18:32
14
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 '16 at 14:04
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 '16 at 14:04
3
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.– developerbmw
Aug 3 '16 at 10:59
@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.– developerbmw
Aug 3 '16 at 10:59
3
3
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.
– NicholasJohn16
Aug 10 '16 at 18:36
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.
– NicholasJohn16
Aug 10 '16 at 18:36
8
8
@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!
– Rich Turner
Nov 7 '16 at 23:16
@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!
– Rich Turner
Nov 7 '16 at 23:16
3
3
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.– Rich Turner
Nov 14 '17 at 18:32
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.– Rich Turner
Nov 14 '17 at 18:32
|
show 15 more comments
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%lxsshome{username}
or:
C:Users{user}AppDataLocallxss{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.
My machine can't find: "C:Users{user}AppDataLocalLxss{username}" or "%localappdata%Lxsshome{username}" but "C:Users{user}AppDataLocallxss{username}" works. I.E. use "lxss" NOT "Lxss"
– Joe Codeswell user601770
Aug 17 '16 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 '16 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%AppDataLocallxss
– jla
Dec 1 '16 at 16:10
8
Note that this folder (lxss) did not appear in my windows explorer listing of folders in AppDataLocal, 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 '16 at 20:52
Alternatively, you can go to the Desktop, right-click "New->Shortcut" and paste a path like C:UsersyournameAppDataLocallxsshomeyourname
– Colin D
Dec 20 '16 at 20:57
|
show 2 more comments
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%lxsshome{username}
or:
C:Users{user}AppDataLocallxss{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.
My machine can't find: "C:Users{user}AppDataLocalLxss{username}" or "%localappdata%Lxsshome{username}" but "C:Users{user}AppDataLocallxss{username}" works. I.E. use "lxss" NOT "Lxss"
– Joe Codeswell user601770
Aug 17 '16 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 '16 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%AppDataLocallxss
– jla
Dec 1 '16 at 16:10
8
Note that this folder (lxss) did not appear in my windows explorer listing of folders in AppDataLocal, 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 '16 at 20:52
Alternatively, you can go to the Desktop, right-click "New->Shortcut" and paste a path like C:UsersyournameAppDataLocallxsshomeyourname
– Colin D
Dec 20 '16 at 20:57
|
show 2 more comments
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%lxsshome{username}
or:
C:Users{user}AppDataLocallxss{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.
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%lxsshome{username}
or:
C:Users{user}AppDataLocallxss{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.
edited Apr 14 '18 at 8:48
Louis
1631310
1631310
answered Aug 10 '16 at 18:35
NicholasJohn16NicholasJohn16
57143
57143
My machine can't find: "C:Users{user}AppDataLocalLxss{username}" or "%localappdata%Lxsshome{username}" but "C:Users{user}AppDataLocallxss{username}" works. I.E. use "lxss" NOT "Lxss"
– Joe Codeswell user601770
Aug 17 '16 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 '16 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%AppDataLocallxss
– jla
Dec 1 '16 at 16:10
8
Note that this folder (lxss) did not appear in my windows explorer listing of folders in AppDataLocal, 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 '16 at 20:52
Alternatively, you can go to the Desktop, right-click "New->Shortcut" and paste a path like C:UsersyournameAppDataLocallxsshomeyourname
– Colin D
Dec 20 '16 at 20:57
|
show 2 more comments
My machine can't find: "C:Users{user}AppDataLocalLxss{username}" or "%localappdata%Lxsshome{username}" but "C:Users{user}AppDataLocallxss{username}" works. I.E. use "lxss" NOT "Lxss"
– Joe Codeswell user601770
Aug 17 '16 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 '16 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%AppDataLocallxss
– jla
Dec 1 '16 at 16:10
8
Note that this folder (lxss) did not appear in my windows explorer listing of folders in AppDataLocal, 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 '16 at 20:52
Alternatively, you can go to the Desktop, right-click "New->Shortcut" and paste a path like C:UsersyournameAppDataLocallxsshomeyourname
– Colin D
Dec 20 '16 at 20:57
My machine can't find: "C:Users{user}AppDataLocalLxss{username}" or "%localappdata%Lxsshome{username}" but "C:Users{user}AppDataLocallxss{username}" works. I.E. use "lxss" NOT "Lxss"
– Joe Codeswell user601770
Aug 17 '16 at 15:52
My machine can't find: "C:Users{user}AppDataLocalLxss{username}" or "%localappdata%Lxsshome{username}" but "C:Users{user}AppDataLocallxss{username}" works. I.E. use "lxss" NOT "Lxss"
– Joe Codeswell user601770
Aug 17 '16 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 '16 at 16:07
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 '16 at 16:07
1
1
@JoeCodeswelluser601770 That's odd. Windows filesystems are normally case insensitive. I can enter %localappdata%Lxss or %localappdata%lxss and both go to %HOMEPATH%AppDataLocallxss
– jla
Dec 1 '16 at 16:10
@JoeCodeswelluser601770 That's odd. Windows filesystems are normally case insensitive. I can enter %localappdata%Lxss or %localappdata%lxss and both go to %HOMEPATH%AppDataLocallxss
– jla
Dec 1 '16 at 16:10
8
8
Note that this folder (lxss) did not appear in my windows explorer listing of folders in AppDataLocal, 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 '16 at 20:52
Note that this folder (lxss) did not appear in my windows explorer listing of folders in AppDataLocal, 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 '16 at 20:52
Alternatively, you can go to the Desktop, right-click "New->Shortcut" and paste a path like C:UsersyournameAppDataLocallxsshomeyourname
– Colin D
Dec 20 '16 at 20:57
Alternatively, you can go to the Desktop, right-click "New->Shortcut" and paste a path like C:UsersyournameAppDataLocallxsshomeyourname
– Colin D
Dec 20 '16 at 20:57
|
show 2 more comments
If you install Linux from MS Market:
- Free Ubuntu in Windows store
- Free Open Suse in Windows store
they placed distros under:
$ cat /proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Lxss/{861c29b4-ebe2-49a5-8a22-7e53a27934a0}/BasePath
C:UsersuserAppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
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_USERSoftwareMicrosoftWindowsCurrentVersionLxss -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_USERSoftwareMicrosoftWindowsCurrentVersionLxss$DEFAULT_LXSS_ID -name BasePath | Format-List -property "BasePath"
%LocalAppData%PackagesCanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgscLocalState
PPS. https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-not-change-linux-files-using-windows-apps-and-tools/
add a comment |
If you install Linux from MS Market:
- Free Ubuntu in Windows store
- Free Open Suse in Windows store
they placed distros under:
$ cat /proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Lxss/{861c29b4-ebe2-49a5-8a22-7e53a27934a0}/BasePath
C:UsersuserAppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
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_USERSoftwareMicrosoftWindowsCurrentVersionLxss -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_USERSoftwareMicrosoftWindowsCurrentVersionLxss$DEFAULT_LXSS_ID -name BasePath | Format-List -property "BasePath"
%LocalAppData%PackagesCanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgscLocalState
PPS. https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-not-change-linux-files-using-windows-apps-and-tools/
add a comment |
If you install Linux from MS Market:
- Free Ubuntu in Windows store
- Free Open Suse in Windows store
they placed distros under:
$ cat /proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Lxss/{861c29b4-ebe2-49a5-8a22-7e53a27934a0}/BasePath
C:UsersuserAppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
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_USERSoftwareMicrosoftWindowsCurrentVersionLxss -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_USERSoftwareMicrosoftWindowsCurrentVersionLxss$DEFAULT_LXSS_ID -name BasePath | Format-List -property "BasePath"
%LocalAppData%PackagesCanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgscLocalState
PPS. https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-not-change-linux-files-using-windows-apps-and-tools/
If you install Linux from MS Market:
- Free Ubuntu in Windows store
- Free Open Suse in Windows store
they placed distros under:
$ cat /proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Lxss/{861c29b4-ebe2-49a5-8a22-7e53a27934a0}/BasePath
C:UsersuserAppDataLocalPackagesCanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgscLocalState
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_USERSoftwareMicrosoftWindowsCurrentVersionLxss -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_USERSoftwareMicrosoftWindowsCurrentVersionLxss$DEFAULT_LXSS_ID -name BasePath | Format-List -property "BasePath"
%LocalAppData%PackagesCanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgscLocalState
PPS. https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-not-change-linux-files-using-windows-apps-and-tools/
edited Oct 24 '18 at 7:05
paul-emil
32
32
answered Sep 13 '17 at 14:54
gavenkoagavenkoa
657814
657814
add a comment |
add a comment |
The only thing that worked for me was %localappdata%lxsshome{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:UsersWINDOWS-USERAppDataLocal
, 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.
wow good tip, had the same problem
– Nicolas Mommaerts
Feb 19 '18 at 12:08
add a comment |
The only thing that worked for me was %localappdata%lxsshome{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:UsersWINDOWS-USERAppDataLocal
, 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.
wow good tip, had the same problem
– Nicolas Mommaerts
Feb 19 '18 at 12:08
add a comment |
The only thing that worked for me was %localappdata%lxsshome{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:UsersWINDOWS-USERAppDataLocal
, 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.
The only thing that worked for me was %localappdata%lxsshome{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:UsersWINDOWS-USERAppDataLocal
, 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.
answered Jun 9 '17 at 17:02
thinksinbinarythinksinbinary
4072717
4072717
wow good tip, had the same problem
– Nicolas Mommaerts
Feb 19 '18 at 12:08
add a comment |
wow good tip, had the same problem
– Nicolas Mommaerts
Feb 19 '18 at 12:08
wow good tip, had the same problem
– Nicolas Mommaerts
Feb 19 '18 at 12:08
wow good tip, had the same problem
– Nicolas Mommaerts
Feb 19 '18 at 12:08
add a comment |
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/
Does not work for me. It opens command prompt and launches bash.
– blablatros
May 28 '17 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 '17 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 pressedls -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.
– thinksinbinary
Jun 25 '17 at 14:00
add a comment |
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/
Does not work for me. It opens command prompt and launches bash.
– blablatros
May 28 '17 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 '17 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 pressedls -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.
– thinksinbinary
Jun 25 '17 at 14:00
add a comment |
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/
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/
edited Oct 1 '17 at 15:26
mwfearnley
1,02221120
1,02221120
answered Feb 21 '17 at 20:19
KangaroooKangarooo
3,03442334
3,03442334
Does not work for me. It opens command prompt and launches bash.
– blablatros
May 28 '17 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 '17 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 pressedls -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.
– thinksinbinary
Jun 25 '17 at 14:00
add a comment |
Does not work for me. It opens command prompt and launches bash.
– blablatros
May 28 '17 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 '17 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 pressedls -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.
– thinksinbinary
Jun 25 '17 at 14:00
Does not work for me. It opens command prompt and launches bash.
– blablatros
May 28 '17 at 19:38
Does not work for me. It opens command prompt and launches bash.
– blablatros
May 28 '17 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 '17 at 2:24
@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 '17 at 2:24
1
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.– thinksinbinary
Jun 25 '17 at 14:00
@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.– thinksinbinary
Jun 25 '17 at 14:00
add a comment |
protected by Community♦ Aug 11 '16 at 17:44
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
20
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
– Rich Turner
Nov 14 '17 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.
– Danny Staple
Mar 1 '18 at 11:56
Although it looks like on boxes with more recent updates - this no longer happens.
– Danny Staple
Mar 1 '18 at 12:04
2
@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.– Rich Turner
Mar 2 '18 at 2:14