-
Notifications
You must be signed in to change notification settings - Fork 822
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
wsl 2.4.4.: An assertion failure has occurred. Error code: Wsl/Service/0x8007029c [SOLVED - but...] #12294
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:
|
The log file: |
logs file |
Diagnostic information
|
the same problemWslLogs-2024-11-21_11-59-48.zip |
I had the same issue, but it was resolved by downgrading to version 2.3.26. |
how to downgrade to 2.3.26? |
https://github.com/microsoft/WSL/releases/tag/2.3.26 |
To downgrade WSL version is very easy regardless of how you install WSL 2.4.4:
|
Thank you @josemtella. Looking at the logs, the issue seems to be coming from a string encoding errors. Could you share what's your Windows username, and what environment variables you have set on the machine ? I wonder if there are special characters that are causing this error. |
Tank @OneBlue, Indeed, the characters in the "prompt" environment variable are causing the error. prompt=$_$E[92m┌─$E[93m[CMD]$E[92m─($E[94mcpanld4@%computername%$E[92m)$_└─$E[93m[$E[97m$p$E[93m]$E[94m$$$S$E[0m If I remove it or set the value prompt=[$p], the Linux distributions boot without problems. I would like to keep the prompt, please consider this a bug. |
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! Open similar issues:
Closed similar issues:
|
I leave the logs once I have seen the problem with my answer: #12294 (comment) |
Diagnostic information
|
@josemtella - I think I have a fix, could you give me some instructions on how validate this? You're setting some environment variable on the Windows side right? |
@benhillis see: |
[code] |
Thanks! I have confirmed my fix resolves this issue. |
Windows Version
Microsoft Windows [Version 10.0.26100.2448]
WSL Version
2.4.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.167.4-1
Distro Version
Any distro
Other Software
No response
Repro Steps
start any distro
Expected Behavior
start distro
Actual Behavior
The error
An assertion failure has occurred. Error code: Wsl/Service/0x8007029c
appears and the distribution does not start.Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: