`wsl --debug-shell` hangs when exits

[chansey97]

Windows Version

Microsoft Windows [Version 10.0.26100.4652]

WSL Version

2.5.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2

Distro Version

Mariner based root file system

Other Software

No response

Repro Steps

This is not an urgent issue. I was just reading this document from https://learn.microsoft.com/en-us/windows/wsl/wsl-plugins#plugins-linux-user-space and wanted to inspect the content of the "very minimal Mariner based root file system".

But it still appears to be a BUG, as it cannot exit properly.

1. Open an Command Prompt in Windows Terminal
2. Input wsl
   NOTE: This step is necessary, otherwise

   The system cannot find the file specified.
   Error code: Wsl/DebugShell/ERROR_FILE_NOT_FOUND
   

3. Open an elevated Command Prompt in Windows Terminal
4. Input wsl --debug-shell

   Welcome to CBL-Mariner 2.0.20240829 (x86_64) - Kernel 6.6.87.2-microsoft-standard-WSL2 (hvc2)
   DESKTOP-7942QN8 login: root (automatic login)
   

5. Input exit

   logout
   <<hangs....>>
   

Expected Behavior

Return to the Command Prompt normally.

Actual Behavior

Hangs forever...

Other things you can do:

• Open the 2nd elevated Command Prompt in Windows Terminal

  C:\Users\Chansey>wsl --debug-shell
  All pipe instances are busy.
  Error code: Wsl/DebugShell/ERROR_PIPE_BUSY
  

• The only way to reset everything, is sc.exe stop wslservice.

Diagnostic Logs

WslLogs-2025-08-03_22-21-44.zip

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

[github-actions]

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/21566329/WslLogs-2025-08-03_22-21-44.zip
.wslconfig found
Detected appx version: 2.5.9.0

[benhillis]

Thanks for reporting, I have an idea on how to fix this.

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!