Skip to content

Green screen after standing When wsl again, accompany Wsl/Service/CreateInstance/E_UNEXPECTED #12892

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

Closed
1 of 2 tasks
Darkluna999 opened this issue May 11, 2025 · 6 comments
Closed
1 of 2 tasks

Comments

@Darkluna999
Copy link

Windows Version

Microsoft Windows [Version 10.0.27842.1000]

WSL Version

2.5.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

Green screen after standing. When wsl again, accompany Wsl/Service/CreateInstance/E_UNEXPECTED

Expected Behavior

Startup as usual

Actual Behavior

When wsl again, accompany Wsl/Service/CreateInstance/E_UNEXPECTED

Diagnostic Logs

No response

Copy link

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-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
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] 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'.

@benja2998
Copy link

I am unable to understand what you're saying.

@Darkluna999
Copy link
Author

Darkluna999 commented May 14, 2025

I am unable to understand what you're saying.

I don't know what happened. When wsl was running in the background, the computer had a green screen error. Then, when wsl was started again, it could not be started and prompted Wsl/Service/CreateInstance/E_UNEXPECTED. I have reinstalled the distribution running internally of wsl and have not been able to replicate the problem again. Related to this, wsl could not be used when windows was updated to version 27818, similar to this green screen error situation.Of course, I noticed that the previous green screen error no longer appears frequently under version 27842. I wonder if it is relevant.

@OneBlue
Copy link
Collaborator

OneBlue commented May 15, 2025

/logs

Copy link
Contributor

Hello! Could you please provide more logs to help us better diagnose your issue?

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 scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

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

No branches or pull requests

3 participants