WSL2 (Preview) cannot run .exe files: exec format error: wsl.exe #8952

blami · 2022-10-05T06:07:13Z

Version

Microsoft Windows [Version 10.0.22621.521]

WSL Version

WSL 2
WSL 1

Kernel Version

5.15.62.1-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04

Other Software

systemd 249.11-0ubuntu3.3

WSL version: 0.68.2.0
Kernel version: 5.15.62.1
WSLg version: 1.0.44
MSRDC version: 1.2.3401
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.521

Repro Steps

[optional] disable wslg
[optional] enable systemd support
make sure interop is not disabled
attempt to run wsl.exe --version from any shell inside WSL2
ls /proc/sys/fs/binfmt_misc/ for presence of WSLInterop

Expected Behavior

wsl.exe will exe will execute and output version on terminal
/proc/sys/fs/binfmt_misc/ will contain custom binary format for WSL interop

Actual Behavior

After upgrade to preview version of WSL2 (ver. 0.68.2.0 from Github on non-Insider build) it was possible to run Windows binaries from within WSL2 by simply having them in PATH and typing binary.exe with systemd enabled and disabled.

After Windows build 22H2 upgrade this is not longer possible. Shell sees binaries in PATH but its not possible to run them, error message being exec format error: wsl.exe. After further inspection I found WSL interop is not registered with binfmt_misc:

~ $ ls /proc/sys/fs/binfmt_misc/
llvm-15-runtime.binfmt  qemu-arm     qemu-mips64el  qemu-riscv64  register
qemu-aarch64            qemu-mips64  qemu-ppc64le   qemu-s390x    status

After upgrade I noticed Hypervisor Platform was disabled although I am sure I had it enabled before. I reenabled it but it didn't solve the issue.

Diagnostic Logs

~ $ cat /etc/wsl.conf
[boot]
systemd = true

[automount]
enabled = true
mountFsTab = true
root = /mnt/
options = "metadata,umask=2,fmask=1,case=off"

[network]
generateHosts = true
generateResolvConf = true

[interop]
enabled = true

~ $ cat /mnt/c/Users/blami/.wslconfig
[wsl2]
guiApplications = false

The text was updated successfully, but these errors were encountered:

blami · 2022-10-05T08:18:33Z

I collected logs while trying to run wsl.exe.

There's repeating exception trace: D:\a\1\s\src\windows\common\svccomm.cpp(95)\wsl.exe!00007FF6EF4D3D14: (caller: 00007FF6EF4D07F6) Exception(1) tid(1840) 80070006 The handle is invalid. "

WslLogs-2022-10-05_17-08-44.zip

blami · 2022-10-05T12:24:26Z

Disabling systemd support in /etc/wsl.conf resolves the issue.

~ $ cat /etc/wsl.conf
[boot]
#systemd = true

[automount]
enabled = true
mountFsTab = true
root = /mnt/
options = "metadata,umask=2,fmask=1,case=off"

[network]
generateHosts = true
generateResolvConf = true

[interop]
enabled = true

After wsl.exe --shutdown and relaunch:

~ $ powershell.exe
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS Microsoft.PowerShell.Core\FileSystem::\\wsl.localhost\Ubuntu\home\blami>

~ $ ls /proc/sys/fs/binfmt_misc
register  status  WSLInterop

Is this some sort of binfmt_misc setup race condition?

cerebrate · 2022-10-08T00:28:47Z

That's exactly what it is. Specifically, it's #8843 , and I posted a workaround over in that issue.

blami · 2022-10-08T08:17:52Z

@cerebrate Thanks! Not sure why I did not find that one. Will mark mine as duplicate of it. And thanks for workaround. Did some reading and TIL how binfmt works!

Dragon1573 · 2023-04-21T13:48:58Z

Environments

Microsoft Windows 11 Professional 22H2 (10.0.22621.1555)
Windows Subsystem Linux (Version 2)
- WSL Version 1.2.5.0
- Kernel Version 5.15.90.1
- WSLg Version 1.0.51
Ubuntu 23.04 Lunar Lobster

