WslRegisterDistribution failed with error: 0x80072746 [Updated with a Log]

[silver2row]

Windows Version

Windows version: 10.0.22635.3930

WSL Version

WSL version: 2.3.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Kernel version: 6.6.36.3-1

Distro Version

Debian

Other Software

No response

Repro Steps

wsl --install Debian

Expected Behavior

I was expecting on Debian to be installed in my WSL2 instance.

Actual Behavior

wsl --install Debian

Debian GNU/Linux is already installed.

Launching Debian GNU/Linux...

Installing, this may take a few minutes...

WslRegisterDistribution failed with error: 0x80072746

Error: 0x80072746 An existing connection was forcibly closed by the remote host.

Press any key to continue...

The operation completed successfully.

Then, when I open Debian after the install, the output is this:

Installing, this may take a few minutes...

WslRegisterDistribution failed with error: 0x80072749

Error: 0x80072749 A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.

Press any key to continue...

After I press any key, the Distro WSL2 instance of Debian disappears.

Diagnostic Logs

[github-actions]

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

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:

• Installing Any Distro on WSL2 Fails with "WslRegisterDistribution failed with error: 0x80070002" (#5107), similarity score: 0.81

Closed similar issues:

• WslRegisterDistribution failed with error: 0x80070002 (#10660), similarity score: 0.82
• WslRegisterDistribution failed with error: 0x80070057 (#8216), similarity score: 0.81
• Installing Debian fails; RPC cancelled; failure in lxssmanager combase.dll (#5626), similarity score: 0.81
• WslRegisterDistribution failed with error: 0x80070057 (#11284), similarity score: 0.80

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

Diagnostic information

Detected appx version: 2.3.11.0
Found no WSL traces in the logs

[silver2row]

No sir-re-Bob, those listed 80% closeness rated hyperlinks serve no help to me. I tried some ideas in those links. Notta.

Seth

[WenjieXuCN]

Just a few days ago, after WSL automatically updated to version 2.3.11, I encountered the same issue as you. Rolling back to version 2.2.4 didn't resolve it either, and I couldn't use any WSL distributions. However, I discovered that this issue affects WSL 2 specifically. I was able to install Linux distributions with WSL 1.

[silver2row]

@WenjieXu2000 ,

Hello...thank you for your support. Is this just a common error that cannot be solved or are people, behind the scenes, working to address this issue as a viable error?

Seth

P.S. I want to keep WSL2 for all it offers but if WSL1 is the only cure for the error at hand, I can revert.

[silver2row]

@WenjieXu2000 , it worked. Thank you. I will test this for now.

Seth

[silver2row]

Does WSL2 work at all these days?

[silver2row]

I mean...I can get kernel 4.4.x to work via Debian on WSL1 but I miss my advancements in programming and newer language skills on VS Code and WSL2.

If you guys get it to work, please let me know.

Seth

[WenjieXuCN]

@silver2row, I've tried various reset methods, including removing WSL, Hyper-V, and Virtual Machine Platform, as well as disabling and re-enabling virtualization, but nothing has worked.

What's puzzling is that both of my computers have the latest version of WSL, yet only one of them is experiencing this problem and I can't seem to fix it!

[silver2row]

Hey @WenjieXu2000 ,

I think someone or "Me" erased an environment variable that may have something to do with the correct adaptation of WSL2 on my current working desktop.

Seth

P.S. In environment variables, maybe check the one that is workin' and port the correct variable to the computer that is not working.

Another Note:

I noticed that my current working desktop is going through issues on screen. The taskbar, hopefully totally unrelated, is starting to miss icons...

Anyway, I will get a working computer one day and look up the environment variables needed to have WSL2 instances run on it.

[silver2row]

So, something like:

dir env:

That will list your environment variables on your current desktop. I have WSLENV listed but it is not in working condition right now.

Seth

[silver2row]

https://devblogs.microsoft.com/commandline/share-environment-vars-between-wsl-and-windows/

That may help.

Seth

P.S. It is not a command of sorts but an understanding of how WSLENV works with WSL(N) and Windows(N). I cannot find more right now.

[github-actions]

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:

• WslRegisterDistribution failed with error: 0x80072746 (#11818), similarity score: 0.94
• WslRegisterDistribution failed with error: 0x8007273f (#7183), similarity score: 0.79

Closed similar issues:

• WslRegisterDistribution failed with error: 0x80070057 (#8216), similarity score: 0.80
• Installing Debian fails; RPC cancelled; failure in lxssmanager combase.dll (#5626), similarity score: 0.79
• WslRegisterDistribution failed with error: 0x80070002 (#10660), similarity score: 0.79

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

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.3.12.0
Found evidence of kernel panic: [    0.588558] Kernel panic - not syncing: Fatal exception in interrupt

[silver2row]

What now?

[WenjieXuCN]

@silver2row
Hi, I just rolled back to WSL version 2.2.4, and it seems to have resolved the issue. I successfully installed Debian and started it. Unlike before, this time I reinstalled using the wsl.2.2.4.0.x64.msi package instead of Microsoft.WSL_2.2.4.0_x64_ARM64.msixbundle.

Now, I've upgraded back to version 2.3.12, and the previous issue has reappeared. You might want to try rolling back to the wsl.2.2.4.0.x64.msi version of WSL to see if it resolves the issue.

[silver2row]

wsl.2.2.4.0.x64 and right. That worked.

Seth

P.S. Thank you.

[silver2row]

I installed the latest kernel and had a crash. Oops.

[silver2row]

Sorry...too embarrassed.

[zxy719]

@silver2row Hi, I just rolled back to WSL version 2.2.4, and it seems to have resolved the issue. I successfully installed Debian and started it. Unlike before, this time I reinstalled using the wsl.2.2.4.0.x64.msi package instead of Microsoft.WSL_2.2.4.0_x64_ARM64.msixbundle.您好，我刚刚回滚到 WSL 版本 2.2.4，似乎已经解决了该问题。我成功安装了 Debian 并启动了它。与以前不同，这次我使用 wsl.2.2.4.0.x64.msi 包而不是 Microsoft.WSL_2.2.4.0_x64_ARM64.msixbundle 重新安装。

Now, I've upgraded back to version 2.3.12, and the previous issue has reappeared. You might want to try rolling back to the wsl.2.2.4.0.x64.msi version of WSL to see if it resolves the issue.现在，我已经升级回2.3.12版本了，之前的问题又出现了。您可能需要尝试回滚到 WSL 的 wsl.2.2.4.0.x64.msi 版本以查看是否可以解决问题。

Thank you so much! I tried many methods without any progress until I found your reply.

[vishnumda]

Had the following issue with WSL version 2.3.14. Rolled back to 2.2.4 and that solved the problem.