Skip to content
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

WslRegisterDistribution failed with error: 0x80072749 #11844

Closed
1 of 2 tasks
THZ34 opened this issue Jul 26, 2024 · 7 comments
Closed
1 of 2 tasks

WslRegisterDistribution failed with error: 0x80072749 #11844

THZ34 opened this issue Jul 26, 2024 · 7 comments
Assignees

Comments

@THZ34
Copy link

THZ34 commented Jul 26, 2024

Windows Version

Microsoft Windows [版本 10.0.22635.3858]

WSL Version

2.3.11.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

6.6.36.3-1

Distro Version

Ubuntu 22.04

Other Software

Docker version 24.0.2, build cb74dfc

Repro Steps

wsl.exe --install Ubuntu-22.04

Expected Behavior

Enter the ubuntu subsystem

Actual Behavior

正在安装: Ubuntu 22.04 LTS
已安装 Ubuntu 22.04 LTS。
正在启动 Ubuntu 22.04 LTS...
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80072749
Error: 0x80072749 ???????????(????? sendto ???????????)???????????????????????

Press any key to continue...
分发“Ubuntu-22.04”的安装过程失败,退出代码: 1。
Error code: Wsl/InstallDistro/WSL_E_INSTALL_PROCESS_FAILED

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'.

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.

Copy link

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
.wslconfig found
Detected appx version: 2.3.11.0
Found no WSL traces in the logs

Copy link

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
.wslconfig found
Detected appx version: 2.3.11.0
Found no WSL traces in the logs

@THZ34
Copy link
Author

THZ34 commented Jul 26, 2024

Copy link

Diagnostic information
.wslconfig found
Detected appx version: 2.3.11.0
Found evidence of kernel panic: [    0.681892] Kernel panic - not syncing: Fatal exception in interrupt

@benhillis
Copy link
Member

@chessturo - another instance of a FPU-related kernel panic.

@chessturo
Copy link
Collaborator

Closing as a dup of #11791. We have a temporary fix listed there --- if the fix does not work for you, please let me know.

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

No branches or pull requests

3 participants