WslRegisterDistribution failed with error: 0x8007273f

[fschramka]

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

[johnfriedrich]

Same for me, but with Debian.

Win Version 21H1 (Build 19043.1081)

Tried removing Linux Subsystem, removing those features but no luck at all.

In my case I used the "Fix startup issues" in rescue mode due to an issue. After that, it was broken. Worked before without any issues.

[AleksSem]

I got same issue after update today. Trying to reinstall evrything but won't helped.

[johnfriedrich]

I got same issue after update today. Trying to reinstall evrything but won't helped.

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)

[benhillis]

/logs

Judging by the error message, I suspect you may have some kind of AV software blocking the hvsocket address family.

[ghost]

Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it.

Thank you!

[bison--]

I got same issue after update today. Trying to reinstall evrything but won't helped.

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.

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x8007273f
Error: 0x8007273f Es wurde eine Adresse verwendet, die mit dem angeforderten Protokoll nicht kompatibel ist.

Press any key to continue...

(its the same message but in german)

[bison--]

@johnfriedrich

I just reinstalled Windows via Media Installer, while keeping all Apps and Data and it working again without doing anything further.

does it still work after you installed ALL new updates?

[johnfriedrich]

@johnfriedrich

I just reinstalled Windows via Media Installer, while keeping all Apps and Data and it working again without doing anything further.

does it still work after you installed ALL new updates?

Yes it does work fine after installing the latest Windows Updates. Was required to due to IT security policy, so I had to find out!:)

[bison--]

Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it.

Thank you!

@msftbot i did that now https://aka.ms/AAd8sm5

[johnfriedrich]

Sorry cant provide logs anymore, but in my case I had no anti virus installed and there wasn't a vEthernet (WSL) adapter installed

[fschramka]

@msftbot my logs are here: https://aka.ms/AAd9fui

I showed that a WSL 1.0 is currently installed, default installation version is WSL 2.

• Installed Debian and started it --> error: 0x8007273f
• Wanted to upgrade the WSL 1.0 to 2.0 --> "An address incompatible with the requested protocol was used."

@benhillis No AV software other than the windows defender is installed.

[bison--]

I got same issue after update today. Trying to reinstall evrything but won't helped.

I just reinstalled Windows via Media Installer, while keeping all Apps and Data and it working again without doing anything further.

can confirm now that this works without re-installing everything.
Windows re-install from a media installer (launching the setup from WITHIN windows and keeping all apps+data) is enough to make it work again (uninstalled all ubuntu versions before hand, maybe thats important?).
And BIG thanks @johnfriedrich

[fishbone-translation]

Can verify the same issue on my end.

[jet082]

Same issue here.

[vertan]

I got same issue after update today. Trying to reinstall evrything but won't helped.

I just reinstalled Windows via Media Installer(from inside windows), while keeping all Apps and Data and it working again without doing anything further.

This was the only solution that worked for me as well. I'm still not sure when this 0x8007273f issue started, but it's a bit worrying that it seemingly came from nowhere and had me spend hours on trying different solutions to get rid of.

[fschramka]

I will wait for an "smarter" fix - reinstalling Windows can not be the only solution^^

[bison--]

I will wait for an "smarter" fix - reinstalling Windows can not be the only solution^^

@fschramka it is more like a repair-installation like back in the days with Win95/Win98. With my mentioned way you do not have to re-install any program (better make a full-backup before anyway ^^).

[benhillis]

0x8007273f (WSAEAFNOSUPPORT) is most often due to a third party firewall or AV software. Do you have any AV / firewall aside from Defender or the inbox firewall?

[fschramka]

@benhillis Nope, just Windows Defender :)

[Toliak]

The same issue.
I have already installed Debian distro and, unfortunately, one day it just broken down with message An address incompatible with the requested protocol was used.

When I tried to install Ubuntu distro, I received the same error like at the first message of this issue.

I'm using Windows 10 Home

Microsoft Windows [Version 10.0.19042.1165]

Re-installing Windows with keeping the data looks like a workaround. Is there any less painful solutions?

UPD: I have tried to reinstall WSL using this guide, several reboots and wsl --install --distribution Debian. The error still appears.

[felipegodias]

Is reinstalling the windows the only way around it?

[alikrc]

same here, docker not working since this issue occured, i tried everything and spent hours. Any solution would be appreciated except reinstalling windows

[johnfriedrich]

@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

[alikrc]

@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

Thanx for clarifying, i will try 👍 i thought my data will be lost

[alikrc]

Reinstalling windows worked for me but took a lot of time for me to get apps to current state

[Toliak]

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:

• Stable internet connection

