How to Mount Network Drives in Windows Subsystem for Linux
You can mount network drives in Windows Subsystem for Linux (WSL) to access files stored on your network directly from your Linux environment.
This process integrates your Windows network shares with your WSL distribution, allowing you to manage network storage seamlessly within Linux.
For instance, you can mount a Windows 11 network share using the `mount` command in WSL.
Leveraging the SMB protocol and Linux mount commands, you’ll be able to access your shared folders from the terminal.
Access Windows network drives in WSL by creating a Linux mount point and using the `mount` command with the `drvfs` type. For example, to mount a Windows drive letter like F:, run `sudo mkdir /mnt/f` then `sudo mount -t drvfs F: /mnt/f`.
Why mount network drives in WSL?
Mounting a network drive lets you use Linux tools to work on shared files. It connects your Windows network folders to your Linux environment, making it much easier to manage projects or data stored on a server.
What happens when you are done?
Once finished, your network folder will look and act like a normal folder inside your Linux system. You can read, edit, and move files just like any other file on your computer.
DrvFs vs. Native Linux Mounting
WSL uses DrvFs to bridge Windows files to Linux. This is the standard way to access Windows network shares. While you could use cifs-utils to mount shares natively, DrvFs is better for WSL because it handles Windows permissions automatically. Use DrvFs for most tasks to avoid complex configuration.
Mounting a drive letter
You can easily bring a Windows drive letter, like F:, that you’ve already mapped to a network location into your WSL environment to mount network drives in WSL.
If you have already mapped a network location to a drive letter in Windows (like F:), you can easily bring it into WSL.
Note: The following commands require admin privileges.
- Create a folder in Linux to act as the bridge:Bash / Shell
sudo mkdir /mnt/f - Mount the Windows drive letter to that folder:Bash / Shell
sudo mount -t drvfs F: /mnt/f
Mounting a network folder path (UNC)
You can access network shares without mapping a drive letter by using the UNC path directly. This is useful for temporary access.
- Create a mount point:Bash / Shell
sudo mkdir /mnt/documents - Mount the network share:Bash / Shell
sudo mount -t '\\server\documents' /mnt/documents
Persistent mounting via /etc/fstab
To keep your mount after a reboot, add it to the /etc/fstab file. Open the file with sudo nano /etc/fstab and add this line:
\\server\share /mnt/network drvfs defaults 0 0
Run sudo mount -a to apply changes immediately.
Troubleshooting Common Errors
If you run into problems mounting network drives in WSL, common errors like ‘Permission Denied’ usually mean your Windows user needs access to the network share.
If you see a Permission Denied error, ensure your Windows user has access to the share. If you see Mount point busy, the folder is already in use. Use mount to check active connections.
mount in your terminal. This lists all active connections and their paths.
Why does my WSL network drive mount disappear after reboot?
Your WSL network drive mounts disappear after reboot because WSL doesn’t save them automatically; you need to add the mount to your /etc/fstab file to make them permanent.
How do I handle permission issues when accessing Windows network drives in WSL?
Permission issues when accessing Windows network drives in WSL often happen because WSL doesn’t share your Windows login details, so you need to map the drive in Windows first using ‘net use’.
Summary
Mounting network drives in WSL lets you use your Windows network files directly in Linux, using DrvFs to connect drive letters or UNC paths to Linux folders, and making them permanent with /etc/fstab.
Mounting network drives in WSL allows you to bridge your Windows network resources into your Linux workflow. By using DrvFs, you can map drive letters or direct UNC paths to Linux folders. For permanent access, configure your /etc/fstab file. Always verify your connection with the mount command if you run into errors.
Learn more about DrvFs file permissions in the official Microsoft documentation.
Was this guide helpful?
About the Author
Richard
Tech Writer, IT Professional
Richard, a writer for Geek Rewind, is a tech enthusiast who loves breaking down complex IT topics into simple, easy-to-understand ideas. With years of hands-on experience in system administration and enterprise IT operations, he’s developed a knack for offering practical tips and solutions. Richard aims to make technology more accessible and actionable. He's deeply committed to the Geek Rewind community, always ready to answer questions and engage in discussions.
Hi!
You’re missing one thing from this otherwise extraordinarily useful post:
sudo mount -t ‘\\server\documents’ /mnt/documents
should be
sudo mount -t drvfs ‘\\server\documents’ /mnt/documents
(I got the bit about “-t drvfs” from another post that involved doing
“Map network drive” first to assign a drive letter to the network drive.)