Permission Denied For Folders in Mounted VHDX/VHD in WSL #1199

ghazi94 · 2016-10-12T18:46:38Z

I have created a VHDX/VHD (GUID/MBR type) file in Windows 10.
It is mounted as an NTFS formatted drive with drive letter X:. When I open the bash (Ubuntu on Windows 10/WSL), I am able to
cd /mnt/x
However, when I do ls, i get permission denied for all the files. Also, I am not able to create directory even with sudo. Same problem with chmod, chown, etc.

I have also tried to grant permissions to everyone through icacls in Windows through command line as well as through the GUI.

Attached the screenshots below:

Windows Explorer

### Bash

### Bash - Displaying permissions

I think the problem is that the way NTFS gets mounted on Windows. The mounted mode is being treated as a read-only mode by the Ubuntu Bash.

The text was updated successfully, but these errors were encountered:

fpqc · 2016-10-12T19:12:22Z

@benhillis This used to work pre-Anniversary edition. Are there any plans to get it working again?

ghazi94 · 2016-10-12T19:42:41Z

This was working till yesterday. Today's update screwed it up! @fpqc

benhillis · 2016-10-12T20:29:01Z

Interesting, I'll sync up with a couple people and see what is up here.

benhillis · 2016-10-12T20:33:02Z

@ghazi94 - What build were you running before yesterday's update?

fpqc · 2016-10-12T20:36:16Z

@benhillis The case I am thinking of was where you mounted the vhdx as VolFS (mount to a folder inside LXSS, for example) rather than DriveFS, but it was a similar problem.

ghazi94 · 2016-10-13T07:36:20Z

