WSL2 is extremely slow at the file system frontier and it doesn't have any right to be.

[pierrelgol]

Ok so it's 2025, we all have supercomputers that a few decades ago would have been used to compute state of the art physics problem, but apparently this is 2025 and we can't have things be fast. I don't understand how a trillion dollar company can fumble the bag this hard but here we are. So the issue is simple, if you dare to try to create a symlink in wsl2 to a windows repo (keep in mind this is a 200 bucks OS), and if you just do something like 'ls' it takes 30s. So here's my idea how about you try to use the hundreds of GIGAFLOPS of my computer and figure it out. it shouldn't take more than a few ms if even that. Mounting even exotic filesystem to a vm on linux has never been an issue to performance, so i don't really know what to say. Stop letting the summer intern maintain 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 in Collect WSL logs for networking issues

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

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[pierrelgol]

WslLogs-2025-12-06_10-48-34.zip

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

.wslconfig found
Detected appx version: 2.6.2.0
Found no WSL traces in the logs

[pierrelgol]

shut up stupid bot not my fault your trace util doesn't capture the mediocrity of this implementation

[pierrelgol]

There is no world that I want to live in where ls takes 140s to output something. This computer has an intel 13900hk 32gb of 6000mt/s ram an rtx 4090 gpu.

[pierrelgol]

Also remember this is the top of the line the peak of performance the top 10% of modern computing power I have. Imagine some poor guy running a dual core CPU with 8gb of ram, my man haven't opened an issue yet because he's still probably WAITING FOR LS TO FINISH