WSL: WslRegisterDistribution failed with error: 0x8007273f
Windows Build Number
Microsoft Windows [Version 10.0.19043.1083]
WSL Version
- WSL 2
- WSL 1
Kernel Version
No response
Distro Version
Ubuntu 20.04 LTS
Other Software
No response
Repro Steps
Install WSL like statet in https://docs.microsoft.com/en-us/windows/wsl/install-win10
- Virtual Machine Platform active
- Windows Subsystem for Linux active
- Virtualization activated in BIOS
wsl --set-default-version 2
Open Windows Store, get and install Ubuntu 20.04 LTS. Start Ubuntu
Expected Behavior
The installation process as it should be.
Actual Behavior
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x8007273f
Error: 0x8007273f An address incompatible with the requested protocol was used.
Press any key to continue...
This error occurs out of nowhere… 😦
Diagnostic Logs
No response
About this issue
- Original URL
- State: open
- Created 5 years ago
- Reactions: 17
- Comments: 80 (3 by maintainers)
From July 15, the problem has not yet been solved. Microsoft ignores customers.
I just reinstalled Windows via Media Installer(from inside windows), while keeping all Apps and Data and it working again without doing anything further.
After a day of debugging with no findings that was the only viable solution for me (cost wise)
@Toliak @felipegodias @alikrc Reinstalling windows from inside windows with keeping apps and data only takes 10-20 minutes and nothing will be lost. I tried debugging a full working day before trying that and wasn’t able to fix it. I tried clean installs of wsl etc. I know it’s super frustrating that there is no proper solution, but this works and its quick
I will wait for an “smarter” fix - reinstalling Windows can not be the only solution^^
Edit: See below reply, this just installed it under WSL1. Ignore this.
So, this is ridiculous, but it worked for me. This is the approximate steps I took, but I can’t confirm 100%. Nothing else I tried worked, including uninstalling/reinstalling the WSL feature, unchecking IPv6 on every network adapter, and all Windows updates, with reboots in-between everything.
First, run this in an elevated prompt:
wsl --set-default-version 1
then:
bash sudo apt-get update sudo apt-get dist-upgrade exit
then, exit, and reopen a new elevated cmd:
ubuntu sudo apt-get update sudo apt-get dist-upgrade exit
then:
wsl --set-default-version 2
Then starting Ubuntu 20.04 LTS from the start menu tile worked and it installed successfully.
same here, docker not working since this issue occured, i tried everything and spent hours. Any solution would be appreciated except reinstalling windows
I have the same issue now (2021-07-20) after Microsoft support on twitter told me to update the windows store because i had this funny bug with the store https://twitter.com/bison_42/status/1416385301627408391 and now it doesn’t work anymore with the exact error message.
(its the same message but in german)
You don’t need to do that. Windows 10 and above has the ability to refresh itself without the need of an ISO. while keeping files and settings.
it is work!
@drathier @ddr-09
no VPN or similar software is installed on my machine 😕
meanwhile I updated my win10 to 21H2 - issue still here 😦
Dear developers of WSL, could you at least print out more diagnostics or provide the option to export more verbose plain text logs when wsl fails with this kind of error? That way we the users can help with diagnosing and troubleshooting. Right now wsl has basically been unusable for months and there’s nothing we can do except trying reinstalling windows while preserving apps/files, which you cannot expect everyone to be casually doing on a work machine loaded with apps and projects.
This error code translates to WSAEAFNOSUPPORT. I suspect you have some kind of antivirus / firewall installed that is blocking the address family used by hyper-v sockets:
#define AF_HYPERV 34@ralke1 WSL1 never had this issue - setting the version to WSL1 will of course solve the problem with WSL2 because there is no WSL2 😊
@Toliak
It’s Feb 19, 2023 and I went from a working Ubuntu install to it not starting. As people mentioned in this and other threads, I had just had a MS update applied - It removed the vhdx file, and when I went to re-install ubuntu, it gave this error.
Following these steps worked without issue on my system. and I was able to re-install ubuntu. I always back up my important things in WSL to my windows system on another drive and only lost a couple of batch files.
After trying every solution in this issue and #5092, this is the only solution that worked. Took about an hour and messed up all my virtual audio cables, but that’s an easier fix than trying to figure out why Microsoft’s own updates break their WSL time and time again.
I had the same issue here. I vaguely remember it is after I rebooted my computer to adapt a new update that prompted me several days ago ( I haven’t shut down my laptop since the first prompt ). However, I am not sure if that is exactly the issue.
The problem occurs today. At first, I got an error message saying
The specified module could not be found.with code 4294967295, which I did not find anyone with the same issues online. So I just followed the thread with the same error code https://github.com/microsoft/WSL/issues/5092.It seems like most of those solutions have no impact on me. The last thing I tried is to turn off the WSL feature in Windows Features manually, reboot, turn it on again, and reboot again. Then, the error message has changed to:
An address incompatible with the requested protocol was used.I was still not able to solve this issue, tho. So I decided to reinstall the WSL to see if I could get better luck. I did
wsl --unregister Debianin Windows Terminal. Then, I am not able to install it again, which guided me here.I currently have two WSL installed, Ubuntu and Debian. My Ubuntu distribution hasn’t been used for a while but there is no issue with it. All issues above are related to my Debian one.
I think there is something bigger going on here. I have the same issue with WSL2, Sandbox and docker. None of these are starting. And all state (in one way or another) the following error:
Code:
0x8007273fIn the case of Sandbox this is the full error:
Is there any update on what this means, I feel like ive tried everything. I cant pinpoint when WSL2 stopped working, but at some point it just stopped along with docker and sandbox. So I’m willing to assume a rogue update has caused this.
I just feel even though the re-install doesnt take long, it is still a nuke approach (imo) and I’d like to know the root cause of the issue.
EDIT: Same issue with Hyper-V
Since the reinstalling seems to be the only way to fix that, I would like to provide briefly guide How to reinstall windows without apps / data loss (source)
Pre-requirements:
Steps:
setup.exe