This 6 year old bug was closed but not fixed

[AndersHogqvist]

Please consider re-opening #5934. It's a 6 year old bug that still isn't fixed and people continuously post comments on it.

[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-wsl-logs.ps1 -LogProfile networking instead, 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'.

[AndersHogqvist]

/question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[OneBlue]

Thank you for reporting this @AndersHogqvist. This is unfortunately not a bug, but a consequence of your shell trying to access every single file in your $PATH, which can take a long time depending on how many files are in $PATH.

[AndersHogqvist]

Ok, I have quite a few entries in $PATH for sure but not an excessive amount. I read somewhere that someone had made a "hack" that removed all Windows paths which seemed to have solved the issue, so I assume they are the culprit here. However, I guess we can close this one then.