Spaces in windows PATH break when appendWindowsPath is true

[cooperoptigrid]

Windows Version

Microsoft Windows [Version 10.0.26200.7171]

WSL Version

2.5.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu 24.04

Other Software

VS Code - 1.106.2
Cursor - 2.1.25

Repro Steps

>>> code .
command code not found
>>> cursor .
command cursor not found

Expected Behavior

>>> code .  # opens VS Code
>>> cursor .  # opens Cursor

Actual Behavior

>>> code .
command code not found
>>> cursor .
command cursor not found

Diagnostic Logs

>>> echo $PATH
# ... bunch of normal linux paths like /usr/bin]
# broken Windows Paths, note ":" where spaces should be
/mnt/c/Program:Files/dotnet/:Files/Git/cmd:Files/Amazon/AWSCLIV2/:/Docker/host/bin:Files/cursor/resources/app/bin:Files/PowerShell/7/:/mnt/c/Users/Cooper/.local/bin:/mnt/c/Users/Cooper/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/Cooper/AppData/Local/Programs/Microsoft:VS:Code/bin:
# bunch of other stufff

A workaround is for me to manually add the correct paths to my .bashrc

# temporary, hopefully. not sure why this suddenly stopped working...
export PATH="$PATH:/mnt/c/Users/Cooper/AppData/Local/Programs/Microsoft VS Code/bin"
export PATH="$PATH:/mnt/c/Program Files/cursor/resources/app/bin"

This made it work!

This was never a problem until I restarted my device recently (and presumbaly some updates were applied).

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

[cooperoptigrid]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[OneBlue]

Thank you for reporting this @cooperoptigrid.

Could you share which PATH you have set in that shell ? I wonder if there's a parsing bug in wsl.exe.

For PowerShell:

echo $env:PATH

For cmd.exe:

path

[cooperoptigrid]

@OneBlue here it is

PS C:\Users\CooperEllidge> echo $env:PATH
C:\Program Files\PowerShell\7;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\Git\cmd;C:\Program Files\Amazon\AWSCLIV2\;C:\Program Files\cursor\resources\app\bin;C:\Program Files\PowerShell\7\;C:\Program Files\Docker\Docker\resources\bin;C:\Users\CooperEllidge\.local\bin;C:\Users\CooperEllidge\AppData\Local\Microsoft\WindowsApps;C:\Users\CooperEllidge\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\CooperEllidge\AppData\Local\Microsoft\WinGet\Packages\Gruntwork.Terragrunt_Microsoft.Winget.Source_8wekyb3d8bbwe;C:\Users\CooperEllidge\AppData\Local\Microsoft\WinGet\Packages\Hashicorp.Terraform_Microsoft.Winget.Source_8wekyb3d8bbwe;C:\Users\CooperEllidge\AppData\Local\Programs\Zed\bin