WSL: WslRegisterDistribution failed with error: 0x80072746 [Updated with a Log]
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
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 21
wsl.2.2.4.0.x64 and right. That worked.
Seth
P.S. Thank you.
Diagnostic information
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.
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, 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!
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