WSL icon indicating copy to clipboard operation
WSL copied to clipboard

WslRegisterDistribution failed with error: 0x8007273f

Open fschramka opened this issue 4 years ago • 80 comments

Windows Build Number

Microsoft Windows [Version 10.0.19043.1083]

WSL Version

  • [X] 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

fschramka avatar Jul 15 '21 12:07 fschramka

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.

johnfriedrich avatar Jul 16 '21 15:07 johnfriedrich

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

AleksSem avatar Jul 16 '21 15:07 AleksSem

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)

johnfriedrich avatar Jul 16 '21 16:07 johnfriedrich

/logs

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

benhillis avatar Jul 16 '21 16:07 benhillis

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!

ghost avatar Jul 16 '21 16:07 ghost

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-- avatar Jul 20 '21 16:07 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?

bison-- avatar Jul 20 '21 16:07 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?

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!:)

johnfriedrich avatar Jul 20 '21 16:07 johnfriedrich

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

bison-- avatar Jul 20 '21 17:07 bison--

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

johnfriedrich avatar Jul 20 '21 21:07 johnfriedrich

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

fschramka avatar Jul 22 '21 09:07 fschramka

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

bison-- avatar Jul 27 '21 19:07 bison--

Can verify the same issue on my end.

fishbone-translation avatar Jul 28 '21 02:07 fishbone-translation

Same issue here.

jet082 avatar Aug 09 '21 16:08 jet082

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.

vertan avatar Aug 12 '21 02:08 vertan

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

fschramka avatar Aug 16 '21 15:08 fschramka

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 ^^).

bison-- avatar Aug 19 '21 23:08 bison--

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?

benhillis avatar Aug 20 '21 00:08 benhillis

@benhillis Nope, just Windows Defender :)

fschramka avatar Aug 20 '21 11:08 fschramka

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.

Toliak avatar Aug 20 '21 20:08 Toliak

Is reinstalling the windows the only way around it?

felipegodias avatar Aug 21 '21 02:08 felipegodias

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

alikrc avatar Aug 22 '21 22:08 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

johnfriedrich avatar Aug 23 '21 23:08 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

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

alikrc avatar Aug 24 '21 06:08 alikrc

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

alikrc avatar Aug 26 '21 14:08 alikrc

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

Toliak avatar Aug 27 '21 10:08 Toliak

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)

TheJaysH avatar Sep 03 '21 12:09 TheJaysH

I have the exact same problem and I have tried everything I can think about except reinstalling Windows. Reinstalling Windows is just not an option for me at this stage as it will break everything else and it is just to time consuming to fix everything again.

Also logged in Feedback Hub: https://aka.ms/AAdxv2e

Windows Build Number

Microsoft Windows [Version 10.0.19043.1266]

WSL Version

  • [x] WSL 2
  • [ ] WSL 1

Kernel Version

5.10.16

Distro Version

Ubuntu 20.04 LTS

Other Software

Also Docker version 4.1.0.69386 is failing with same error.

Repro Steps

Install WSL like stated in https://docs.microsoft.com/en-us/windows/wsl/install-win10

Additional steps:

  • 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

Error Message on Screen:

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

Expected Behavior

An error free installation and the possibility to start Ubuntu 20.04 LTS without getting an error.