Steps:

1. Download Media Creation Tool from Microsoft Website ("Download tool now" button)
2. Click "Create installation media for another PC" -> "ISO File" -> Save it somewhere on your PC
3. Mount the created ISO file (I have used Deamon Tools Lite) and run setup.exe
4. There should be a caption like "Data will be stored". Reinstall the windows

[TheJaysH]

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:

An address incompatible with the requested protocol was used.

Code: 0x8007273f

In the case of Sandbox this is the full error:

Windows Sandbox failed to start.
Error 0x8007273f. An address incompatible with the requested protocol was used.
Would you like to submit feedback about this issue?

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

[Window Title]
Virtual Machine Connection

[Main Instruction]
The application encountered an error while attempting to change the state of 'Ubuntu 18.04.3 LTS'.

[Content]
'Ubuntu 18.04.3 LTS' failed to start.

Microsoft Synthetic Rdp Device (Instance ID 9ED5FD4B-40C3-4DE3-8597-98ECD17035DA): Failed to Power on with Error 'An address incompatible with the requested protocol was used.'.

[Expanded Information]
'Ubuntu 18.04.3 LTS' failed to start. (Virtual machine ID 1F3D3AE6-0980-4D98-82C2-0C8022075385)

'Ubuntu 18.04.3 LTS' Microsoft Synthetic Rdp Device (Instance ID 9ED5FD4B-40C3-4DE3-8597-98ECD17035DA): Failed to Power on with Error 'An address incompatible with the requested protocol was used.' (0x8007273F). (Virtual machine ID 1F3D3AE6-0980-4D98-82C2-0C8022075385)

[darrenmason]

I have this issue as well, "An address incompatible with the requested protocol was used." -- just happened to me out of the blue after some Windows updates. I have tried all the common remedies to no avail.

Update: I fixed the issue by running the Windows 10 installer (MediaCreationTool21H2) and preserving all apps and files. Fixed WSL without losing anything, though I would do an image backup just in case, if you choose this route. Would love to know what actually broke.

[yuanchen-zhu]

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.

[sethmayer]

@craigloewen-msft any level of support or acknowledgement here would be appreciated

[ddr-09]

@drathier Same, disconnecting nordvpn fixed this exact issue

[fschramka]

@drathier @ddr-09

no VPN or similar software is installed on my machine :/

meanwhile I updated my win10 to 21H2 - issue still here :(

[skyruzhen]

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.

it is work!

[fschramka]

@skyruzhen

This does not elevate your WSL version from 1 to 2... As the author of the quote you posted wrote himself in the top "Edit...".

Open a powershell and check with wsl -l -v if you have WSL 2 ;)

[CocaKolev]

I don't have a solution to the WSL2 not working, I had the same issue and continue being unable to get it to launch. However, for anyone else that was stuck trying to get WSL1 to work after WSL2 failed multiple times, ensure you have wsl --set-default-version 1 set before attempting to reinstall anything. Otherwise every command off of the Microsoft docs will continue to fail as the system assumes you're attempting to get WSL2 working.

Hopefully this can save someone a headache when getting the above error just trying to install WSL1.

[term-est]

I am also having the same issue when I try to use WSL2
Docker also doesn't work and Windows Sandbox gives a similar error

Windows Sandbox failed to start. Error 0x8007273f. An address incompatible with the requested protocol was used. 

I tried disable/reenable WSL/HYPER-V/Virtualisation, tried sfc /scannow and dism /Online /Cleanup-Image /RestoreHealth and billion more stuff.

The solution cannot possibly be "Just reinstall windows"

[sethmayer]

The solution cannot possibly be "Just reinstall windows"

Sadly an in-place reinstall is the only solution at this point

[Theaninova]

I had to do the soft reinstall as well, can't believe this was the only thing that fixed it.

[M2xAy]

Same problem here with Windows 10 Enterprise. Please help i investigated many hours. I can not reinstall windows beacause its a compony pc

[Shalankwa]

I also starting getting this error today after a windows update. The update seemed to have had and issue and Automatic repair ran after a few reboots.
Once I was able to sign in, wsl (ubuntu-22.04) would fail to load stating:

An address incompatible with the requested protocol was used.
Error code: Wsl/Service/CreateInstance/CreateVm/0x8007273f

I also tried to install a new wsl distro to see what would happen and I get the same error.

Since im part of the insider program I'm actually unable to do a re-install of windows 11 without clearing all apps & files which i really want to avoid because theres some files I have stuck in my wsl distro I would like to recover.

Has anyone been able to fix this issue without a re-install? Still haven't been able to find any good information about this rather than this issue thread.

[M2xAy]

I also starting getting this error today after a windows update. The update seemed to have had and issue and Automatic repair ran after a few reboots. Once I was able to sign in, wsl (ubuntu-22.04) would fail to load stating:

An address incompatible with the requested protocol was used.
Error code: Wsl/Service/CreateInstance/CreateVm/0x8007273f

I also tried to install a new wsl distro to see what would happen and I get the same error.

Since im part of the insider program I'm actually unable to do a re-install of windows 11 without clearing all apps & files which i really want to avoid because theres some files I have stuck in my wsl distro I would like to recover.

Has anyone been able to fix this issue without a re-install? Still haven't been able to find any good information about this rather than this issue thread.

unfortunately i am also waiting for a solution. @msftgits please find a solution. I can not reinstall the OS

[hexadecimality]

turned on Hyper-V and made restart. it worked for me

[sdimos]

Had this same issue and got it resolved! Not sure which part helped but I outlined my workflow here: #5215 (comment)

[fschramka]

Can anybody else (@AleksSem, @bison--, @fishbone-translation, @Toliak, @felipegodias, @TheJaysH, @CosmoMaaya, @Gabriellavoura, @weyh, @M2xAy, @Shalankwa) who is still stuck on WSL1 check if the solution described by @sdimos in #5215 (comment) works?

I upgraded my PC platform from the Intel 5th Gen to a AMD Ryzen Zen 3 system and installed Windows 11 - there the problem did not occur again - yaaay🎉

I still have the SSD with the old system - if nobody else can try it, I would try it with the old Win10 install. We need proof before I close this issue🤔🤓

[TheJaysH]

@fschramka
This was a while ago. But I remember doing a reset of windows (keeping files and settings) that solved it for me.

[fschramka]

@TheJaysH
Thanks for the reply - alright. Well that was/is the only known working solution so far.

Somebody still needs to check @sdimos solution 😊 for the sake of all those who will have the same issue.

[tempest2023]

I have the same problems. Unfortunately, I even can not update my windows version to 21H2. The windows updates tried lots of times and every time it shows fail to update with error code 0x800f0922. I can not fix this problem. And it also cause other terrible problems:

1. I can not shutdown my machine until kill power, it always restart automatically
2. Docker Desktop crashed immediately after opening.
3. When starting up, windows is automatically updated periodically (every day now), and rolls back because it fails everytime, and the booting time exceeds 5-8 minutes.

I don't know how they are determined to automatically update these buggy patches to users. It crashed all my work on my WSL2.
It seems like reinstall the whole OS is the only solution.

[hexadecimality]

try to turn off VPN and update WSL

[jeancallisti]

There still isn't a "soft" fix for this??? Wtf?

[fschramka]

@jeancallisti @623059008

We could not verify the solution posted by @sdimos in #5215 (comment)

If you still have a broken WSL2 instance - please try this first.

[psyhawk]

@Toliak

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:
* Stable internet connection

Steps:
1. Download Media Creation Tool from Microsoft Website ("Download tool now" button)
2. Click "Create installation media for another PC" -> "ISO File" -> Save it somewhere on your PC
3. Mount the created ISO file (I have used Deamon Tools Lite) and run setup.exe
4. There should be a caption like "Data will be stored". Reinstall the windows

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.

[TheJaysH]

@Toliak

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:

• Stable internet connection
  Steps:

1. Download Media Creation Tool from Microsoft Website ("Download tool now" button)
2. Click "Create installation media for another PC" -> "ISO File" -> Save it somewhere on your PC
3. Mount the created ISO file (I have used Deamon Tools Lite) and run setup.exe
4. There should be a caption like "Data will be stored". Reinstall the windows

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.

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.

[Snahoj]

Whats worked for me was , Set default the WLS version to 1 , and then go to the network device -> properties->
extensible virtual switch for hyperv -> install -> add the sings and then try to install and that's

PD. Previously i tried all the solutions before you posted here

[ysterbal]

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.

it is work!

This worked for me, downgrade to WSL 1, update kernel set wsl 2 and restart shakes head

[psyhawk]

@Toliak

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:

• Stable internet connection
  Steps:

1. Download Media Creation Tool from Microsoft Website ("Download tool now" button)
2. Click "Create installation media for another PC" -> "ISO File" -> Save it somewhere on your PC
3. Mount the created ISO file (I have used Deamon Tools Lite) and run setup.exe
4. There should be a caption like "Data will be stored". Reinstall the windows

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.

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.

While I didn't state that, I had already tried your suggestion. my vxhd file was NOT restored.
Thanks for down voting instead if asking if I had tried that.