@benhillis I will update the build number before and after the update as soon as I reach home (It's my personal pc)

wimpunk · 2016-10-13T08:35:08Z

I got here because I got the same problem as @ghazi94... Using the latest normal version worked until yesterday. I've got a windows update today and now it is broken. Don't know the version numbers.

ghazi94 · 2016-10-14T09:52:02Z

@benhillis Current build is 14393.321
Couldn't find how to get the build number before the update.

Manouchehri · 2016-10-14T14:36:31Z

The permissions seem to be identical between my VHD and physical partition, but WSL cannot access the VHD.

PS T:\> [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.14942.0 Microsoft Windows NT 10.0.14942.0

VHD

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS T:\> icacls T:\
T:\ BUILTIN\Administrators:(F)
    BUILTIN\Administrators:(OI)(CI)(IO)(F)
    NT AUTHORITY\SYSTEM:(F)
    NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
    NT AUTHORITY\Authenticated Users:(M)
    NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(M)
    BUILTIN\Users:(RX)
    BUILTIN\Users:(OI)(CI)(IO)(GR,GE)

Successfully processed 1 files; Failed processing 0 files

dave@universal:~$ df -h /mnt/t
Filesystem      Size  Used Avail Use% Mounted on
T:              997M   15M  983M   2% /mnt/t
dave@universal:~$ mount | grep '/mnt/'
C: on /mnt/c type drvfs (rw,noatime)
G: on /mnt/g type drvfs (rw,noatime)
T: on /mnt/t type drvfs (rw,noatime)
dave@universal:~$ ls -l /mnt/t/
ls: cannot access /mnt/t/$RECYCLE.BIN: Permission denied
ls: cannot access /mnt/t/System Volume Information: Permission denied
ls: cannot access /mnt/t/usertest: Permission denied
total 0
d????????? ? ? ? ?            ? $RECYCLE.BIN
d????????? ? ? ? ?            ? System Volume Information
d????????? ? ? ? ?            ? usertest
dave@universal:~$ touch /mnt/t/test.txt
touch: cannot touch ‘/mnt/t/test.txt’: Permission denied

Physical Partition

G:\ BUILTIN\Administrators:(F)
    BUILTIN\Administrators:(OI)(CI)(IO)(F)
    NT AUTHORITY\SYSTEM:(F)
    NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
    NT AUTHORITY\Authenticated Users:(M)
    NT AUTHORITY\Authenticated Users:(OI)(CI)(IO)(M)
    BUILTIN\Users:(RX)
    BUILTIN\Users:(OI)(CI)(IO)(GR,GE)

Successfully processed 1 files; Failed processing 0 files

dave@universal:~$ df -h /mnt/g
Filesystem      Size  Used Avail Use% Mounted on
G:              7.9G   29M  7.8G   1% /mnt/g
dave@universal:~$ mount | grep '/mnt/'
C: on /mnt/c type drvfs (rw,noatime)
G: on /mnt/g type drvfs (rw,noatime)
T: on /mnt/t type drvfs (rw,noatime)
dave@universal:~$ ls -l /mnt/g/
total 64
drwxrwxrwx 0 root root 0 Oct  4 13:53 $RECYCLE.BIN
d--------- 0 root root 0 Oct  4 15:20 System Volume Information
dave@universal:~$ touch /mnt/g/test.txt
dave@universal:~$ ls -l /mnt/g/
total 64
drwxrwxrwx 0 root root 0 Oct  4 13:53 $RECYCLE.BIN
d--------- 0 root root 0 Oct  4 15:20 System Volume Information
-rwxrwxrwx 1 root root 0 Oct 14 10:41 test.txt

mheden · 2016-10-17T12:27:02Z

I also see the problem on my VHD drive as described above (all files/directories have messed up permissions), but my physical drive also seems to have some problems (even though most of the directories are fine):

user@machine:/mnt/c$ ls -lF
ls: cannot access hiberfil.sys: Permission denied
ls: cannot access pagefile.sys: Permission denied
ls: cannot access swapfile.sys: Permission denied
total 524
drwxrwxrwx 2 root root      0 Oct  5 09:37 bin/
dr-xr-xr-x 2 root root      0 Jun 22 20:40 Boot/
-r-xr-xr-x 1 root root 400228 Oct 30  2015 bootmgr*
-r-xr-xr-x 1 root root      1 Oct 30  2015 BOOTNXT*
drwxrwxrwx 2 root root      0 Aug 25 17:03 DRIVERS/
drwxrwxrwx 2 root root      0 Aug 16 17:10 $GetCurrent/
-????????? ? ?    ?         ?            ? hiberfil.sys
drwxrwxrwx 2 root root      0 Jun 22 21:35 Intel/
-????????? ? ?    ?         ?            ? pagefile.sys
drwxrwxrwx 2 root root      0 Jul 16 13:47 PerfLogs/
drwxrwxrwx 2 root root      0 Oct  6 11:28 ProgramData/
dr-xr-xr-x 2 root root      0 Sep 20 10:33 Program Files/
dr-xr-xr-x 2 root root      0 Sep 26 19:11 Program Files (x86)/
drwxrwxrwx 2 root root      0 Aug 26 13:51 Python27/
d--------- 2 root root      0 Aug 16 18:06 Recovery/
drwxrwxrwx 2 root root      0 Aug 17 11:39 $Recycle.Bin/
-????????? ? ?    ?         ?            ? swapfile.sys

benhillis · 2016-10-17T15:16:27Z

@mheden - What you are seeing is actually expected. hiberfil.sys, pagefile.sys, and swapfile.sys are protected files.

Manouchehri · 2016-10-17T16:23:53Z

@benhillis But all VHDs shouldn't be protected? #1199 (comment)

benhillis · 2016-10-17T16:43:24Z

@Manouchehri I'm surprised you're able to see VHD's at all in bash. I thought we only exposed fixed NTFS drives.

Manouchehri · 2016-10-17T18:21:37Z

Moved to #1220 since I think I've found another issue.

IL2 · 2016-10-23T08:48:56Z

Same permission problems on 14951 and VHD drive automounted at boot (via VHDAttach):

user@wind:~$ sudo ls -l /mnt/d/
ls: cannot access '/mnt/d/$RECYCLE.BIN': Permission denied
ls: cannot access '/mnt/d/dev': Permission denied
ls: cannot access '/mnt/d/Downloads': Permission denied
ls: cannot access '/mnt/d/System Volume Information': Permission denied
total 0
d????????? ? ? ? ?            ? dev
d????????? ? ? ? ?            ? Downloads
d????????? ? ? ? ?            ? $RECYCLE.BIN
d????????? ? ? ? ?            ? System Volume Information
user@wind:~$ sudo ls -l /mnt/d/Downloads
ls: cannot access '/mnt/d/Downloads': Permission denied

I could remember it worked some build ago.

ivivanov-bg · 2016-10-24T05:37:47Z

The last working version is: 14393.0

(Uninstalling KB3194798 removes also the issue)

fpqc · 2016-10-24T05:48:27Z

@ivivanov-bg Good stuff! Thanks for rolling back to all those timebombed updates. How'd you do it?

ivivanov-bg · 2016-10-24T05:54:13Z

As I'm NOT on the insider program - this was the only update for windows which was installed - so - uninstalling it through the control panel (the old school one) and rebooting.

As all my stuff is on VHDX disk - accessing it in WSL is very very important to me - so I guess I have to live for a while without this update.

(Let's hope it won't be for very long)

ivivanov-bg · 2016-10-24T07:07:52Z

Wrong Id - the one that was uninstalled is actually: KB3194798

ghazi94 · 2016-10-24T12:55:07Z

thanks a lot @ivivanov-bg !!

andrewfinnell · 2016-10-27T20:38:35Z

Ditto problem here. No longer able to access a mounted VHDX drive.. So unfortunate the little things that stop us from being productive. What did that KB update do?

ghazi94 · 2016-10-28T06:57:52Z

Yeah .... especially when an update messes up a working application 👎

andrewfinnell · 2016-10-28T13:38:41Z

Unrelated.. (but really.. it's related), the latest Insider Preview update, which took 2 hours to install had made the OS almost unusable. I can no longer sign into my domain account when it's off the network. I get a "password changed by a different device" error when entering my password . Which is untrue as I can verify my domain account other ways.
Context menus are broken. VHD access is broken in WSL. There's a definite issue with this latest patch.

0xbadfca11 · 2016-10-30T10:42:54Z

@benhillis Windows says that mounted vhdx is fixed drive.

PS C:\> Get-Disk | Format-List FriendlyName,Model,BusType,Location,Path

FriendlyName : Virtual HD
Model        : Virtual HD
BusType      : ATA
Location     : PCI Slot 0 : Adapter 0 : Channel 0 : Device 0
Path         : \\?\ide#diskvirtual_hd______________________________1.1.0___#5&2d5f53a1&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

FriendlyName : Msft Virtual Disk
Model        : Virtual Disk
BusType      : File Backed Virtual
Location     : C:\temp.vhdx
Path         : \\?\scsi#disk&ven_msft&prod_virtual_disk#2&1f4adffe&0&000001#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

PS C:\> Get-Disk | Get-Partition

   DiskPath: \\?\scsi#disk&ven_msft&prod_virtual_disk#2&1f4adffe&0&000001#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

PartitionNumber  DriveLetter Offset                                        Size Type
---------------  ----------- ------                                        ---- ----
1                E           1048576                                     127 GB IFS


   DiskPath: \\?\ide#diskvirtual_hd______________________________1.1.0___#5&2d5f53a1&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

PartitionNumber  DriveLetter Offset                                        Size Type
---------------  ----------- ------                                        ---- ----
1                            1048576                                     500 MB IFS
2                C           525336576                                126.51 GB IFS

PS C:\> Get-Disk | Get-Partition | Get-Volume

DriveLetter FileSystemLabel FileSystem DriveType HealthStatus OperationalStatus SizeRemaining      Size
----------- --------------- ---------- --------- ------------ ----------------- -------------      ----
                            NTFS       Fixed     Healthy      OK                    465.62 MB    500 MB
E                           NTFS       Fixed     Healthy      OK                    126.89 GB    127 GB
C                           NTFS       Fixed     Healthy      OK                    100.48 GB 126.51 GB

PS C:\> mkdir E:\test1,E:\test2,E:\test3 | Out-Null
PS C:\> bash -c "ls -l /mnt/e"
ls: cannot access /mnt/e/System Volume Information: Permission denied
ls: cannot access /mnt/e/test1: Permission denied
ls: cannot access /mnt/e/test2: Permission denied
ls: cannot access /mnt/e/test3: Permission denied
total 0
d????????? ? ? ? ?            ? System Volume Information
d????????? ? ? ? ?            ? test1
d????????? ? ? ? ?            ? test2
d????????? ? ? ? ?            ? test3

ivivanov-bg · 2016-11-21T06:51:52Z

Any progress on this ??
It's a second updated rolled out which contains this issue (so I had to uninstall it manually again)

ghazi94 · 2016-11-21T10:30:51Z

It's still not labelled as an Issue yet!

jcar87 · 2016-12-07T15:10:38Z

Problem for me as well. used to work fine on Anniversary Update

ivivanov-bg · 2016-12-09T09:26:00Z

Anyone tried the latest updates: KB3200970 and KB3176929 ?
Is the issue still present there ?

ghazi94 · 2016-12-17T23:39:55Z

Yes .. its still present @ivivanov-bg

ivivanov-bg · 2017-01-13T20:14:02Z

anyone any idea if this will ever be fixed ?

I see it's still present in KB3213986

TheRealDuckboy · 2017-01-27T14:08:58Z

Still an issue as of 14393.693 (all updates installed but pending reboot for KB3216755).

Any news, anyone?

sunilmut · 2017-01-27T18:53:24Z

@TheRealDuckboy - Only security and critical fixes for WSL will be pushed out to the 14393 build. All of the major updates are currently only available to the Windows Insider builds (see our release notes). These updates will also make it to the Creators Update release.

aseering · 2017-01-27T23:38:33Z

@sunilmut -- just verifying -- did you notice that this is not a regular bug report, it's a regression report?

If a hotfix to Anniversary inadvertently breaks part of WSL, what's your policy on fixing it? I would advocate that such fixes should be prioritized if at all possible -- y'all want people applying your hotfixes, and they're not going to if hotfixes introduce regressions and start being perceived as risky.

sunilmut · 2017-01-27T23:50:12Z

@aseering - No, I did not notice that. I would agree with you assessment. Thanks for bringing it to my notice. Not much has gone for WSL in KB article(s). So, probably something outside of WSL changed that broke this (my initial view). Let me run this internally with the team.

sunilmut · 2017-01-31T00:36:43Z

I had a word about this with the team. It appears that this is a known issue, and, regressed because of an update outside of WSL. Irrespective, we understand that this is a regression. Unfortunately, and as I have been informed, the bug bar to get this fixed in Anniversary Update is high and this won't make the cut. Also, because the Creators Update release is around the corner which has a fix for this. We do owe an apology here.

fpqc · 2017-01-31T03:09:01Z

@sunilmut are you sure this is fixed in CU? It wasn't in CU a while back. This broke right before RTM of AU.

sunilmut · 2017-01-31T05:53:56Z

@fpqc That's what I have been informed by @SvenGroot. If someone here is willing to try it out in a recent Insider build, we can know for sure.

fpqc · 2017-01-31T06:10:57Z

@sunilmut Installation and extraction works, but when you try to run bash.exe, it fails with error:
0x80070003.

Repro steps: Create an empty vhdx, attach it, create a new volume formatted with ntfs, create %localappdata%\lxss, and mount the vhdx on that directory. Then lxrun /install. The installation and extraction works fine, but you get the error when you go to set up your unix accounts and also if you try to run bash.exe.

ghazi94 · 2017-02-01T11:48:09Z

I can confirm that this issue is still not resolved by the latest insider build. Same issue as mentioned in the description.

0xbadfca11 · 2017-02-02T13:09:04Z

Fixed in 15025.

dbsavage · 2017-03-09T20:26:45Z

Oxbadfca11: really? i just checked and i'm still getting the permission denied issue.... i'm pretty sure i'm on the latest version.... did you do anything else?

0xbadfca11 · 2017-03-10T05:27:23Z

dbsavage · 2017-03-10T17:10:59Z

Oxbadfca11 - that's totally it.... my bad, apologize for jumping on this thread and not realizing it was for the preview builds....

dimo414 · 2017-05-25T04:58:36Z

I started running into "Permission denied" issues once I upgraded to the Creators Update (everything was working fine before), then I started seeing things like:

$ ls data/h2
ls: cannot open directory data/h2: Permission denied

I found a strange "Deny" entry in the folder's permission in Windows Explorer (Right Click > Properties > Security > Advanced) denying my account "Special" access. Below it was an identical looking "Allow" entry. Removing the "Deny" entry allowed Bash to access the directory again.

I'm not sure where that entry came from, but I don't think it's related to WSL (it does seem new with the Creators Update though). I just wanted to share that troubleshooting step here since I initially thought it was a WSL issue. I could still access the directory normally from Explorer, so it might only crop up for people using Bash.

benhillis · 2018-06-21T00:07:34Z

Following up on this thread. Are people still seeing similar failures on the 1803 build?

fpqc · 2018-06-22T02:44:08Z

@benhillis It's not really practical to even test this anymore, since it's not just mounting a vhdx on lxss but you'd have to mount it on the app's directory. I would like to see an option to launch an lx environment off an ntfs vhdx for portability, but doing it the way we did at the beginning is pretty much a dead end now.

onomatopellan · 2018-06-22T08:49:40Z

@benhillis No more permission problems on my end on 1803. It also follows my wsl.conf properly as other DrvFs mounts do.

bitcrazed · 2018-08-06T19:07:39Z

Hey @benhillis - reopening because Heath Yates is running on 1803 and posted this on Reddit, and pinged us on Twitter re. same.

Handing-off to @tara-raj to triage with y'all.

therealkenc · 2018-08-06T20:26:25Z

That's #2779

SvenGroot · 2018-08-06T21:33:54Z

Confirmed, Heath Yates's issue is not related to this one, but to #2779 and is "by design". Closing again.

bitcrazed · 2018-08-06T21:41:36Z

Great, thanks for taking a look @therealkenc & @SvenGroot :)

ghazi94 changed the title ~~Permission Denied For Folders in Mounted VHDX in WSL~~ Permission Denied For Folders in Mounted VHDX/VHD in WSL Oct 13, 2016

0xbadfca11 mentioned this issue Nov 18, 2016

ReFS on WSL #1372

Closed

benhillis closed this as completed Jun 22, 2018

bitcrazed reopened this Aug 6, 2018

SvenGroot closed this as completed Aug 6, 2018

github-actions bot mentioned this issue Feb 20, 2024

VHD mount issue with "WSL (2156) ERROR: UtilMount" #11183

Closed

2 tasks

Permission Denied For Folders in Mounted VHDX/VHD in WSL #1199

Permission Denied For Folders in Mounted VHDX/VHD in WSL #1199

Comments

ghazi94 commented Oct 12, 2016 • edited Loading

Windows Explorer

fpqc commented Oct 12, 2016

ghazi94 commented Oct 12, 2016

benhillis commented Oct 12, 2016

benhillis commented Oct 12, 2016

fpqc commented Oct 12, 2016

ghazi94 commented Oct 13, 2016

wimpunk commented Oct 13, 2016

ghazi94 commented Oct 14, 2016

Manouchehri commented Oct 14, 2016 • edited Loading

VHD

Physical Partition

mheden commented Oct 17, 2016

benhillis commented Oct 17, 2016

Manouchehri commented Oct 17, 2016 • edited Loading

benhillis commented Oct 17, 2016

Manouchehri commented Oct 17, 2016 • edited Loading

IL2 commented Oct 23, 2016

ivivanov-bg commented Oct 24, 2016 • edited Loading

fpqc commented Oct 24, 2016

ivivanov-bg commented Oct 24, 2016 • edited Loading

ivivanov-bg commented Oct 24, 2016

ghazi94 commented Oct 24, 2016

andrewfinnell commented Oct 27, 2016

ghazi94 commented Oct 28, 2016

andrewfinnell commented Oct 28, 2016

0xbadfca11 commented Oct 30, 2016

ivivanov-bg commented Nov 21, 2016

ghazi94 commented Nov 21, 2016

jcar87 commented Dec 7, 2016

ivivanov-bg commented Dec 9, 2016

ghazi94 commented Dec 17, 2016

ivivanov-bg commented Jan 13, 2017

TheRealDuckboy commented Jan 27, 2017

sunilmut commented Jan 27, 2017

aseering commented Jan 27, 2017

sunilmut commented Jan 27, 2017

sunilmut commented Jan 31, 2017

fpqc commented Jan 31, 2017

sunilmut commented Jan 31, 2017

fpqc commented Jan 31, 2017 • edited Loading

ghazi94 commented Feb 1, 2017

0xbadfca11 commented Feb 2, 2017

dbsavage commented Mar 9, 2017

0xbadfca11 commented Mar 10, 2017 • edited Loading

dbsavage commented Mar 10, 2017

dimo414 commented May 25, 2017 • edited Loading

benhillis commented Jun 21, 2018

fpqc commented Jun 22, 2018

onomatopellan commented Jun 22, 2018 • edited Loading

bitcrazed commented Aug 6, 2018 • edited Loading

therealkenc commented Aug 6, 2018

SvenGroot commented Aug 6, 2018

bitcrazed commented Aug 6, 2018 • edited Loading

ghazi94 commented Oct 12, 2016 •

edited

Loading

Manouchehri commented Oct 14, 2016 •

edited

Loading

Manouchehri commented Oct 17, 2016 •

edited

Loading

Manouchehri commented Oct 17, 2016 •

edited

Loading

ivivanov-bg commented Oct 24, 2016 •

edited

Loading

ivivanov-bg commented Oct 24, 2016 •

edited

Loading

fpqc commented Jan 31, 2017 •

edited

Loading

0xbadfca11 commented Mar 10, 2017 •

edited

Loading

dimo414 commented May 25, 2017 •

edited

Loading

onomatopellan commented Jun 22, 2018 •

edited

Loading

bitcrazed commented Aug 6, 2018 •

edited

Loading

bitcrazed commented Aug 6, 2018 •

edited

Loading