Skip to content

WSL fails to launch on a host with > 256 Logical Processors. #41731

Closed

Description

Windows Version

Microsoft Windows [Version 10.0.26100.33438]

WSL Version

2.9.13.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

6.18.40.1-1

Distro Version

Debian 13

Other Software

No response

Repro Steps

  • Deploy Windows Server 2025 on an Intel Granite Rapids 2-Socket Server running the Xeon6 6972P Processor with Hyperthreading enabled.
    • This will enumerate 384 Logical Processors.
  • Enable WSL2. Reboot the host if asked to do so.
  • Attempt to deploy Debian. Deployment will fail.
  • Restrict the Processor Count to 256 in the WSL Settings application.
  • Attempt to deploy Debian. Deployment will work.
  • Reset the Processor Count to the original 384 in the WSL Settings application.
  • Attempt to launch Debian. Launch will fail with the following error message.
The parameter is incorrect.
Error code: Wsl/Service/CreateInstance/CreateVm/HCS/E_INVALIDARG
  • Restrict the Processor Count to 256 in the WSL Settings application.
  • Attempt to launch Debian. Launch will succeed.

Expected Behavior

Described in Repro Steps.

Actual Behavior

Described in Repro Steps.

Diagnostic Logs

No response

Activity

  1. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor

    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-wsl-logs.ps1 -LogProfile networking instead, 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 [email protected] 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'.

  2. kgopal3-intel commented on Sep 29, 2026

    @kgopal3-intel
    Author
  3. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor
    Diagnostic information
    .wslconfig found
    Detected appx version: 2.9.13.0
    Detected user visible error: Wsl/Service/CreateInstance/CreateVm/HCS/E_INVALIDARG
    
  4. benhillis commented on Sep 30, 2026

    @benhillis
    Member

    I have a potential fix for this, but I don't have access to any literal supercomputers to test it out ;)

    Karthik Gopalakrishnan (@kgopal3-intel) - are you able to build a private WSL based on this branch to see if this resolves the issue you are seeing (after removing the config option to cap CPU count of course).

    #41741

    Thanks!

  5. kgopal3-intel commented on Sep 30, 2026

    @kgopal3-intel
    Author

    Hello Ben Hillis (@benhillis) - I don't think I have the ability to. If you can share detailed instructions, I can try. But it maybe faster if you just share a private binary with the fix with details to deploy. I have the platform ready to test. Thanks for the quick response.

  6. kgopal3-intel commented on Oct 2, 2026

    @kgopal3-intel
    Author

    Hello Ben Hillis (@benhillis) - Thank you for sharing the test package with me offline. I was able to deploy it on my test system & confirm that Debian in WSL2 launches successfully on this host with 384 LPs. Running nproc in Debian also shows 384.

    Let me know if you would like me to collect any other information. If not, we can close this bug & wait for the fix to make it to a release & retest.

    Thanks again for the quick turnaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions