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
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370109
Error: 0x80370109 The operation timed out because a response was not received from the virtual machine or container.
Press any key to continue...
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered:
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:
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'.
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!
Windows Version
Microsoft Windows [Version 10.0.22631.4249]
WSL Version
2.3.24.0
Are you using WSL 1 or WSL 2?
Kernel Version
Default Version: 2
Distro Version
Ubuntu
Other Software
Docker Desktop
Repro Steps
Update Windows
Expected Behavior
Running Ubuntu WSL
Actual Behavior
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370109
Error: 0x80370109 The operation timed out because a response was not received from the virtual machine or container.
Press any key to continue...
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: