Feature Request: Simplify File Access and Navigation Between Windows and Linux in WSL

[MichaelKamelit]

Summary

I would like to suggest a feature that improves and simplifies file access between the Windows host and the Linux filesystem in WSL (especially WSL2).

Current Behavior

Currently, users can access Windows files from WSL via /mnt/c, and access WSL files from Windows through paths like \\wsl$\Ubuntu. However, navigating these paths manually can be confusing, especially for new users or developers using WSL in daily workflows.

Suggested Improvements

1. Introduce a shortcut command or mount point like /windows inside WSL that points directly to the Windows home directory (C:\Users\YourName).
2. Add a GUI option in Windows File Explorer (e.g., a quick shortcut under "This PC") to jump directly into the WSL Linux file system.
3. Enable easy drag-and-drop support between Windows and WSL folders using the native file explorer.

Benefits

• Saves time and reduces confusion for developers.
• Makes onboarding new WSL users easier.
• Improves daily workflow and cross-system file handling.

Additional Context

Many developers using IDEs like VS Code, IntelliJ, or Docker with WSL would benefit from seamless file access. Reducing the mental overhead of navigating paths manually would increase productivity and adoption.

[github-actions[bot]]

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'.

[MichaelKamelit]

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 /feature

[github-actions[bot]]

Diagnostic information

Found '/feature', adding tag 'feature'

[MichaelKamelit]

[MichaelKamelit]

working on code now

[OneBlue]

Thank you for the suggestion @MichaelKamelit.

1. can be easily done by adding an entry in /etc/fstab, or a symlink, but creating a /windows shouldn't be the default WSL behavior since that's a non standard mount path

As you saw 2. is already in place via the Linux explorer short

And for 3., drag and drop is always possible via the explorer between Windows & Linux. If you mean drag and drop towards a GUI app, that would be a wslg feature.

[MichaelKamelit]

Thank you for the detailed response!

You're right — creating a symlink is straightforward, and I agree that making /windows a default path might conflict with standard Linux conventions.

For the drag & drop part, yes — I was thinking of an enhanced workflow, possibly with a mini tool or tray app that simplifies this interaction further for non-technical users.

Happy to keep improving the idea or contribute a small utility for the community if that’s helpful. Appreciate your time!