WSL2 cannot mount FAT32 formatted physical drives

[ccoles146]

Windows Version

Microsoft Windows [Version 10.0.22621.963]

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

try to mount a FAT32 formatted USB stick or SD Card.

In PowerShell> wmic diskdrive list brief
xxx NVMe xxx \\.\PHYSICALDRIVE0 etc. etc.
Lexar JD FireFly USB Device \\.\PHYSICALDRIVE1 Lexar JD FireFly USB Device 1

In PowerShell> wsl --mount \\.\PHYSICALDRIVE1
The system cannot find the drive specified.
Error code: Wsl/Service/AttachDisk/HCS/0x8007000f

Try again in Ubuntu

In Ubuntu:$ sudo mount D: /mnt/d
mount: /mnt/d: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> help program. etc.
In Ubuntu:$ sudo mount -t vfat D: /mnt/d
mount: /mnt/d: special device D: does not exist. dmesg(1) etc.
In Ubuntu:$ sudo mount -t drvfs D: /mnt/d
In Ubuntu:$ cd /mnt/d
In Ubuntu:/mnt/d$ ls
ls: reading directory '.': Operation not supported

Expected Behavior

I expect to be able to either mount the device any number of ways:

• using -t vfat (if that is an option)
• otherwise using -t drvfs
• AND I expect to be able to mount it in Powershell using wsl --mount \.\PHYSICALDRIVE1

Actual Behavior

Either doesn't mount and claims device does not exist.
Or does mount and then reports reading '.' operation not supported.

Diagnostic Logs

WslLogs-2024-10-11_11-53-41.zip

[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 wsl-gh-logs@microsoft.com 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:

• WSL --mount will not mount a microSD card (#8090), similarity score: 0.77

Closed similar issues:

• wsl --mount fails when physical drive is detected (#10208), similarity score: 0.81
• SD Card (on PCIe reader) bare mount fails. (#10198), similarity score: 0.77
• Failed to mount Ext4 partition (#8885), similarity score: 0.77
• Can't mount ext4 partition under windows using WSL2. Fails to mount with error code: -1 (#6319), similarity score: 0.76

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

[github-actions]

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/17341054/WslLogs-2024-10-11_11-53-41.zip
Detected appx version: 2.3.24.0
Detected user visible error: Wsl/Service/AttachDisk/WSL_E_ELEVATION_NEEDED_TO_MOUNT_DISK
Detected user visible error: Wsl/Service/AttachDisk/0x8007000f

[zcobol]

@ccoles146 that's an external USB attached physical drive.! You might have better luck mounting it using usbip instead.

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!