search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.54k stars 823 forks source link

wsl 2.4.4.: An assertion failure has occurred. Error code: Wsl/Service/0x8007029c [SOLVED - but...] #12294

Open josemtella opened 1 week ago

josemtella commented 1 week ago

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

github-actions[bot] commented 1 week ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please 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:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

espresso3389 commented 1 week ago

I have the same issue. And, just trying to install another distro (debian), it shows the following error:

Image

Marukome0743 commented 1 week ago

The log file: WslLogs-2024-11-20_09-59-45.zip

josemtella commented 1 week ago

logs file WslLogs-2024-11-19_17-12-08.zip

github-actions[bot] commented 1 week ago
Diagnostic information ``` .wslconfig found Detected appx version: 2.4.4.0 Detected user visible error: Wsl/Service/0x8007029c ```
thomasyangbo commented 1 week ago

the same problemWslLogs-2024-11-21_11-59-48.zip

ssi-kt commented 1 week ago

I had the same issue, but it was resolved by downgrading to version 2.3.26.

thomasyangbo commented 1 week ago

I had the same issue, but it was resolved by downgrading to version 2.3.26.

how to downgrade to 2.3.26?

ssi-kt commented 1 week ago

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 only need to run either wsl.2.3.26.0.x64.msi or wsl.2.3.26.0.arm64.msi. Which one to run depends on your environment.

espresso3389 commented 1 week ago

how to downgrade to 2.3.26?

To downgrade WSL version is very easy regardless of how you install WSL 2.4.4:

wsl --uninstall
wsl --install Ubuntu-24.04

Ubuntu-24.04 on the command line is just a example, use any distro you want to install.

OneBlue commented 6 days ago

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.

josemtella commented 5 days ago

Tank @OneBlue, Indeed, the characters in the "prompt" environment variable are causing the error. I have:

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. Just putting the previous prompt back, it fails again

I would like to keep the prompt, please consider this a bug.

github-actions[bot] commented 5 days ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please 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:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

josemtella commented 5 days ago

I leave the logs once I have seen the problem with my answer: https://github.com/microsoft/WSL/issues/12294#issuecomment-2495421233

WslLogs-2024-11-23_11-13-40.zip

github-actions[bot] commented 5 days ago
Diagnostic information ``` .wslconfig found Detected appx version: 2.4.4.0 ```
benhillis commented 3 days ago

@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?

josemtella commented 2 days ago

@benhillis see:

Image

josemtella commented 2 days ago

[code] set var=└─ [/code]

benhillis commented 2 days ago

Thanks! I have confirmed my fix resolves this issue.