binfmt config cleared on all distro when distro with systemd is terminated

[MiKom]

Windows Version

Microsoft Windows [Version 10.0.26200.7462]

WSL Version

WSL version: 2.6.2.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-microsoft-standard-WSL2

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

1. Install two distros with systemd. For example Ubuntu 24.04 and Ubuntu 22.04
2. Run both of them in separate terminals
3. terminate one of those in a third terminal (wsl.exe -t "Ubuntu 22.04")
4. Observe ls /proc/sys/fs/binfmt_misc in the one left open

Expected Behavior

In the distro that is left open, the registered binfmt handlers aren't cleared

Actual Behavior

All binfmt handlers in the non-terminated distro are gone. Including WSLInterop. As if the binfmt handlers were shared somehow.

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

[MiKom]

/emailed-logs

[github-actions]

Diagnostic information

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

[MiKom]

Pinging to make sure the bot doesn't close it. Issue still persists

[MiKom]

Pinging again to fend off the bot