Actual Behavior

  1. Setting up / make computer ready to use WLS2
  2. Ensure Windows 10 is up to date.
  3. Setting WSL to version 2 - wsl --set-default-version 2.
  4. Ensure WSL" is on newest Kernel Version.
  5. Installing Ubuntu 20.04 LTS (Doesn't matter if you do it form MS Store, via WSL CL and other CL commands).
  6. Error Message on Screen:
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...

Installing Ubuntu 20.04 LTS under WSL1 do not create any error and it start without any problem. But migrating it from WSL! to WSL" is not possible:

$ wsl  --set-version Ubuntu-20.04 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
An address incompatible with the requested protocol was used.

Diagnostic Logs

log-wsl.etl.zip

Line #, Provider Name, Task Name, Opcode Name, Id, Process, Event Name, Cpu, ThreadId, Field 1, Field 2, Field 3, Field 4, Field 5, Field 6, Field 7, Field 8, Field 9, Count, Time (s) 14, , Error, win:Info, 0, Unknown, Error, 13, 11872, onecore\vm\wsl\lxss\lxcmdlineshared\hvsocket.cpp, 116, 0, 19, 11872, 0x8007273F, , , , 1, 5,891471600

Line #, Provider Name, Task Name, Opcode Name, Id, Process, Event Name, Cpu, ThreadId, Field 1, Field 2, Field 3, Field 4, Field 5, Field 6, Field 7, Field 8, Field 9, Count, Time (s)
1, Microsoft-Windows-Host-Network-Service, , , , , , , , , , , , , , , , , 33, 
2, , OnRundown, win:Info, 0, Unknown, , , , , , , , , , , , , 2, 
3, , Entity, win:Info, 0, Unknown, , , , , , , , , , , , , 5, 
4, , Enter function, win:Info, 0, Unknown, , , , , , , , , , , , , 11, 
5, , Exit function, win:Info, 0, Unknown, , , , , , , , , , , , , 12, 
6, , TimerCallback, win:Info, 0, Unknown, TimerCallback, 17, 22032, , , , , , , , , , 1, 11,692724200
7, , GoalStateDriverCallBack, , , , , , , , , , , , , , , , 2, 
8, Microsoft.Windows.Lxss.Manager, , , , , , , , , , , , , , , , , 11, 
9, , CreateInstanceBegin, win:Info, 0, Unknown, , , , , , , , , , , , , 3, 
10, , CreateInstanceEnd, win:Info, 0, Unknown, , , , , , , , , , , , , 3, 
11, , VerboseLog, win:Info, 0, Unknown, VerboseLog, 4, 11872, onecore\vm\wsl\lxss\service\lib\lxssusersession.cpp, 495, 1, 11872, 0x80040302, , , , , 1, 5,512523000
12, , RegisterDistributionBegin, win:Info, 0, Unknown, RegisterDistributionBegin, 19, 11872, Ubuntu-20.04, 0, , , , , , , , 1, 5,728124300
13, , CreateVmBegin, win:Info, 0, Unknown, CreateVmBegin, 13, 11872, 16777216, , , , , , , , , 1, 5,852569700
14, , Error, win:Info, 0, Unknown, Error, 13, 11872, onecore\vm\wsl\lxss\lxcmdlineshared\hvsocket.cpp, 116, 0, 19, 11872, 0x8007273F, , , , 1, 5,891471600
15, , RegisterDistributionEnd, win:Info, 0, Unknown, RegisterDistributionEnd, 5, 11872, Ubuntu-20.04, 0x8007273F, 2, 16777216, , , , , , 1, 5,893517400
16, Microsoft-Windows-Hyper-V-Compute, , , , , , , , , , , , , , , , , 10, 
17, , , , 2014, Unknown, Microsoft-Windows-Hyper-V-Compute//, 0, 40432, 3394F7D2-1B56-41E7-81C9-8A53BEC3F814, , , , , , , , , 1, 5,854123600
18, , , , 2000, Unknown, Microsoft-Windows-Hyper-V-Compute//, 0, 40432, 3394F7D2-1B56-41E7-81C9-8A53BEC3F814, 0xC0370103, , , , , , , , 1, 5,854171700
19, , , , 2009, Unknown, , , , , , , , , , , , , 3, 
20, , , , 2008, Unknown, , , , , , , , , , , , , 2, 
21, , , , 102, Unknown, , , , , , , , , , , , , 3, 
22, EventMetadata, Event Metadata: Event Info, , 0, Unknown, , , , , , , , , , , , , 7, 
23, WinSATAssessment, , , , , , , , , , , , , , , , , 3, 
24, , WinSAT: WinSPR Compressed Info, , 0, Unknown, WinSAT: WinSPR Compressed Info, 6, 0, , , , , , , , , , 1, 43,113888700
25, , WinSAT: Metrics Compressed Info, , 0, Unknown, WinSAT: Metrics Compressed Info, 6, 0, , , , , , , , , , 1, 43,113888700
26, , WinSAT: SystemConfig Compressed Info, , 0, Unknown, WinSAT: SystemConfig Compressed Info, 6, 0, , , , , , , , , , 1, 43,113888700
27, Microsoft-Windows-Hyper-V-Worker, , , , , , , , , , , , , , , , , 2, 
28, , , , 18609, Unknown, Microsoft-Windows-Hyper-V-Worker//, 4, 49228, Virtual Machine, 3394F7D2-1B56-41E7-81C9-8A53BEC3F814, 0x060277CB67F39FBF, 0x000000000050381F, 0x0000000000044120, 2, 8, 0, , 1, 5,882530500
29, , , , 3452, Unknown, Microsoft-Windows-Hyper-V-Worker//, 16, 49232, Virtual Machine, 3394F7D2-1B56-41E7-81C9-8A53BEC3F814, %%2147749889, 0x80041001, , , , , , 1, 5,891768400
30, EventTrace, EventTrace [Provider], , 0, Unknown, EventTrace [Provider], 0, 39000, , , , , , , , , , 1, 43,113073500

Triopticon avatar Oct 01 '21 18:10 Triopticon

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.

npnance avatar Oct 13 '21 17:10 npnance

Then starting Ubuntu 20.04 LTS from the start menu tile worked and it installed successfully.

I am sure your Ubuntu 20.04 LTS worked under WSL1. You can check WSL version for each distro by command: wsl -l -v

jubba2001 avatar Oct 16 '21 13:10 jubba2001