Unable to access ReFS drive

[PhiliaTheCat]

Windows Version

Windows 11 Home 10.0.26100 Build 26100

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Just create a dev drive in your Windows.
Assume you labeled it as E:.

Expected Behavior

Run cd /mnt/e in WSL shell, you should be able to open the drive and read/write things there.

Actual Behavior

WSL shell returns that permission denied.

Diagnostic Logs

I know this is reported in a old issue, but it's closed due to too old version.
This one is discovered on a more recent version of WSL.

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• Unable to access WSL mounted disk (\wsl.localhost\Ubuntu\mnt\c) from File Explorer due to Permission Denied (#11222), similarity score: 0.74

Closed similar issues:

• WSL distros cannot access files within a Dev Drive (#10854), similarity score: 0.71
• ReFS on WSL (#1372), similarity score: 0.70
• WSL can not access mounted drives (#11079), similarity score: 0.70
• can not access windows driver using /mnt (#11793), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[PhiliaTheCat]

Note that this issue came after I updated my system 2 or 3 days ago, and I hadn't updated it since Sept.

[PhiliaTheCat]

WslLogs-2024-10-14_14-19-55.zip
WSL logs required

[github-actions]

Diagnostic information

Detected appx version: 2.2.4.0
Detected user visible error: Wsl/Service/CreateInstance/GetDefaultDistro/WSL_E_DEFAULT_DISTRO_NOT_FOUND

[PhiliaTheCat]

I think this issue is just the same with #10792, but that one is closed.

[HerrLiljegren]

@PhiliaTheCat I have the same issue. I solved it for now by uninstalling the update KB5044384

After I've rebooted the computer I could once again access my dev drive in WSL and Docker is now working 🎉

[sibbl]

@HerrLiljegren may I ask how were you able to uninstall the update?

I first tried via Windows Update > Update history > Uninstall update > find the update, click uninstall. It also indicates success. However, when reopening the page, it's immediately shown as installed again. The dev drive is still unaccessable immediately and after a reboot.

Also, pausing Windows Update makes no difference.

Using wusa /uninstall /kb:5044384 fails with 0x800f0825 error code.

[HerrLiljegren]

@HerrLiljegren may I ask how were you able to uninstall the update?

I first tried via Windows Update > Update history > Uninstall update > find the update, click uninstall. It also indicates success. However, when reopening the page, it's immediately shown as installed again. The dev drive is still unaccessable immediately and after a reboot.

Also, pausing Windows Update makes no difference.

Using wusa /uninstall /kb:5044384 fails with 0x800f0825 error code.

I resolved the issue by following these steps:

Pressed the Windows key and typed "Uninstall Updates".
Uninstalled the recent update KB5044384 from the list.
Rebooted the system.
After rebooting, I found that the dev drive was accessible in WSL. Previously, when I tried ls /mnt/d in WSL, I received an access denied error. But after uninstalling the update and rebooting, I could see the content of the directory in WSL.

[sibbl]

@HerrLiljegren thanks for the insights! Seems like something more is broken over here, so I probably will adapt my dev workflow until MS fixes the issue in another update.

[PhiliaTheCat]

@HerrLiljegren may I ask how were you able to uninstall the update?
I first tried via Windows Update > Update history > Uninstall update > find the update, click uninstall. It also indicates success. However, when reopening the page, it's immediately shown as installed again. The dev drive is still unaccessable immediately and after a reboot.
Also, pausing Windows Update makes no difference.
Using wusa /uninstall /kb:5044384 fails with 0x800f0825 error code.

I resolved the issue by following these steps:

Pressed the Windows key and typed "Uninstall Updates". Uninstalled the recent update KB5044384 from the list. Rebooted the system. After rebooting, I found that the dev drive was accessible in WSL. Previously, when I tried ls /mnt/d in WSL, I received an access denied error. But after uninstalling the update and rebooting, I could see the content of the directory in WSL.

Thanks for instructions. Hope they will repair this problem as soon as possible.

[PhiliaTheCat]

Because microsoft has reopened the previous issue so this one is closed up.