Repository navigation
Description
WSL service stack overflow during Ubuntu .wsl installation with explicit VHD size
Environment
- WSL and faulting wslservice.exe: 3.0.5.0.
- Windows version from saved WSL output: 10.0.26300.9974.
- Kernel: 6.18.58.1-1; WSLg: 1.0.79; MSRDC: 1.2.7391.
- Official Ubuntu image: https://releases.ubuntu.com/24.04/ubuntu-24.04.5-wsl-amd64.wsl
- Image SHA256: bb415d824822c4b878125729af451a5d18fb13d1cf5cbed9a7393ad64ac6039e, checked against Canonical-signed checksum metadata. Image bytes were unchanged; offline inspection confirmed gzip tar.
Failed operation
The following records an already completed failed attempt; local paths and distribution name are replaced with generic examples. No new reproduction is currently planned.
C:\Windows\System32\wsl.exe --install --from-file C:\Images\ubuntu-24.04.5-wsl-amd64.wsl --name BuildTest --location C:\BuildDistributions\BuildTest --no-launch --version 2 --vhd-size 274877906944B
Expected: registration of a separate WSL2 distribution with a dynamic logical maximum of 256 GiB, or an actionable error without service termination.
Actual: the client returned signed -1 (unsigned 4294967295) and Wsl/Service/RPC_S_CALL_FAILED. Its exit and closed output streams were observed. The attempt ran 2026-11-15 14:13:09.005–14:13:10.943 UTC.
Existing Application Error, WER and Service Control Manager records correlate one service crash and unexpected service termination during that attempt. A subsequently copied, hash-verified local Report.wer matches the events' integrator report identity and all eight application/module/exception signature fields:
- Application: wslservice.exe 3.0.5.0, timestamp 6ae3c6fe.
- Fault module: ntdll.dll 10.0.26100.9974, timestamp a2b84216.
- Exception: c00000fd (stack overflow).
- Offset: 0000000000040e54.
- WER bucket hash: ec3f7da9438734239135b09e953c548e; legacy bucket: 1240091467565520014; report status: 268435456.
The report contains 97 loaded-module entries but no call stack or dump payload. Module and Windows version fields above are reported separately as observed. Neither the fault-module name nor its offset establishes the internal WSL cause.
Read-only checks after the failure found no new distribution in --list --verbose, no matching current-user Lxss registration, and no requested target directories. This does not establish absence of all side effects. An earlier separately authorized attempt on WSL 2.7.12.0 failed with the same exception code and RPC error but a different offset; an identical internal cause is not established. No install retry, import workaround, service reset or cleanup has been performed since the 3.0.5 failure.
Request
Can the existing signature/bucket identify a known failure? If not, what is the smallest supported diagnostic artifact needed to resolve the faulting thread's stack with matching symbols? We would prefer to use existing crash artifacts before reproducing a crash in a shared WSL service.
No raw logs, reports, dumps, machine names, user names, private paths, registry GUIDs or report identifiers are attached. Additional collection or uploads would be considered separately.
Activity
github-actions commentedon Nov 15, 2026
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:
The script will output the path of the log file once done.
If this is a networking issue, please use
.\collect-wsl-logs.ps1 -LogProfile networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce 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'.
chemwolf6922 commentedon Nov 16, 2026
Hi Arash Molavi (@ironyh) .
I'm not able to reproduce this locally. If you can repro this issue. Could you please help collect the dump and wsl log with the following steps?
C:\WSL-CrashDumps-42285.