Details

I upgrade to Ubuntu 23.04 today by executing do-release-upgrade. After upgrade process, I find wslfetch goes wrong on my device.

systemd enabled

21:39:41 ~/Documents 0ms $ wslfetch --colorbar --options "windows-build,windows-rel-branch,wsl-release,wsl-kernel,windows-uptime"
grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory
/usr/bin/wslfetch: line 233: /mnt/c/Windows/System32/reg.exe: cannot execute binary file: Exec format error
grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory
/usr/bin/wslsys: line 233: /mnt/c/Windows/System32/reg.exe: cannot execute binary file: Exec format error
/usr/bin/wslsys: line 233: /mnt/c/Windows/System32/reg.exe: cannot execute binary file: Exec format error
/usr/bin/wslsys: line 233: /mnt/c/Windows/System32/reg.exe: cannot execute binary file: Exec format error
/usr/bin/wslsys: line 441: /mnt/c/Windows/System32/reg.exe: cannot execute binary file: Exec format error
/usr/bin/wslsys: line 233: /mnt/c/Windows/System32/reg.exe: cannot execute binary file: Exec format error
/usr/bin/wslsys: line 267: [: : integer expression expected
/usr/bin/wslsys: line 260: /mnt/c/Windows/System32/chcp.com: cannot execute binary file: Exec format error
/usr/bin/wslsys: line 268: /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe: cannot execute binary file: Exec format error
/usr/bin/wslsys: line 270: [: : integer expression expected
/usr/bin/wslsys: line 260: /mnt/c/Windows/System32/chcp.com: cannot execute binary file: Exec format error
               .-/+oossssoo+/-.               Windows Subsystem for Linux (WSL1)
           `:+ssssssssssssssssss+:`           dragon1573@ubuntu.localhost
         -+ssssssssssssssssssyyssss+-         Build:
       .ossssssssssssssssssdMMMNysssso.       Branch:
      /ssssssssssshdmmNNmmyNMMMMhssssss/      Release: Ubuntu 23.04
     +ssssssssshmydMMMMMMMNddddyssssssss+     Kernel: Linux 5.15.90.1-microsoft-standard-WSL2
    /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Uptime (Windows): 0d 0h 0m
   .ssssssssdMMMNhsssssssssshNMMMdssssssss.
   +sssshhhyNMMNyssssssssssssyNMMMysssssss+
   ossyNMMMNyMMhsssssssssssssshmmmhssssssso
   ossyNMMMNyMMhsssssssssssssshmmmhssssssso
   +sssshhhyNMMNyssssssssssssyNMMMysssssss+
   .ssssssssdMMMNhsssssssssshNMMMdssssssss.
    /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
     +sssssssssdmydMMMMMMMMddddyssssssss+
      /ssssssssssshdmNNNNmyNMMMMhssssss/
       .ossssssssssssssssssdMMMNysssso.
         -+sssssssssssssssssyyyssss+-
           `:+ssssssssssssssssss+:`
               .-/+oossssoo+/-.
21:39:45 ~/Documents 245ms $ ls /proc/sys/fs/binfmt_misc
jar  python3.11  register  status

21:40:41 ~/Documents 3ms $ code .
/usr/local/bin/code: 61: /mnt/d/Applications/WinGet/Microsoft/VSCode/Code.exe: Exec format error

When switching systemd = false in /etc/wsl.conf, this issue does solved with some other informations.

systemd disabled

21:42:41 ~/Documents 0ms $ ls /proc/sys/fs/binfmt_misc
register  status  WSLInterop
21:42:44 ~/Documents 9ms $ wslfetch --colorbar --options "windows-build,windows-rel-branch,wsl-release,wsl-kernel,windows-uptime"
找不到“GetEncoding”的重载，参数计数为:“0”。
所在位置 行:1 字符: 59
+ ... ing]::UTF8; [Console]::InputEncoding = [System.Text.Encoding]::GetEnc ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodException
    + FullyQualifiedErrorId : MethodCountCouldNotFindBest

               .-/+oossssoo+/-.               Windows Subsystem for Linux (WSL2)
           `:+ssssssssssssssssss+:`           dragon1573@ubuntu.localhost
         -+ssssssssssssssssssyyssss+-         Build: 22621
       .ossssssssssssssssssdMMMNysssso.       Branch: ni_release
      /ssssssssssshdmmNNmmyNMMMMhssssss/      Release: Ubuntu 23.04
     +ssssssssshmydMMMMMMMNddddyssssssss+     Kernel: Linux 5.15.90.1-microsoft-standard-WSL2
    /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Uptime (Windows): 0d 5h 12m
   .ssssssssdMMMNhsssssssssshNMMMdssssssss.
   +sssshhhyNMMNyssssssssssssyNMMMysssssss+
   ossyNMMMNyMMhsssssssssssssshmmmhssssssso
   ossyNMMMNyMMhsssssssssssssshmmmhssssssso
   +sssshhhyNMMNyssssssssssssyNMMMysssssss+
   .ssssssssdMMMNhsssssssssshNMMMdssssssss.
    /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/
     +sssssssssdmydMMMMMMMMddddyssssssss+
      /ssssssssssshdmNNNNmyNMMMMhssssss/
       .ossssssssssssssssssdMMMNysssso.
         -+sssssssssssssssssyyyssss+-
           `:+ssssssssssssssssss+:`
               .-/+oossssoo+/-.

My /etc/wsl.conf looks like follows:

[boot]
systemd = false

[network]
hostname = "ubuntu.localhost"

[interop]
enabled = true
appendWindowsPath = false

[user]
default = dragon1573

[automount]
enabled = true
mountFsTab = true
root = /mnt/
options = "metadata,umask=022,fmask=011"

[filesystem]
umask = 022
fmask = 011

Mystic8b · 2023-04-22T16:10:46Z

Same problem after upgrade to Ubuntu 23.04.

❯ code
/mnt/c/Users/mystic/AppData/Local/Programs/Microsoft VS Code/bin/code: 61: /mnt/c/Users/mystic/AppData/Local/Programs/Microsoft VS Code/Code.exe: Exec format error
❯ explorer.exe .
zsh: exec format error: explorer.exe

Shutting down systemd didn't solve the problem

Win11 22h2 22621.1413
WSL2

upd
Same problem was after updating to 22.10. Last time and now the problem was solved by complete reinstall distro.. If I didnt have my own env-build project, I'd be just mad. Solve this issue...

ViniciusBastosTR · 2023-04-28T21:06:21Z

Same issue here.

/etc/release

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Only works when disabling systemd

[user]
default=vinicius

[boot]
systemd=false

the-moog · 2023-05-30T10:47:24Z

The issue is that enabling systemd somehow alters /proc/sys/fs/binfmt_misc/
The file (or filelike??) entry WSLInterop.conf goes missing.

I've re-written the answer here rather than just linking as the original reference thread is getting rather long and has dead links.
The oneliner elimiates that problem.

The solution (from here) is to replace that file. Windows executable files start with the two letters MZ
The following tells Linux what to do when trying to run files that start with those letters.

sudo sh -c 'echo :WSLInterop:M::MZ::/init:PF > /usr/lib/binfmt.d/WSLInterop.conf'
sudo systemctl restart systemd-binfmt

I;m using the 23.04 image from links in this post
I guess this is a bug in packaging, or during installation, but I've no idea who to tell.

tardis89 · 2023-06-01T14:45:57Z

@the-moog's solution worked! The only extra step I had to add was unmasking the systemd-binfmt service in order to get it working. So to add to his steps. I unmask the service, restart it, then re-mask it to return it back to its previous protected state besides the new modification.

sudo sh -c 'echo :WSLInterop:M::MZ::/init:PF > /usr/lib/binfmt.d/WSLInterop.conf'
sudo systemctl unmask systemd-binfmt.service
sudo systemctl restart systemd-binfmt
sudo systemctl mask systemd-binfmt.service

khushal123 · 2023-08-03T18:03:55Z

just in case if anyone is still facing the issue, try disabling systemd in /etc/wsl.conf in the distro.

renanlido · 2023-08-04T23:57:28Z

Thanks man! This worked for me!

hros · 2023-08-09T01:54:59Z

Thanks @tardis89
The command solves the issue, and now code starts from wsl.
Can you explain what was the problem, and how do these command solve the issue?

abrahamprz · 2023-08-09T03:55:38Z

Thanks for the solution!

sanjayojha · 2023-08-19T16:39:04Z

Thank you so much. It solved my problem.
Not only this I had problem in running ddev launch command it also fixed it.

maicon-cesar · 2023-08-23T13:23:08Z

For me this helps but it doesn't solve it, because the problem reappears later and I need to run these commands again!

bpkroth · 2023-08-24T19:02:12Z

[like] Brian Kroth (GSL) reacted to your message:

…

________________________________

sanjaybip · 2023-08-25T04:53:07Z

Not sure why, but there is no such problem on my side. The mentioned solution fixed it for once and all.

aravindsomaraj · 2023-11-06T18:41:01Z

Works perfectly! Thank you...

Eliezer134 · 2023-11-22T02:02:43Z

Muchísimas gracias, esos 2 comandos me solucionaron el problema.

stephanlamoureux · 2024-01-20T16:49:25Z

I am getting this error because of minikube. The commands above would fix the problem until I ran minikube again. Are there any other options?

akagami-harsh · 2024-02-16T20:24:26Z

me too getting the same problem

stephanlamoureux · 2024-02-16T20:44:21Z

My only fix was to stop using Docker Desktop and to manually install docker onto WSL. After that, minikube stopped breaking my command line.

FilipeVMartins · 2024-02-27T16:26:47Z

thanks that worked for me, just had to also restart wsl

surgiie · 2024-03-26T03:22:05Z

Solutions here didnt work for me. For vscode 😭

/mnt/d/Microsoft VS Code/bin/code: 61: /mnt/d/Microsoft VS Code/Code.exe: Exec format error

The only thing that temporarily fixes the issue for me:

open cmd
run wsl
rm -rf ~/.vscode-server
exit
back in cmd terminal, run: wsl --shutdown
relaunch wsl

VS code will work for a short period before randomly the error comes back and I have to repeat my steps.

Anybody else having this issue or know of a permanent fix?

keivanipchihagh · 2024-04-13T07:02:31Z

In my case, I found out my Docker Desktop wasn't running (:

trallnag · 2024-08-08T20:03:32Z

For me restarting the distribution was sufficient. @surgiie have you tried it without uninstall vscode server? It should not be related to the problem, as it is Windows interop in general

blami closed this as completed Oct 8, 2022

arrmo mentioned this issue Apr 6, 2023

AMF Issues, Win64 vs. Native rdp/ffmpeg-windows-build-helpers#671

Closed

mcdonnnj mentioned this issue Jun 15, 2023

Cannot create Docker images using Molecule due to _api.credentials.errors ansible/molecule#3934

Closed

the-moog mentioned this issue Jun 16, 2023

systemd-binfmt.service breaks interop ubuntu/WSL#334

Closed

1 task

RobMahn mentioned this issue Jul 20, 2023

"Exec format error" after wsl --import #10314

Closed

2 tasks

kropptrevor mentioned this issue Aug 1, 2023

cannot connect to host: fork/exec /app/wsl-gvproxy.exe: no such file or directory sakai135/wsl-vpnkit#217

Open

r1m mentioned this issue Aug 4, 2023

wsl.exe: 1: MZ: Permission denied sakai135/wsl-vpnkit#228

Closed

This was referenced Aug 7, 2023

WSL2 cannot start VS Code #10363

Closed

VS Code Exec format error in Terminal but can open remote window from within VS Code integrated terminal microsoft/vscode-remote-release#8790

Closed

pierzchalski mentioned this issue Aug 11, 2023

WSL2 - Code.exe: Exec format error microsoft/vscode#189694

Closed

U3erKa mentioned this issue Aug 20, 2023

Unable to start .exe files after Debian12 update #10404

Closed

2 tasks

rbutleriii mentioned this issue Sep 11, 2023

Systemd setup prevents wsl.exe from running sakai135/wsl-vpnkit#239

Open

liketechnik mentioned this issue Sep 13, 2023

[windows/wsl] binfmt does not work in default machine containers/podman#19961

Open

BacLuc mentioned this issue Oct 9, 2023

+ add wsl2 support scs/jumpstart-vm#9

Closed

phbelitz mentioned this issue Nov 30, 2023

Starting Minikube messes up binfmt config for Docker, making it unable to run cross-architecture images kubernetes/minikube#17700

Closed

pfeileon mentioned this issue Apr 18, 2024

[WSL2][systemd][interop] Unable to Execute Windows Binary when systemd enabled #8843

Open

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

WSL2 (Preview) cannot run .exe files: exec format error: wsl.exe #8952

WSL2 (Preview) cannot run .exe files: exec format error: wsl.exe #8952

blami commented Oct 5, 2022

blami commented Oct 5, 2022

blami commented Oct 5, 2022 •

edited

Loading

cerebrate commented Oct 8, 2022

blami commented Oct 8, 2022

Dragon1573 commented Apr 21, 2023

Mystic8b commented Apr 22, 2023 •

edited

Loading

ViniciusBastosTR commented Apr 28, 2023

the-moog commented May 30, 2023

tardis89 commented Jun 1, 2023

khushal123 commented Aug 3, 2023

renanlido commented Aug 4, 2023

hros commented Aug 9, 2023

abrahamprz commented Aug 9, 2023

sanjayojha commented Aug 19, 2023

maicon-cesar commented Aug 23, 2023

bpkroth commented Aug 24, 2023 via email •

edited by microsoft-github-policy-service bot

Loading

sanjaybip commented Aug 25, 2023

aravindsomaraj commented Nov 6, 2023

Eliezer134 commented Nov 22, 2023

stephanlamoureux commented Jan 20, 2024

akagami-harsh commented Feb 16, 2024

stephanlamoureux commented Feb 16, 2024

FilipeVMartins commented Feb 27, 2024

surgiie commented Mar 26, 2024

keivanipchihagh commented Apr 13, 2024

trallnag commented Aug 8, 2024

WSL2 (Preview) cannot run .exe files: exec format error: wsl.exe #8952

WSL2 (Preview) cannot run .exe files: exec format error: wsl.exe #8952

Comments

blami commented Oct 5, 2022

Version

WSL Version

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

blami commented Oct 5, 2022

blami commented Oct 5, 2022 • edited Loading

cerebrate commented Oct 8, 2022

blami commented Oct 8, 2022

Dragon1573 commented Apr 21, 2023

Environments

Details

Mystic8b commented Apr 22, 2023 • edited Loading

ViniciusBastosTR commented Apr 28, 2023

the-moog commented May 30, 2023

tardis89 commented Jun 1, 2023

khushal123 commented Aug 3, 2023

renanlido commented Aug 4, 2023

hros commented Aug 9, 2023

abrahamprz commented Aug 9, 2023

sanjayojha commented Aug 19, 2023

maicon-cesar commented Aug 23, 2023

bpkroth commented Aug 24, 2023 via email • edited by microsoft-github-policy-service bot Loading

sanjaybip commented Aug 25, 2023

aravindsomaraj commented Nov 6, 2023

Eliezer134 commented Nov 22, 2023

stephanlamoureux commented Jan 20, 2024

akagami-harsh commented Feb 16, 2024

stephanlamoureux commented Feb 16, 2024

FilipeVMartins commented Feb 27, 2024

surgiie commented Mar 26, 2024

keivanipchihagh commented Apr 13, 2024

trallnag commented Aug 8, 2024

blami commented Oct 5, 2022 •

edited

Loading

Mystic8b commented Apr 22, 2023 •

edited

Loading

bpkroth commented Aug 24, 2023 via email •

edited by microsoft-github-policy-service bot

Loading