-
Notifications
You must be signed in to change notification settings - Fork 846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better error messages and known exit codes for wsl.exe #12132
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload 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-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Closed similar issues:
|
/feature |
Diagnostic information
|
wsl.exe
prints some error numbers and returns some error return codes which get printed in TerminalIt would be nice to have text explanations printed in Terminal instead of
Wsl/Service/0xd00002fe
and somehow let Terminal recognize exit-codes such as 0xffffffff and have it print some reason corresponding to this exit-code.Original discussion:
The text was updated successfully, but these errors were encountered: