Cmder : "wslbridge error: failed to start backend process"

[AurelienCordonnier]

Hello, when I start a WSL bash terminal on Cmder or with ConEmu64.exe -basic -run {bash}, I have

wslbridge error: failed to start backend process
note: backend error output: -v: -c: line 0: unexpected EOF while looking for matching `''
-v: -c: line 1: syntax error: unexpected end of file


ConEmuC: Root process was alive less than 10 sec, ExitCode=0.
Press Enter or Esc to close console...

But the standard console (Debian in my case) works...

Do you have an idea to solve this problem?

[dcole2929]

I have the same issue, specifically with WSL2. Looks like there was some discussion on this months ago here Maximus5/ConEmu#1930 but doesn't appear to be a clear cut resolution

[AurelienCordonnier]

In agreement with @LesterCovax in Maximus5/ConEmu#1930, edit the task definition by replacing %ConEmuBaseDirShort%\conemu-cyg-64.exe by wsl.exe in Cmder Settings/Startup/Tasks works fine. Probably that don't realy solve the "wslbridge error" encountered directly, but that gives an answer. I don't know if it is the same result as well...

I have to mention that works also with debian.exe and I think it will be the same for other distributions.

[aymond]

Thanks @AurelienCordonnier - I am running WSL2 Ubuntu with ZSH. Updating the command to set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & wsl.exe worked for me.

[mavaddat]

For recent changes in WSL, particularly WSL mode V2, the new gateway wslbridge2 should be used instead. Many thanks for this further development and maintenance go to Biswapriyo Nath.

[ElizaZadura]

Thanks @AurelienCordonnier - I am running WSL2 Ubuntu with ZSH. Updating the command to set "PATH=%ConEmuBaseDirShort%\wsl;%PATH%" & wsl.exe worked for me.

Worked for me too on Win 10 👍