You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WSL fails to launch on a host with > 256 Logical Processors. #41731
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 networking instead, following the instructions in Collect WSL logs for networking issues
Once completed please upload the output files to this GitHub issue.
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'.
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).
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.
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.
Activity
github-actions commentedon Sep 29, 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 [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'.
kgopal3-intel commentedon Sep 29, 2026
WslLogs-2026-09-29_16-28-37.tar.gz
github-actions commentedon Sep 29, 2026
Diagnostic information
benhillis commentedon Sep 30, 2026
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!
kgopal3-intel commentedon Sep 30, 2026
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.
kgopal3-intel commentedon Oct 2, 2026
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
nprocin Debian also shows384.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.