Cmder: wslbridge error: failed to start backend process

[gabimladin]

When I open a tab for WSL, WSL-> BASH, an error occurs.

[Ergamon]

It is a ConEmu thing. The whole WSL part is for WSL version 1, I guess you are running WSL version 2?

1. You need a new version of cygwin1.dll
   Grab one here: https://cygwin.com/snapshots/
   Go to vendor\conemu-maximus5\ConEmu\wsl and replace the dll.

2. You need wslbridge 2:
   Grab it here: https://github.com/Biswa96/wslbridge2/releases (the cygwin version)
   Copy the content to the same directory: vendor\conemu-maximus5\ConEmu\wsl

3. Now edit your WSL bash task:
   Replace the part "conemu-cyg-64.exe --wsl" with "conemu-cyg-64.exe %ConEmuBaseDirShort%\wsl\wslbridge2.exe"

Done.

[gabimladin]

I have Windows 10 Build 19041 and Cmder v1.3.16. It's not a path problem because if I run Cmder\vendor\conemu-maximus5\ConEmu\wsl\wslbridge.exe, the same error occurs. The problem is to wslbridge.exe.

[Tiaonmmn]

When you use WSL2,do not use original wslbridge.exe,it's designed for WSL1.You can create a new task,and set the task command as: set PATH="%ConEmuBaseDirShort%\wsl";%PATH% & wsl -d kali-linux,which kali-linux is the distro name you have installed.You can get the name by seeing wsl -l output.

[gabimladin]

Yes, I can run wsl.exe but will no longer use colors 256colors, looking like windows cmd.

[stale[bot]]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contribution(s).

[stale[bot]]

This issue has been automatically closed due to it not having any activity since it was marked as stale. Thank you for your contribution(s).

[elisim]

Hey,
any progress?