/usr/bin/kex: line 25: route.exe: command not found

[303acido]

Windows Version

Windows Pro 24h2 26100.2605

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Kali-Linux

Other Software

only the kali liux from WSL2

Repro Steps

Start the Terminal of Kali-Linux
Add command "Sudo kex --win"
error : /usr/bin/kex: line 25: route.exe: command not found
But still can use the GUI ,but now internet connection.

Expected Behavior

not the error : /usr/bin/kex: line 25: route.exe: command not found

And Internet connection on the GUI.

Error GUI :

apt update && apt upgrade -y
Ign:1 http://http.kali.org/kali kali-last-snapshot InRelease
Ign:1 http://http.kali.org/kali kali-last-snapshot InRelease
Ign:1 http://http.kali.org/kali kali-last-snapshot InRelease
Err:1 http://http.kali.org/kali kali-last-snapshot InRelease
Could not connect to http.kali.org:80 (18.211.24.19), connection timed out
All packages are up to date.
Warning: Failed to fetch http://http.kali.org/kali/dists/kali-last-snapshot/InRelease Could not connect to http.kali.org:80 (18.211.24.19), connection timed out
Warning: Some index files failed to download. They have been ignored, or old ones used instead.

Actual Behavior

An error code after using the command : sudo kex --win in the Kali-linux terminal.

and no internet connection int hte GUI

Diagnostic Logs

No response

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

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• Win - kex stopped working (#9361), similarity score: 0.75

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[303acido]

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

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• Win - kex stopped working (#9361), similarity score: 0.75

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Thx for the info,will do it asap😅

Cheers

[303acido]

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

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• Win - kex stopped working (#9361), similarity score: 0.75

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Thx for the info,will do it asap😅

Cheers

Hello,

I don't had the time for the logging ,will do it in the futher ,but thanks for the info!
I just did a clean install "wsl --unregister Kali-Linux" and delete the app.

Than downloaded it back from the Microsoft Store.
And the problem was fixed.

Best regards,

303acido

[zcobol]

@303acido this is the content of line 25 in /usr/bin/kex:

25 HOSTIP=$(route.exe print | grep 0.0.0.0 | head -1 | awk '{print $4}')

It's using the Windows route command to find the host IP address. Under WSL the path is /mnt/c/Windows/system32/route.exe. Do you maybe have appendWindowsPath=false in your /etc/wsl.conf?

What is the output of command -v route.exe? On an working system it looks like this:

┌──(zcobol㉿eleven)-[~]
└─$ command -v route.exe
/mnt/c/Windows/system32/route.exe