WslRegisterDistribution failed with error: 0xffffffff

Please fill out the below information:

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.18945.1001]

What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
PS C:\WINDOWS\system32> wsl --set-version ubuntu 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Error: 0xffffffff

PS C:\WINDOWS\system32> wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu (Default)
PS C:\WINDOWS\system32> wsl --list --verbose
NAME      STATE           VERSION

Ubuntu    Stopped         1

PS C:\WINDOWS\system32> WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
FeatureName      : Microsoft-Windows-Subsystem-Linux
DisplayName      : Windows Subsystem for Linux
Description      : Provides services and environments for running native user-mode Linux shells and tools on Windows.
RestartRequired  : Possible
State            : Enabled
CustomProperties :
ServerComponent\Description : Provides services and environments for running native user-mode Linux
shells and tools on Windows.
ServerComponent\DisplayName : Windows Subsystem for Linux
ServerComponent\Id : 1033
ServerComponent\Type : Feature
ServerComponent\UniqueName : Microsoft-Windows-Subsystem-Linux
ServerComponent\Deploys\Update\Name : Microsoft-Windows-Subsystem-Linux
PS C:\WINDOWS\system32> wsl --unregister ubuntu
Unregistering...
PS C:\WINDOWS\system32> ubuntu
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0xffffffff
Error: 0xffffffff (null)
Press any key to continue...

What's wrong / what should be happening instead:
I've got error

Strace of the failing command, if applicable:  (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).

For WSL launch issues, please collect detailed logs.

See our contributing instructions for assistance.
wsl.zip

For google indexing
onecore\vm\wsl\lxss\service\lib\utilityvmcontext.cpp
 1196
 0
26
 20132
0xFFFFFFFF

onecore\vm\wsl\lxss\service\lib\utilityvmcontext.cpp
 1183
 0
25
 20132
0xFFFFFFFF
HcnCreateNetwork failed (null)

HcnCreateNetwork failed (null)

HcnCreateNetwork failed
Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          01.08.2019 8:32:36
Event ID:      233
Task Category: None
Level:         Information
Keywords:      (128)
User:          SYSTEM
Computer:      nc
Description:
The operation 'Delete' succeeded on nic A02CEDA8-C5D8-4D31-8771-08945EDF7CE8 (Friendly Name: WSL).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67dc0d66-3695-47c0-9642-33f76f7bd7ad}" />
    <EventID>233</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000080</Keywords>
    <TimeCreated SystemTime="2019-08-01T05:32:36.956025600Z" />
    <EventRecordID>2641</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="10152" />
    <Channel>System</Channel>
    <Computer>nc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="NicNameLen">36</Data>
    <Data Name="NicName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
    <Data Name="NicFNameLen">3</Data>
    <Data Name="NicFName">WSL</Data>
    <Data Name="Operation">8</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          01.08.2019 8:32:36
Event ID:      234
Task Category: None
Level:         Information
Keywords:      (128)
User:          SYSTEM
Computer:      nc
Description:
NIC A02CEDA8-C5D8-4D31-8771-08945EDF7CE8 successfully disconnected from port A02CEDA8-C5D8-4D31-8771-08945EDF7CE8.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67dc0d66-3695-47c0-9642-33f76f7bd7ad}" />
    <EventID>234</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000080</Keywords>
    <TimeCreated SystemTime="2019-08-01T05:32:36.955890900Z" />
    <EventRecordID>2640</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="10152" />
    <Channel>System</Channel>
    <Computer>nc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="NicNameLen">36</Data>
    <Data Name="NicName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
    <Data Name="PortNameLen">36</Data>
    <Data Name="PortName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          01.08.2019 8:32:36
Event ID:      233
Task Category: None
Level:         Information
Keywords:      (128)
User:          SYSTEM
Computer:      nc
Description:
The operation 'Delete' succeeded on nic 0D7F979E-6AB7-4B69-82B4-9BC9EA824FE8 (Friendly Name: WSL).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67dc0d66-3695-47c0-9642-33f76f7bd7ad}" />
    <EventID>233</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000080</Keywords>
    <TimeCreated SystemTime="2019-08-01T05:32:36.845094800Z" />
    <EventRecordID>2639</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="10152" />
    <Channel>System</Channel>
    <Computer>nc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="NicNameLen">36</Data>
    <Data Name="NicName">0D7F979E-6AB7-4B69-82B4-9BC9EA824FE8</Data>
    <Data Name="NicFNameLen">3</Data>
    <Data Name="NicFName">WSL</Data>
    <Data Name="Operation">8</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          01.08.2019 8:32:36
Event ID:      234
Task Category: None
Level:         Information
Keywords:      (128)
User:          SYSTEM
Computer:      nc
Description:
NIC 0D7F979E-6AB7-4B69-82B4-9BC9EA824FE8 successfully disconnected from port .
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67dc0d66-3695-47c0-9642-33f76f7bd7ad}" />
    <EventID>234</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000080</Keywords>
    <TimeCreated SystemTime="2019-08-01T05:32:36.104798800Z" />
    <EventRecordID>2638</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="10152" />
    <Channel>System</Channel>
    <Computer>nc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="NicNameLen">36</Data>
    <Data Name="NicName">0D7F979E-6AB7-4B69-82B4-9BC9EA824FE8</Data>
    <Data Name="PortNameLen">1</Data>
    <Data Name="PortName">
    </Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          01.08.2019 8:32:35
Event ID:      232
Task Category: None
Level:         Information
Keywords:      (128)
User:          SYSTEM
Computer:      nc
Description:
NIC 0D7F979E-6AB7-4B69-82B4-9BC9EA824FE8 (Friendly Name: WSL) successfully connected to port 611D7FCC-8F7C-4D8A-B353-249740E3A0C3 (Friendly Name: Container NIC 4190d08a) on switch A02CEDA8-C5D8-4D31-8771-08945EDF7CE8(Friendly Name: WSL).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67dc0d66-3695-47c0-9642-33f76f7bd7ad}" />
    <EventID>232</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000080</Keywords>
    <TimeCreated SystemTime="2019-08-01T05:32:35.919106000Z" />
    <EventRecordID>2637</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="10152" />
    <Channel>System</Channel>
    <Computer>nc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="NicNameLen">36</Data>
    <Data Name="NicName">0D7F979E-6AB7-4B69-82B4-9BC9EA824FE8</Data>
    <Data Name="NicFNameLen">3</Data>
    <Data Name="NicFName">WSL</Data>
    <Data Name="PortNameLen">36</Data>
    <Data Name="PortName">611D7FCC-8F7C-4D8A-B353-249740E3A0C3</Data>
    <Data Name="PortFNameLen">22</Data>
    <Data Name="PortFName">Container NIC 4190d08a</Data>
    <Data Name="SwitchNameLen">36</Data>
    <Data Name="SwitchName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
    <Data Name="SwitchFNameLen">3</Data>
    <Data Name="SwitchFName">WSL</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          01.08.2019 8:32:35
Event ID:      7
Task Category: (1004)
Level:         Information
Keywords:      (128)
User:          SYSTEM
Computer:      nc
Description:
Miniport NIC 0D7F979E-6AB7-4B69-82B4-9BC9EA824FE8 (Friendly Name: WSL) successfully initialized.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67dc0d66-3695-47c0-9642-33f76f7bd7ad}" />
    <EventID>264</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000080</Keywords>
    <TimeCreated SystemTime="2019-08-01T05:32:35.649074800Z" />
    <EventRecordID>2627</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="10152" />
    <Channel>System</Channel>
    <Computer>nc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="PortNameLen">36</Data>
    <Data Name="PortName">611D7FCC-8F7C-4D8A-B353-249740E3A0C3</Data>
    <Data Name="PortFNameLen">22</Data>
    <Data Name="PortFName">Container NIC 4190d08a</Data>
    <Data Name="SwitchNameLen">36</Data>
    <Data Name="SwitchName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
    <Data Name="SwitchFNameLen">3</Data>
    <Data Name="SwitchFName">WSL</Data>
    <Data Name="Flags">1</Data>
    <Data Name="OwnerService">1</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          01.08.2019 8:32:35
Event ID:      9
Task Category: (1005)
Level:         Information
Keywords:      (128)
User:          SYSTEM
Computer:      nc
Description:
Switch A02CEDA8-C5D8-4D31-8771-08945EDF7CE8 (Friendly Name: WSL) successfully initialized.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67dc0d66-3695-47c0-9642-33f76f7bd7ad}" />
    <EventID>9</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>1005</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000080</Keywords>
    <TimeCreated SystemTime="2019-08-01T05:32:35.516909200Z" />
    <EventRecordID>2626</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="10152" />
    <Channel>System</Channel>
    <Computer>nc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="SwitchNameLen">36</Data>
    <Data Name="SwitchName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
    <Data Name="SwitchFNameLen">3</Data>
    <Data Name="SwitchFName">WSL</Data>
    <Data Name="Flags">0</Data>
    <Data Name="OwnerService">1</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          01.08.2019 8:32:35
Event ID:      232
Task Category: None
Level:         Information
Keywords:      (128)
User:          SYSTEM
Computer:      nc
Description:
NIC A02CEDA8-C5D8-4D31-8771-08945EDF7CE8 (Friendly Name: WSL) successfully connected to port A02CEDA8-C5D8-4D31-8771-08945EDF7CE8 (Friendly Name: WSL) on switch A02CEDA8-C5D8-4D31-8771-08945EDF7CE8(Friendly Name: WSL).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67dc0d66-3695-47c0-9642-33f76f7bd7ad}" />
    <EventID>232</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000080</Keywords>
    <TimeCreated SystemTime="2019-08-01T05:32:35.516871100Z" />
    <EventRecordID>2625</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="10152" />
    <Channel>System</Channel>
    <Computer>nc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="NicNameLen">36</Data>
    <Data Name="NicName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
    <Data Name="NicFNameLen">3</Data>
    <Data Name="NicFName">WSL</Data>
    <Data Name="PortNameLen">36</Data>
    <Data Name="PortName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
    <Data Name="PortFNameLen">3</Data>
    <Data Name="PortFName">WSL</Data>
    <Data Name="SwitchNameLen">36</Data>
    <Data Name="SwitchName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
    <Data Name="SwitchFNameLen">3</Data>
    <Data Name="SwitchFName">WSL</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          01.08.2019 8:32:35
Event ID:      233
Task Category: None
Level:         Information
Keywords:      (128)
User:          N/A
Computer:      nc
Description:
The operation 'Create' succeeded on nic A02CEDA8-C5D8-4D31-8771-08945EDF7CE8 (Friendly Name: WSL).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67dc0d66-3695-47c0-9642-33f76f7bd7ad}" />
    <EventID>233</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000080</Keywords>
    <TimeCreated SystemTime="2019-08-01T05:32:35.516864500Z" />
    <EventRecordID>2624</EventRecordID>
    <Correlation />
    <Execution ProcessID="612" ThreadID="10152" />
    <Channel>System</Channel>
    <Computer>nc</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="NicNameLen">36</Data>
    <Data Name="NicName">A02CEDA8-C5D8-4D31-8771-08945EDF7CE8</Data>
    <Data Name="NicFNameLen">3</Data>
    <Data Name="NicFName">WSL</Data>
    <Data Name="Operation">7</Data>
  </EventData>
</Event>

Having the same issue!
Installed Insider Fast ring.
"wsl --set-default-version 2" and then installing Ubuntu gets me the same error.
Reverting it back to default 1 -> Installing Ubuntu and then using "wsl --set-version Ubuntu 2" still gets me the same error..

im stuck also. everything was working fine untill this error showed up and now im unable to get it running again. unregistered, removed the distros and now i cant install them again.
i first noticed something was not OK when i suddenly could not clone a git repo from Ubuntu on Windows. Seems like the whole name resolution was messed up. After a reboot i started getting this error.
any help would be highly appreciated.

So do I . when i convert wsl 1 to wsl2 . the same error while happen. code is 0xffffffff

Same error, after i did a reboot....
PS C:\> wsl --unregister ubuntu
Unregistering...
PS C:\> ubuntu
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0xffffffff
Error: 0xffffffff (null)
Press any key to continue...

I'm having the same issue as @Andy2244  just can't get wsl 2 to work

Has anyone tried wsl --import method with own .tar.gz file?

I'm also seeing this. Started running WSL2, got some Docker containers working. Restarted computer. Now this error on everything related to actions in WSL. Started as starting Ubuntu, then I uninstalled and reinstalled Ubuntu and now I can't convert to wsl2.
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\WINDOWS\system32> wsl -e bash
Error: 0xffffffff

Uninstalled, then reinstalled:
PS C:\WINDOWS\system32> docker -v
Docker version 19.03.1, build 74b1e89
PS C:\WINDOWS\system32> wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-18.04    Running         1
PS C:\WINDOWS\system32> wsl --set-version Ubuntu-18.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
Error: 0xffffffff

I've tried disabling Hyper-v and WSL via Turn Windows features on or off and then re-enabling them but it made no difference

Updating to Build 18956.1000 seems to have resolved the issue, though I have no idea why.

The -1 error indicates an issue creating the virtual network. Those errors tend to be transient.

Updating to Build 18956.1000 seems to have resolved the issue, though I have no idea why.

i can confirm this too, thx for the info!
Attention: In order to get this update you need to use the fast ring.

I am seeing the same issue after rebooting my machine, on build 18956.1000.
wsl --set-version Ubuntu-18.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 Error: 0xffffffff

The -1 error indicates an issue creating the virtual network. Those errors tend to be transient.

I can confirm that I'm seeing the "WSL" switch created and removed in the Hyper-V-VmSwitch logs.
I also see the same behaviour with the Hyper-V Default vSwitch, where I can actually see it appearing and disappearing in Network Connections.
Some searching suggests that this is due to Group Policy blocking Internet Connection Sharing, However I've enabled it manually to see if it is indeed the issue and the adapter device is still being removed.
Is there anywhere where I can find a specific list of configuration requirements for getting the WSL v-switch to work?

I was having this issue then it was solved by upgrading to version 18956 but then after a reboot it's stopped working again with the same error Error: 0xffffffff

I'm not sure if it's what actually sorted my issue but closing the program that was bound (listening) to port 53, allowed WSL to start with no issues

When I stop the program listening to 53 ,and wsl  can finish convert work

Same here, same build (fast preview) WSL 2 and Ubuntu 18 were working fine with Docker WSL 2 Tech preview until this morning.  0xffffffff error, even if I just try a wsl -l -v in PowerShell.

Mine was running fine with build 18956.1000 and ubuntu.
This morning, wsl suddenly stopped working with 0xffffffff error.
Remove and reinstall didn't solve the problem.
$ wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Stopped         2

$ wsl -d ubuntu
Error: 0xffffffff

Open Windows Events log, I saw some messages indicate that create ICS network failed:
Name resolution for the name wpad timed out after none of the configured DNS servers responded.

'IpICSHlpStopDnsServer' : '0x80070490'.

'IpICSHlpStopSharing' : '0x80070490'.

'IpICSHlpStartDnsServer' : '0xFFFFFFFF'.

HNS-Network-Create :-
 Network id = '{b95d0c5e-57d4-412b-b571-18a81a16e005}'.
 Network type = 'ICS'.
  Result code = '0xFFFFFFFF'.

Also on 18956.rs_preselease.190803-1414, same issue as OP, the only thing listening on *:53 is sharedaccess and dockerd. I can't "kill" ICS and the problem persists even when I stop dockerd. The problem starting manifesting itself after a restart (where I switched from Linux to Windows containers) as I wanted to use exclusively try WSL2 docker. After that I can't start a version 2 distro or change version to 2 on any other distro.

@puco I have been racking my brain as to what caused this issue after the restart and yes it was when I switched to Windows containers like yourself. If  I stop docker desktop and the Docker Desktop Service then start WSL I don't get the error.

@scrossan-crown still does not work for me. (Quit Docker Desktop from the tray icon, which stops the VM and then stop docker service). Upgrading distro to WSL2 returns the same error. Did you do anything other (restarting etc.)

@puco the only other thing I do is kill anything listening on port 53 and  then it works for me. Sorry I can't be of more help

Could somebody on build 18956 or later please take a trace?
https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs

@puco @scrossan-crown Thanks to you guys I've found what caused !
What can I confirmed in my case so far:

wsl 2 crash with 0xFFFFFF, which I assume due to I switched docker to Windows container earlier
Switch back to Linux container does not solve the problem.
Stop the Docker Engine Service (not the Docker Desktop Service), I was able to start wsl 2 again, and docker desktop for linux still working
Disable/remove docker engine service, everythings is back as it is before (wsl 2 works along docker desktop for linux)
Switch to Windows container, new config file is created, I am now able to use wsl 2 along with docker for windows

Here is my new config file content:
{
  "registry-mirrors": [],
  "insecure-registries": [],
  "debug": true,
  "experimental": false,
  "hosts": [
    "npipe:////./pipe/docker_engine_windows"
  ]
}

Nice, for me the only thing that helped to change version back to 2 was uninstalling Docker Desktop. Only after that I could upgrade to WSL2, reinstall Docker and have everything running again.

in my case, close the dockerd.exe in the task manager helps.

Closing dockerd.exe and restarting hns service solves the problem for me.

18970 seems to have resolved this issue for me. (docker for windows edge <IP_ADDRESS> (37260))

I got the same error but it seems what I did fixed it:
I'm on Windows 10 Pro Insider Preview 18970.rs_prerelease.190824-1711
I had Ubuntu installed, not Ubuntu 18.04 LTS, so I removed Ubuntu and installed 18.04 LTS:
https://www.microsoft.com/en-us/p/ubuntu-1804-lts/9n9tngvndl3q?activetab=pivot:overviewtab
I switched to Windows container:

Reboot, and then run
PS C:\Users\[username]> wsl --set-version Ubuntu-18.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
Conversion complete.

I don't know if everything's usefull and if it will help someone but ... 💁♂

On build 190824, I had same issue but didn't have docker installed.
Here is the trace.
trace.zip

I got the same error but it seems what I did fixed it:
I'm on Windows 10 Pro Insider Preview 18970.rs_prerelease.190824-1711
I had Ubuntu installed, not Ubuntu 18.04 LTS, so I removed Ubuntu and installed 18.04 LTS:
https://www.microsoft.com/en-us/p/ubuntu-1804-lts/9n9tngvndl3q?activetab=pivot:overviewtab
I switched to Windows container:

Reboot, and then run
PS C:\Users\[username]> wsl --set-version Ubuntu-18.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
Conversion complete.

I don't know if everything's usefull and if it will help someone but ... 💁♂

Works for me !

I got the same error but it seems what I did fixed it:
I'm on Windows 10 Pro Insider Preview 18970.rs_prerelease.190824-1711
I had Ubuntu installed, not Ubuntu 18.04 LTS, so I removed Ubuntu and installed 18.04 LTS:
https://www.microsoft.com/en-us/p/ubuntu-1804-lts/9n9tngvndl3q?activetab=pivot:overviewtab
I switched to Windows container:

Reboot, and then run
PS C:\Users\[username]> wsl --set-version Ubuntu-18.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
Conversion complete.

I don't know if everything's usefull and if it will help someone but ... 💁♂

Works here as well. docker service was using port 53. Stopped that, restarted the ICS service, reinstalled Ubuntu 18.04 in v2, and everything works now, including restarting docker. Changed Docker Engine service to Manual start, hopefully that'll fix it for reboots.

Please do not quote whole post. Just quote some lines which is related to your comment.

Still happening in new 18970.1005.

@puco could you make sure that port 53 is open? Open Resource Monitor > Network > Listening Ports and look for anything bound to port 53, stop it and then try again.
If that doesn't work could you please collect a networking log for us? Instructions on how to do so are here.

@craigloewen-msft no it is not. It is occupied by dockerd, I just wanted to report that the problem is still occurring after the most recent Fast Ring release. The workaround @Sidneys1 posted works for me quite well

Out if curiosity...is the port 53 hijack a permanent feature? Seems like there are a couple different things all trying to use it, and I wouldn't have expected any of those things to be doing so

@Sidneys1 thats work for me on my windows build 18980.1. Thanks!

Out if curiosity...is the port 53 hijack a permanent feature? Seems like there are a couple different things all trying to use it, and I wouldn't have expected any of those things to be doing so

From my possibly naive point of view, ICS can change to only bind to port 53 on the virtual adapter, instead of binding on <IP_ADDRESS>. It probably does it to conveniently support multiple adapters. But the correct approach, I think, would be to bind to each one separately.

I set up a Ubuntu-18.04 distro and Docker WSL 2 Tech View last night and everything was working well. This morning I needed to reboot my PC. Since then WSL reported a 0xffffffff error whenever I tried to launch the distro.
I was able to launch the distro, once I uninstalled docker from the system.
While I was experiencing the issue, Resource Monitor showed two instances of dockerd.exe and one instance of svchost.exe (netsvcs-p) using port 53.  Once I uninstalled docker, only the svchost was using the port.

yep docker is preventing the boot up of Ubuntu, had to switch to linux containers, then launch the wsl terminal, that booted ubuntu, then set docker back to desktop containers, that somehow fixed the issue.

For future users, I was able to install Ubuntu after having this issue.  I stopped the docker service, but that wasn't enough.  I then killed this process in task manager:

I'm not sure if just killing this process is enough. Next person can test that.

This issue just started occurring for me after updating to Windows Insider build 19018. I wasn't able to open WSL or Docker Engine but I was able to perform the below steps to get docker and wsl both running again.

I selected "Reset to Factory Defaults" from the Docker crash notifier.
After Docker Desktop restarts, open Docker Settings and uncheck: Enable the experimental WSL 2 based engine. Click Apply and Restart.
Run "wsl" from a command prompt to confirm WSL is working correctly. Then select "Ubuntu" (or whatever distro you are using) from start menu - confirm the terminal loads and all is well.
Go back to Docker settings, re-check Enable the experimental WSL 2 based engine. Right click the Taskbar icon for Docker Desktop and select "Restart..." to confirm the docker engine is working still.

Note: At this point, I have no idea if this "fix" will stick past a restart or if I'll have to repeat steps 2-4 after each reboot.

Happened to me again. This time I just rebooted, then "Exited" docker desktop, then was able to complete installation of WSL2.  Started docker, started WSL2, all was good (until the next time it randomly breaks again).

For me the 0xffffffff error was fixed by freeing up port 53.

Same as @alexk111, unfortunately though, that's the port that I use for dnscrypt (as Windows 10 still doesn't have support for DoH).
Sucks that there's no way to use both at the same time..?

if you change the startup type of services Docker Engine and Docker Desktop for Delayed, wsl works fine.
But, the application Docker Desktop will try start the service because it is not started yet.

I can confirm @sergiocabral findings: if I close Docker Desktop, wait a bit, and then I can open Ubuntu without any issues.
So this seems to be related to Docker, but I should point I have enabled Windows Containers on my local instance.

I believe this should be fixed in build 19541.
Please let us know if you continue to hit this on the new Insider Fast build.

@benhillis Do you have any details of the fix? Different port, dynamic port, or something else?
I have the same issue with my work laptop that runs Umbrella Roaming Client (from Cisco), and the subprocess "dnscrypt-proxy.exe" that is listening on port 53. The fun part is that since this is security software, I am unable to kill the process and get WSL running again. I'm thinking that all these clashes on the same port is going to be a common issue. At least consider a proper error message in the output from wsl.exe that gives the actual error to the end user.

The fix was fairly deep in the TCP stack. I have given feedback to the team that owns the API that they should improve their failure return codes.

I just hit this on 19041.21

To fix this issue I've just disabled Docker Desktop on system's startup. Simply enough Docker tries to establish a connection to wsl before it is ready and crashes.

I'm getting this in 2004. I don't have Docker/Docker Desktop. Randomly sometimes wsl2 will work, upon reboot, but the majority of times I get:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0xffffffff
Error: 0xffffffff (null)
Press any key to continue...

I also have this issue on Microsoft Windows [Version 10.0.19041.84].
Already uninstalled docker. No changes. Images are working with WSL1 but fail when switching to WSL2.

10.0.19041.172, I also see the WSL vswitch briefly appear when trying to register a distribution.
Docker service was set to disabled + computer restart
Get-Process -Id (Get-NetUDPEndpoint -LocalPort 53).OwningProcess yields two processes listening on UDP 53

dnscrypt-proxy (on IPv6 localhost)
svchost (on <IP_ADDRESS>)

Both services can be stopped, however Internet Connection Sharing (ICS) (SharedAccess) auto-restarts on its own. Even when you disable it through MMC, the service goes back to manual (trigger start) and starts.
Ergo <IP_ADDRESS>:53 stays squatted, so anything WSL2 won't work.

Same as @alexk111, unfortunately though, that's the port that I use for dnscrypt (as Windows 10 still doesn't have support for DoH).
Sucks that there's no way to use both at the same time..?

I found a way to run dnscrypt with WSL2.
Listen a loopback ip except <IP_ADDRESS>, such as <IP_ADDRESS>, then configure your network to use dns service on <IP_ADDRESS>, that means <IP_ADDRESS>:53 is not being used, then you can run WSL2 instance without this problem.

I have done as you've said, rebinding on another address <IP_ADDRESS> but it doesn't solve the problem.
It is possible to work around this by

disabling the vEthernet (Default Switch)
Stop twice the "SharedAccess" (Internet Connection Sharing (ICS)) service
launch the wsl2 distro (SharedAccess will automatically relaunch)

However, the Hyper-V VMs will lose connectivity even after re-enabling the default vSwitch. I will try again after resetting Winsock, but I don't think it will solve anything.

@mchubby
I have tried a new way to solve it. Its rediculous but usable. I create a a V-Switcher for internal networking names 'dnscrypt switcher', bind adapter IP as <IP_ADDRESS>/8. Then create a Hyper-V VM with dynamic memory within 128~384mb，configure 'Default Switch' and 'dnscrypt switcher' on it, then install OpenWRT. Configure eth0(Default Switch) as wan (dhcp client), eth1 as lan, cancel the bridge in br-lan to separate that interfaces, configure lan ip as <IP_ADDRESS>/8, install and configure dnscrypt-proxy2 as its github page says.
Set the VM auto start with system start, and set dns as <IP_ADDRESS>, that works.
I used to use Simple DNSCrypt as it`s memory usage about 70mb, now the 'VM dnscrypt' use about 250mb, not too bad.

The -1 error indicates an issue creating the virtual network. Those errors tend to be transient.

I can confirm that I'm seeing the "WSL" switch created and removed in the Hyper-V-VmSwitch logs.
I also see the same behaviour with the Hyper-V Default vSwitch, where I can actually see it appearing and disappearing in Network Connections.
Some searching suggests that this is due to Group Policy blocking Internet Connection Sharing, However I've enabled it manually to see if it is indeed the issue and the adapter device is still being removed.
Is there anywhere where I can find a specific list of configuration requirements for getting the WSL v-switch to work?
Edit:
I've manually enabled ICS and tested that it works between my LAN and WiFi manually. However the v-switch is still being removed. So scratch that.
v-switch logs: https://pastebin.com/3ReMcxtc
Last edit:
After manually going over basically everything on my laptop, I've eventually found that it was the Acrylic DNS Proxy service I'm using. The service was grabbing port 53 and preventing the ICS service from binding to it.

This solved for me! Ty.

I am on version 2004, 10.0.19041.208 and I am still having the error on trying to convert to wsl2.

I have the same problem with another service.
I have use TCPView to identify witch service was listening on port 53.
After stopping it, WSL 2 was well done.

Same issue started right after I enabled windows containers on 19041.264

For what it is worth, I was having the original problem of FFFFFF error.
How anyone figured out it was a port 53 binding issue I dont know but would like to. But based on those comments in thread I went looking with TCP view and came up empty. Thankfully however being an IT guy I knew that in fact port 53 was in use by Cisco Umbrella Client which is a DNS proxy agent used by Cisco Any Connect VPN on many systems.
I had to stop the following services:

After that it still didnt work by pressing launch to setup the env however uninstall and reinstalling ubuntu from the store then another launch did work!
So what gives with port 53? Why is that important? How did any one figure out that was the problem?

I am having this issue with nothing running on port 53.
The problem happened to me when I upgraded windows 10 to 2004
Any ETA on this issue being resolved?

Build 19041.264, same error
What I tried to do

Changed dnscrypt-proxy from 127.0.01 to <IP_ADDRESS>
Changed startup type from Automatic to Automatic (Delayed)

Same as @alexk111, unfortunately though, that's the port that I use for dnscrypt (as Windows 10 still doesn't have support for DoH).
Sucks that there's no way to use both at the same time..?

I found a way to run dnscrypt with WSL2.
Listen a loopback ip except <IP_ADDRESS>, such as <IP_ADDRESS>, then configure your network to use dns service on <IP_ADDRESS>, that means <IP_ADDRESS>:53 is not being used, then you can run WSL2 instance without this problem.

Does not help

I was getting the same error (0xffffffff) when trying to upgrade my distros and am running Win10 Version 10.0.19041.264 and Docker <IP_ADDRESS> with the WSL2 option selected on install.  I looked at the install guide at WSL Install Guide for Win10 and it had a step to enable the 'Virtual Machine Platform' component (which it said was an optional component).
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
After running the above, it wanted me to restart my machine.    Docker was running and completed the distro upgrade successfully.  The 'Virtual Machine Platform' component was key for me.
Result

I had the same issue, fixed when I found out Acrylic UI was using the port needed for WSL 2. Just in case some of you had this issue and is using that app.

Same issue for me running Cisco (OpenDNS) Umbrella client.  I had to stop the service, uninstall the distro, then get the distro from the store again before it would work.  Curiously, after the first linux distro worked it let me restart the Umbrella service and add other distros with it running, no problem...

This came up for me on the official release when trying to convert a new Ubuntu install to WSL2.
Reading the thread it seems whatever is on port 53 is the problem (often docker it seems, but I don't have that installed).
For anyone else with the same issue you can find out the conflicting program for you running the following in powershell:
netstat -nao | Select-String :53
Then find the item that ends in :53 and note the PID (last column). Put that PID where the zeros are here:
asklist /fi "pid eq 00000"
You now get the program name for what's blocking your wsl 👍
Stop that service and WSL2 will work again.

what helped for me was to disable Hyper-V in the windows feature section.

what helped for me was to disable Hyper-V in the windows feature section.

This worked for me on my work laptop (with Cisco Umbrella and other security stuff on it), but was not necessary on my unencumbered personal machines.

I was going to test out disabling hyper-v and today for whatever reason after another reboot, it all seems to be working happily together - Umbrella, Hyper-V, and WSL 2.  I even did a wsl -l -v to confirm it was really running v2 and not v1.  Nothing changed on my end, no services stopped - could WSL2 be reaching out to MS and they changed some remotely given instruction or is it just an intermittent problem?  So weird...

This just gets stranger and stranger.  Docker Desktop now tries to take 53 as well. So had to change Docker Desktop service to manual to allow WSL enough time to claim 53. I can't express enough to the WSL team you must stop requiring 53 to start. I get why you do it, but its not your port to have.

Eric2XU maybe I am missing it in the discussion above, but I don't understand why they need to claim port 53, even briefly, and I 100% agree with you that it is not theirs to claim.  Would you mind providing a brief explanation or link explaining why they use it?  Thanks!

I "think" it has something to do with being able to redirect http://localhost: requests to docker containers or something like that where in dev testing you can provide a url, WSL/Docker intercepts and provides a hyper-v networking IP instead perhaps. Ill be honest I am not so sure ether.

I resolved this issue by uninstalling Docker Desktop, Hyper-V, and WSL completely.    Then, I put WSL 2 back on alone, following the installation instructions here: https://docs.microsoft.com/en-us/windows/wsl/install-win10.  Everything was fine and my Ubuntu distro was working.  Docker Desktop was working.  I used it for a few days and across several reboots.
Then, I decided I needed to run a few test VMs.  I re-enabled the Hyper-V feature.  After rebooting I'm back to this error again for WSL 2, and I can't access my Ubuntu distro.  Hyper-V is working great, but now I can't do Linux dev the way I want to and Docker is busted.
This is definitely related to dnscrypt-proxy.  Running:
Get-Process -Id (Get-NetUDPEndpoint -LocalPort 53).OwningProcess
Reveals that much.  In my case it is Cisco Umbrella Client is running dnscrypt-proxy under the covers.
Related: bitbeans/SimpleDnsCrypt#500
I added context to that issue as well.

Docker Desktop was using the VM, so I needed to stop the owning processes. The tipp from @petrsnd solved it for me:
Open a new PowerShell console and check the WSL version:
wsl -l -v

  NAME            STATE           VERSION
* Ubuntu-18.04    Running         1

Find the blocking processes:
Get-Process -Id (Get-NetUDPEndpoint -LocalPort 53).OwningProcess

 NPM(K)    PM(M)      WS(M)     CPU(s)      Id  SI ProcessName
 ------    -----      -----     ------      --  -- -----------
     18    26.42      30.45       5.31   16432   0 dockerd
     15    11.11      16.40       0.36    3972   0 svchost

Kill the owning processes:
# replace the IDs with the proper IDs from the last command
Stop-Process -Id 16432 -Force
Stop-Process -Id 3972 -Force

Try again to migrate:
wsl --set-version 'ubuntu-18.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
Conversion complete.

Check again:
wsl -l -v

  NAME            STATE           VERSION
* Ubuntu-18.04    Stopped         2

Restart Docker Desktop at this point and check again:
wsl -l -v

  NAME                   STATE           VERSION
* Ubuntu-18.04           Running         2
  docker-desktop         Running         2
  docker-desktop-data    Running         2

I also have HyperV running a virtual switch, also have Cisco Umbrella client, but don't have Docker.
At the end, I managed to get it working by stopping the "SharedAccess"/Internet Connection Sharing (ICS).  Yes, the service  restarts from itself, but that was enough to be able to reach the screen where I am prompted to choose a new UNIX username.

In my case the problem was solved when closing the DNS Server that was using port 53.
What I don't understand is that port 53 has to do with WSL

I have the same problem because of Cisco Umbrella, and company policy prevents me from killing it, so I'm completely stuck. Is there a planned patch to make this requirement in WSL2 an optional one or should I abandon all hope and move along?

I have the same problem because of Cisco Umbrella, and company policy prevents me from killing it, so I'm completely stuck. Is there a planned patch to make this requirement in WSL2 an optional one or should I abandon all hope and move along?

I am also waiting for the same answer. I depend a lot on my Private DNS Server and I still cannot explain the use that WSL2 gives it so that it asks to close it obligatorily.

For those with Cisco Umbrella RC interference, changing the service startup from Automatic to Automatic (Delayed Start) seems to have resolved the issue for me.

In my case it seemed like there was a conflict between two internal networks on Hyper-V Switch.
One I've created manually earlier for my Virtual Machines and the other created automatically for WSL.
I've simply removed the first one leaving WSL as the only Internal network and problem gone.
The strange thing is that it has been working for some time without any issues and it seems the problem hit me when I first switched my Docker to Windows Containers and then switched back to Linux Containers - after restart WSL couldn't start.
Killing manually processes on port 53 allowed me to start both WSL and Docker but after restart it was failing again, and only removing the other internal network fixed it permanently.

I had the same issue, what solved it for me:
deinstall docker,
deactivating compression as in this workaround https://github.com/microsoft/WSL/issues/4103#issuecomment-501511504 ,
reboot,
uninstall and reinstall Ubuntu Distro
reinstall Docker

I had the same issue,
Solution:--
Install Currports(http://www.nirsoft.net/utils/cports.html#DownloadLinks) and see what is using port 53.
In my case it was acrylicservice.exe
So uninstall/stop those service.

I ran into this issue earlier today when trying to upgrade to WSL2 and get Ubuntu 20.04 LTS working with it.
Based on the advice in moriarity9211's post above, I was able to find the service that was operating on port 53 using this Powershell command: Get-Process -Id (Get-NetTCPConnection -LocalPort 53).OwningProcess
If nothing is running on that port, then Powershell will throw an error. In my case, the offending application turned out to be Cisco AnyConnect VPN Client (which is apparently using dnscrypt-proxy internally). Disabling the Windows service and restarting Windows cleared the port and allowed me to proceed with the Linux distro install (and also to finish installing Docker for Windows with the WSL2 feature).

I have the same issue because I run CoreDNS which used port 53, but If stop CoreDNS and start WSL then start CoreDNS again, then both of them works well

I have had this issue on restart since updating to wsl 2. I have cisco anywhere connect installed but also endpoint security. I have noticed that if I start a ubuntu terminal prior to endpoint starting than I am able to use wsl2 ubuntu image. If not I have to use the workaround posted here https://github.com/microsoft/WSL/issues/4364#issuecomment-638895281.
If I don't get the terminal up before endpoint starts I use the workaround of finding the svchost pid thats using port 53 and force killing it. If I wait to long after force killing it it will start again and block wsl2. If I start the ubuntu terminal as soon as I kill the pid it works and everything works fine. Its annoying but hopefully this workaround will help others.

Same issue here. What fixed the issue in my case was to change the Acrylic DNS port from 53 to 55 in the config using the Acrylic DNS UI.

This can solve this error, and it works well for me
If some application used these ports which WSL need, such as DNS 53, try to start WSL first and then start application in Windows.

Same issue:  Ubuntu says    Error:  0xFFFFFFFF
Press any key to continue
wsl -l -v
NAME                   STATE           VERSION

docker-desktop-data    Stopped         2
docker-desktop         Stopped         2
Ubuntu                 Stopped         2

Windows 10 Enterprise  Version
10.0.19041 Build 19041
I will look at what is bound to port 53 ..

Note, today was the 1st time this issue came up for me...
I did a restart and then  Ubuntu was the 1st app I started and Ubuntu came up..
I am a linux guy so I assume the screen shot of the powershell and proc list shows correctly who is listening on port 53 , ie svchost and and dockerd (17248) listening  :53
Are we sure that it's port :53 that is blocking WSL Ubuntu startup ?

The question still is why are they using a system port ...

I found the listening on the same port problem too. So, I removed Docker as I haven't been using it for a while. Then I stopped the svchost by finding it using the relevant PID for SharedAccess. Right after that, WSL was back.
So, I can confirm it is the same port listening that's causing these problems, @MikeWilcoxMicrosoft.

Technitium's DNS Service runs on the port 53 which will cause errors when trying to use the Ubuntu WSL 2 (failed to install it until I stopped the DnsService).

All DNS software runs on port 53 because is the standard port for that protocol. Anyone that have a DNS server will have problems.

So I've found a way to workaround. (at least worked for me, i don't know why it worked, nor if it would work for everyone else)
Open Task Scheduler,
create a new task, run as system,

then go to trigger, select new, choose at system startup.

then go to actions, add wsl.

then goto conditions and uncheck everything

You should be good to go. Select OK to save it. restart your pc to see the effect.
My setup was Hyper-V enabled, WSL2 enabled, Windows Sandbox enabled, VMware Workstation installed, Docker Desktop installed. I've also installed Proxifier, though unrelated to this issue.

All DNS software runs on port 53 because is the standard port for that protocol. Anyone that have a DNS server will have problems.

Can confirm - DNSCrypt service uses port 53, and has to be killed for WSL 2 to work normally again.

To start docker need to stop may DNS proxy on 53. After it started, start DNS Proxy and may restart docker without a problem. That's weird. Service on 53 should not affect work this way.

I'm using Hyper-V for my personal VM and also for WSL. However, due to the bridge network, Shared Access (ICS, internet connection share) Service running via svchost.exe -k netsvcs -p -s SharedAccess will bind to 53 and cannot unbind due to my personal VM need bridging network.
So I'm so confusing, why are you SO EXCITED TO BIND PORT 53/UDP? Just reuse the local connection DNS should be okay.

I am getting this error every time i have Acrylic DNS proxy running, i'd need the custom domains on windows AND wsl, so i went with it https://mayakron.altervista.org/support/acrylic/Home.htm now not sure how to accomplish the same thing since i need to turn it off then WSL2 works

I can confirm having the same issue. There is a collision of port 53 usage between Acrylic and Windows ICS service (connection sharing) which seems to provide connectivity to WSL2.
Setting Acrylic to different port seems to render it unusable for regular Windows use. Windows only sees it on port 53.
I'm baffled, as I'm sure I had no problem with WSL2 and Acrylic coexisting in the past, on a previous machine. And as my current workflow pretty much requires both to work simultaneously, a solution which could achieve that would be a lifesaver!

I run CoreDNS which use port 53 and cause WSL 2 start failed, use this bat script to start WSL first and start CoreDNS after that, both of them works well, so I think WSL just use port 53 when startup
wsl -e exit
d:\Path\CoreDNS.exe

In my case it seems someone monitoring the ICS (SharedAccess) service, when the ics process killed, it starts again. So I change the service account to a new account, then kill the service process successfully, change the service acount back, try install ubuntu again, and it works.

Up-voting this as it's painful to kill services manually and restart them, ICS indeed keeps binding to DNS port and doesn't allow other programs to run. If anybody has fix with using custom DNS server on same machine, please share!
This issue also appears when trying to convert WSL1 to WSL2 VM, because it creates vEthernet and in order to share connectivity, kernel launches this bridge service.

I fixed the issue with uninstalling Memu android emulator

I have also confirmed that another service, Umbrella Roaming Client, listening on port 53 caused the problems for me too.
After changing the service startup of that service to Automatic (Delayed Start) as suggested in this comment, my issue was resolved

I also experienced this issue __without __ anything listening on port 53.
This time the problem was the LxssManager service not running.

Same problem for me as a result of a company mandated Cisco AnyConnect Secure Mobility Client, with 'Roaming Security' that encrypts DNS queries. I've had to convert my Ubuntu instance back to WSL version 1 in order to use both Cisco AnyConnect and WSL.

Hello. Any ETAs on this?

Same problem for me as a result of a company mandated Cisco AnyConnect Secure Mobility Client, with 'Roaming Security' that encrypts DNS queries. I've had to convert my Ubuntu instance back to WSL version 1 in order to use both Cisco AnyConnect and WSL.

same Issue here.

The work-around to quit processes using port 53 just before launching WSL worked for me, but this also caused DNS to break inside WSL, so it's kind of a painful work-around.

I can confirm this bug, after removing Acrylic DNS Proxy, WSL back agagin.
I need Acrylic DNS Proxy for route all *.test domain to <IP_ADDRESS>, it is easier for my life when do web development. Now, I have to add dns entry one by one to hosts file for this purpose.

Same problem for me as a result of a company mandated Cisco AnyConnect Secure Mobility Client, with 'Roaming Security' that encrypts DNS queries. I've had to convert my Ubuntu instance back to WSL version 1 in order to use both Cisco AnyConnect and WSL.

Same problem here too.

It took me way too long to find that WSL2 is incompatible with Cisco Umbrella's (or any other) DNS proxy starting first. Why is it taking so long to fix this? Add up all the lost productivity of the people just in this thread.

I'm not running anything on port 53 I have checked with netstat, running windows 10 pro-1909 and I get this tried uninstalling hyper-v and WSL several times and I always get this error.

Ran into this blocker issue with Cisco's C:\Program Files (x86)\OpenDNS\Umbrella Roaming Client\dnscrypt-proxy.exe

A year from issue opened, M$FT seems have no indication to trying to solve this problem.

So upgraded windows 10 to 2004 version, set the default to WSL 1, installed Ubuntu tried to convert it to Version 2 and same error I don't know what this is but WSL2 is bugged as hell with networking for some reason, I know because I can change the error if in Hyper-V i create the network adapter WSL it changes the error, but the moment I remove it back to 0xffffffff

Recently upgraded to Cisco Anyconnect SMC v4.9.01095 and this seems to have fixed the issue for me.  I no longer need to disable the Cisco Umbrella service, and I can use WSL2 without any issues.

I have had issues at work with WSL2 because of AnyConnect/Umbrella. Not sure what has changed, but no longer. I can freely convert between wsl1 and 2, have networking with wsl2. Everything works (finally!).
What could have changed? Well, we had updates rolled out to our Cisco suite last week. Also, there were some KBs recently that fixed "issues with wsl" without further description. We also changed our VPN profile to allow access to some local resources like specific printers. In conclusion, too many variables have changed to conclude, but if anyone wants me to check something, just ask.

Recently upgraded to Cisco Anyconnect SMC v4.9.01095 and this seems to have fixed the issue for me. I no longer need to disable the Cisco Umbrella service, and I can use WSL2 without any issues.

I just tried upgraded to 4.9.01095 but still facing the same issue. If I run "get-process -id (Get-NetTCPConnection -localport 53).OwningProcess" it's still bound to dnscrypt-proxy, trying to figure out what's different...

I disabled Hyper-V network adapter and could install Ubuntu-20.04 App, WSL 2 was the default version as I didn't switch to WSL 1.

Here's another data point.  If I log in as "Administrator" on my laptop, I can set the WSL version to 2 via powershell (wsl --set-version Ubuntu-20.04 2).  But if I log in as a regular user, I get the -1 error:
PS C:\Users\bob> 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
Error: 0xffffffff

This looks more like a permissions issue, but I'm not sure how to diagnose further.

Here's another data point. If I log in as "Administrator" on my laptop, I can set the WSL version to 2 via powershell (wsl --set-version Ubuntu-20.04 2). But if I log in as a regular user, I get the -1 error:
PS C:\Users\bob> 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
Error: 0xffffffff

This looks more like a permissions issue, but I'm not sure how to diagnose further.

That's strange because I have tried running the command though PowerShell ni Windows Terminal Running as admin and get the same problem

Got this error just now, might be docker related.

Solved after starting elevated powershell and netcfg -d, restart and it's good again.

Solved after starting elevated powershell and netcfg -d, restart and it's good again.

That did nothing for me, as long as I have Acrylic DNS running from valet-windows, WSL 2 will keep producing a bootup error. If I stop these services I can run WSL with no issues.
This bug/feature has been a show-stopper for me since I prefer to run MySQL, PHP & various other tools on Win and manage using scoop. This is mainly for performance reasons and so that I don't have to run a distro to get MySQL, PHP & Nginx running. I know that on boot all my services are running and I can get to code faster.
I use WSL for the various tools and libraries that don't work so well on Win or simply haven't been ported over and/or the ported versions are watered down. This is now forcing me to stop the very services I am complimenting with WSL and thus rendering WSL almost useless.
With that said I have tried to migrate some of these services to WSL and avoid using valet-windows altogether, even looking for alternative options with no luck. Personally, I think it would be much better time spent on resolving these issues rather than working on getting a file manager GUI on WSL running.

I have also confirmed that another service, Umbrella Roaming Client, listening on port 53 caused the problems for me too.
After changing the service startup of that service to Automatic (Delayed Start) as suggested in this comment, my issue was resolved

That has worked for me for Acrylic DNS also

Is there any solution for this?

I have also confirmed that another service, Umbrella Roaming Client, listening on port 53 caused the problems for me too.
After changing the service startup of that service to Automatic (Delayed Start) as suggested in this comment, my issue was resolved

It worked when i stop my DNS server. (port 53)

Recently upgraded to Cisco Anyconnect SMC v4.9.01095 and this seems to have fixed the issue for me. I no longer need to disable the Cisco Umbrella service, and I can use WSL2 without any issues.

I just tried upgraded to 4.9.01095 but still facing the same issue. If I run "get-process -id (Get-NetTCPConnection -localport 53).OwningProcess" it's still bound to dnscrypt-proxy, trying to figure out what's different...

Admittedly, I think I had already converted my WSL to V2 (while the old Umbrella service was disabled) before I upgraded to the newer Cisco version, but I am able to now run WSL while Umbrella is working.

I have also confirmed that another service, Umbrella Roaming Client, listening on port 53 caused the problems for me too.
After changing the service startup of that service to Automatic (Delayed Start) as suggested in this comment, my issue was resolved

That has worked for me for Acrylic DNS also

@zgjimgjonbalaj Does Acrylic DNS also work after Automatic (Delayed Start)?

@markwu - Meant to update my comment previously but unfortunately no. The delayed start it seems is not some magic solution it simply is delaying the start of the service during windows startup giving you the illusion of WSL 2 working (if you happen to launch WSL 2 before Acrylic does). As soon as that service has started WSL2 will fail again with the same code.
I have not tested other DNS Proxy Servers but managed to get WSL 2 to launch while CoreDNS is also running. There is no automatic implementation with CoreDNS as with Valet & Acrylic but what that confirmed for me there was that there may be an incompatibility with how Acrylic handles its wildcard DNS routing and WSL 2 since a DNS server like CoreDNS seems to work just fine.
This is basically going to turn into a Acrylic/DNS Proxies vs WSL 2, willing to bet we wont get this fixed and have to look to alternate solutions.

@zgjimgjonbalaj Thanks for your detail reply.

I may have been premature with my last post about Cisco 4.9.01095 fixing my problems.  It did seem to fix my WSL starting and upgrading to V2 issues, however, I lose DNS resolution in WSL when connected to the VPN.

I may have been premature with my last post about Cisco 4.9.01095 fixing my problems. It did seem to fix my WSL starting and upgrading to V2 issues, however, I lose DNS resolution in WSL when connected to the VPN.

Yeah it's been hit and miss for me too. Numerous DNS and network issues. I'm using an Ubuntu virtual machine on my laptop for the time being until some of these issues are resolved. I've lost too much time trying to get this working.

Cisco AnyClient 4.9.01095 did not help for me.

I don't know what changed, but in 2004 Pro, build 19041.572 the WSL vSwitch has been created without issue, freshly after PC restart. UDP 53 is still in use by SharedAccess and both WSL and Hyper-V work along.
Recent applied hotfixes are:

KB4579311 (2020-10 CU)
KB4576478 (.NET CU)
KB4571756 (2020-09 hybrid security/quality CU)
KB4566782 (2020-08 CU)
KB4569745 (.NET CU)
KB4570334 (SSU)

error events still get logged in H-N-S, but everything seems to work nonetheless. Quite stumped about it.

DO THIS WORKED FOR ME: -
netstat -a -b
finds out which process is listening on a port on Windows
then with Task manager KILL the process running on ::53 (port 53 usually ArcylicDNS...)
then start wsl

DO THIS WORKED FOR ME: -
netstat -a -b
finds out which process is listening on a port on Windows
then with Task manager KILL the process running on ::53 (port 53 usually ArcylicDNS...)
then start wsl

Here's how you can use Acrylic DNS with Docker for Win and WSL2

Change Acrylic DNS Configuration to stop listening on port 53.
WSL2 will not run if port 53 is not free!!

I have used port 54 in my setup.
In Acrylic DNS add a wildcard domain of your choice to route to <IP_ADDRESS>

I am using local in my setup so [anything].local will always route to localhost.
Go to Network and Sharing Center > Change Adapter Settings
Right Click on your Network and select Properties
Make sure your IPV4 DNS settings match this

Make sure your IPV6 DNS settings match this

Verify both Acrylic DNS and Docker Desktop are running and bound to the correct ports
Get-NetUDPEndpoint | Where {$_.LocalPort -eq "53"} | select LocalAddress,LocalPort,@{Name="Process";Expression={(Get-Process -Id $_.OwningProcess).ProcessName}}
Get-NetUDPEndpoint | Where {$_.LocalPort -eq "54"} | select LocalAddress,LocalPort,@{Name="Process";Expression={(Get-Process -Id $_.OwningProcess).ProcessName}}

Verify DNS resolution works fine

The trick here is running Acrylic (or any other  DNS proxy server) over  IPV6 which WSL2 does not bind to.
Alternatively, if you are able to make the DNSClient query a custom DNS port other than 53, or use a different protocol other than UDP for DNS queries you should be able to use a local DNS proxy alongside WSL2.

Here's how you can use Acrylic DNS with Docker for Win and WSL2

Change Acrylic DNS Configuration to stop listening on port 53.
WSL2 will not run if port 53 is not free!!

I have used port 54 in my setup.
In Acrylic DNS add a wildcard domain of your choice to route to <IP_ADDRESS>

I am using local in my setup so [anything].local will always route to localhost.
Go to Network and Sharing Center > Change Adapter Settings
Right Click on your Network and select Properties
Make sure your IPV4 DNS settings match this

Make sure your IPV6 DNS settings match this

Verify both Acrylic DNS and Docker Desktop are running and bound to the correct ports
Get-NetUDPEndpoint | Where {$_.LocalPort -eq "53"} | select LocalAddress,LocalPort,@{Name="Process";Expression={(Get-Process -Id $_.OwningProcess).ProcessName}}
Get-NetUDPEndpoint | Where {$_.LocalPort -eq "54"} | select LocalAddress,LocalPort,@{Name="Process";Expression={(Get-Process -Id $_.OwningProcess).ProcessName}}

Verify DNS resolution works fine

The trick here is running Acrylic (or any other  DNS proxy server) over  IPV6 which WSL2 does not bind to.
Alternatively, if you are able to make the DNSClient query a custom DNS port other than 53, or use a different protocol other than UDP for DNS queries you should be able to use a local DNS proxy alongside WSL2.

My problem was with the Technitium DNS Server, after stopping the service the issue was gone.

DO THIS WORKED FOR ME: -
netstat -a -b
finds out which process is listening on a port on Windows
then with Task manager KILL the process running on ::53 (port 53 usually ArcylicDNS...)
then start wsl

I had error  0xffffffff, and your advise really help ;
Stop ArcylicDNS  Servrice, and porblem sovled;

@jawabuu that kills the DNS resolution, DNS leak tests fail.

Hey @VPraharsha03 Could you share your nslookup results as in the image I posted?

I have the same error. Nothing on port 53:
get-process -id (Get-NetTCPConnection -localport 53).OwningProcess
Get-NetTCPConnection : No MSFT_NetTCPConnection objects found with property 'LocalPort' equal to '53'.  Verify the

value of the property and retry.
get-netadapter|where-object {$_.interfacedescription -like "*hyper-v*"} comes back empty.
The event log only has successful messsages from Hyper V:
The operation 'Create' succeeded on nic 318A01AF-D321-4B67-918B-3C22697D8154 (Friendly Name: WSL).
NIC 318A01AF-D321-4B67-918B-3C22697D8154 (Friendly Name: WSL) successfully connected to port 318A01AF-D321-4B67-918B-3C22697D8154 (Friendly Name: WSL) on switch 318A01AF-D321-4B67-918B-3C22697D8154(Friendly Name: WSL).
.... snip
The operation 'Delete' succeeded on nic 318A01AF-D321-4B67-918B-3C22697D8154 (Friendly Name: WSL).

Tried a netstat -d and rebooted. I closed anyconnect and openvpn. WSL1 is fine.

I can't see any word from Microsoft on this issue?  I have the error consistently, but netstat -d from an elevated command prompt and then reboot is so far working for me.   The Cisco AnyConnect I have seems to now particular effect, good or bad.

@jawabuu Sorry for posting very late, i'd been trying to disable ICS and was wrong. Because the ICS listens on port 53 and also WSL requires it to be running (https://github.com/microsoft/WSL/issues/6646#issue-824861101) an easy solution would be making the start of the DNS server delayed (allowing WSL to listen first) by setting it's startup type to Automatic (Delayed) or keeping the ICS stopped at windows startup and it starts on it's own later
Making DNSCrypt listen to a different port kills the resolution and i don't have support for IPV6

I was able to get AcrylicDNS and WSL2 working together by changing:
LocalIPv4BindingAddress=<IP_ADDRESS>
to
LocalIPv4BindingAddress=<IP_ADDRESS>
I think otherwise Acrylic tries to bind to the vEthernet (WSL) interface?

@jamieburchell

I think otherwise Acrylic tries to bind to the vEthernet (WSL) interface?

From the Acrylic DNS config file:
;
; The local IPv4 address to which Acrylic binds. A value of <IP_ADDRESS> indicates that Acrylic should bind to all available
; addresses and as such it will be able to receive DNS requests coming from all of your network interfaces. A value
; corresponding to the IPv4 address of one of your network interfaces instead will allow Acrylic to receive DNS requests
; only from that specific network interface. An empty value instead indicates that no binding should occur on IPv4.
;
LocalIPv4BindingAddress=<IP_ADDRESS>

From the Acrylic DNS config file:
;
; The local IPv4 address to which Acrylic binds. A value of <IP_ADDRESS> indicates that Acrylic should bind to all available
; addresses and as such it will be able to receive DNS requests coming from all of your network interfaces. A value
; corresponding to the IPv4 address of one of your network interfaces instead will allow Acrylic to receive DNS requests
; only from that specific network interface. An empty value instead indicates that no binding should occur on IPv4.
;
LocalIPv4BindingAddress=<IP_ADDRESS>

Yes, this is what makes me think that it clobbers and causes issue with the vEthernet (WSL) interface. I don't know what interface <IP_ADDRESS> belongs to, but it works.

Wow thank you I came here because om installed  Acrylic DNS

@jamieburchell thanks dude changing the LocalIPv4BindingAddress=<IP_ADDRESS> worked for me!

I deinstalled Acrylic but the service was still there and running after reboot - so also check that.

Very NOT cool for a service to be uninstalled and have the service still remain there on the system!  What is that? Is it some kind of malware packaged as a DNS proxy service? If not, it sure is acting like malware!
To get rid of it after uninstallation, one can disable the service in Services, or fire up an administrative command prompt and run:
SC DELETE [SERVICE NAME]
Substitute the actual name of the service for [SERVICE NAME]. If you are running PowerShell, type cmd in PowerShell before running the command.

For me it was Acrylic DNS Proxy which was binded on UDP Port 53.
Did netstat -anob didn't get program information there but got PID of the process.
Opened Task Manager and pasted PID, Voila. Killed the process and game on for WSL2.
Hello Ubuntu !

after reboot i use wsl --update and again wsl --install -d Ubuntu and it work for me


Integration with docker/distribution web hooks

Notary needs to be able to receive push notifications (specifically from docker/distribution for the moment), to perform actions such as purging trust information when a docker repository is deleted.

This isn't going to happen. In the cases where it has been required, it has been the responsibility of a 3rd service to manage the dependency between the registry and notary.


feat: use kanal instead of futures::channel

kanal is faster but create a async kanal channel is expensive, the oneshot kanal channal is still WIP.
more details can be found here (Add Oneshot implementation)

kanal should be used in a unstable feature

Only tokio has implemented a broadcast channel.


Look for moment on the global object

In Node, moment is loaded via the 'global' object instead of the 'window' object. This change checks which object moment is loaded on, and uses the appropriate object.
Fixes the following issue: https://github.com/urish/angular-moment/issues/79

Hi, thanks for the contribution!
Please apply the global patch at line 561 instead.

Hi urish, no problem - this should now be fixed.

Thanks!

Released as 0.10.2


minutiae matching

I have one more question. if we want to match minutiaes in two fingerprints, how can we align and match them? i have read fingerprint handbook but i couldnt understand

check these papers:
http://biometrics.cse.msu.edu/Publications/Fingerprint/JainHongBolle_OnlineFPVerification_PAMI.pdf
You need to find point correspondences. Here are papers which may be useful:

http://citeseerx.ist.psu.edu/viewdoc/download?doi=<IP_ADDRESS>.4660&rep=rep1&type=pdf
http://citeseerx.ist.psu.edu/viewdoc/download?doi=<IP_ADDRESS>.5382&rep=rep1&type=pdf


Problems with PUT and POST

Hi there,
I am doing PUT "/photos/3" but CRUD wont work, its not updating values on DB.

Result is "OK" but I get old values.

Have you tried ->expectPostData() on the resource? By default it's expecting a json body.
See: https://github.com/redound/phalcon-rest/blob/master/src/PhalconRest/Api/Collection.php#L202,  https://phalcon-rest.redound.org/resources.html

Yes, sorry I didn't mention it but I changed to expectPostData ()... But I tried to send json data before modifying the code and  I got same result that's why I changed to expectPostData but without success.
Thanks

@riveraser Ok, I currently don't have time to help you out. But I would suggest you debug what's happening, maybe your server doesn't have post data enabled in some way. If the error is caused by the library just do a pull request and I will try to merge it asap. If you have questions about the library just ask.

Hi Olivera,
I will use "RAW" and "application/javascript" tu POST or PUT data:
When sending POST (Create) everything is fine if I do "->expectsPostData()" and select "form-data" to send values...
But when I select PUT (Modify) the "body" is not send in "form-data" format but in "x-www-form-urlencoded"....
So I will standardize in RAW json...
Thanks you can close the issue now if you want


New screen definition

Sorry, I'm not getting along with github very well yet, so I don't want to make any pull requests or merges.
It would be great if you look at my suggestion and hopefully  include it in the project.
I took up Trenar's good idea and implemented the power on/off function for the Sunfounder HDMI display via optocoupler.
In this context the following 'files' were created:

New screen definition file
Shell Skript from Trenar adapted to my individual configuration
Circuit diagram
Board layout
Datasheet optocoupler
Two Photos

I also noticed that the wiringpi extension used in the script needs to be updated on the Raspberry Pi 4 first.
This may need to be included in the installer script and works as follows:
cd /tmp
wget https://project-downloads.drogon.net/wiringpi-latest.deb
sudo dpkg -i wiringpi-latest.deb

Screen definition Sunfounder 10.1 hdmi display.zip

Hi @sohamakl, nice to see you working on this.
At first I want to mention #2 to let people see our recent discussion :)
It may be confusing for people that you call pin 29 in the shell script but use 21 in circuit diagram (at least it was for me). So let me attach this link to clarify the pinout used by wiringpi / the gpio utility.
How do you feel about having the gpio mode XX out line not in the screen_switch.sh script but as the cmdInit of the screen config? However I feel like both solutions are not ideal, best would be an additional config parameter and a fallback pin number.
Shouldn't the wiringpi core be update when running sudo apt update && sudo apt upgrade? I think this is done anyhow at some point of the installer script.
Last comment: The image of the optocoupler wiring is very blurry.
I could prepare a pull request once I find time for it.

Sorry, I'm not getting along with github very well yet, so I don't want to make any pull requests or merges.
It would be great if you look at my suggestion and hopefully include it in the project.
I took up Trenar's good idea and implemented the power on/off function for the Sunfounder HDMI display via optocoupler.
In this context the following 'files' were created:

New screen definition file
Shell Skript from Trenar adapted to my individual configuration
Circuit diagram
Board layout
Datasheet optocoupler
Two Photos

I also noticed that the wiringpi extension used in the script needs to be updated on the Raspberry Pi 4 first.
This may need to be included in the installer script and works as follows:
cd /tmp
wget https://project-downloads.drogon.net/wiringpi-latest.deb
sudo dpkg -i wiringpi-latest.deb

Screen definition Sunfounder 10.1 hdmi display.zip

Hi @Trenar,
moving the gpio definition to the config file is a very good idea.
I will take some new and better photos when I back home on Sunday.
I had to update wiringpi manually. I also read on the developer's website that he does not want to support future versions of Raspberry Pi.

Hi,
I played around a little.. Moving the Pin param to the config is imho not feasible, since the config parameters are not accessible where the screen config file is loaded. Therefore, I added a variable in the screen config file which has to be set manually. For now I set it to your default pin 29.
See PR #94 and please test it, just to be on the save side :)

I took three more photos with bit better quality than before.

Looks good. However I think we don't need to upload these images to the git, but instead refer to this conversation at some point, maybe in the screens/README.md of #97

Good idea, could you be so kind and add it to screens/README.md? I really need to learn how to use Github, sorry.

@gegu will do so :)

I think this would be a classic case for a page in the wiki. where we can link to.
Just someone would have to dare to create the first page 😏

My English is not perfect and I don't know how to use a wiki on github yet.
But it seems to be a good start to write a little how-to on the topic "Hardware extension for time-controlled on/off switching of the Sunfounder 10.1 inch HDMI touch display".
If you agree, I would take it over.
Who can give me the necessary rights?

you should be able to edit the wiki now.


Add Elevation / Lenses - Highly Detailed -> Leadership View

Feature Name : Elevations - Standardized levels of detail
Is your feature request related to a problem? Please describe.
Convert raw data into information consumable by different audiences to support Business Cases, Design, Operations, Financials
Describe the feature you'd like to see implemented
The ability to change your perspective / elevation from the 10' (or 10m) level to the 100000' (or meter) level to accommodate different audiences. Examples:

Leadership - 100K' Elevation - Identify Cloud/VPC/Instance/Storage resources at a very course level and map to applications/URL's
Designer/Architecture - 20K' Elevation - Identify Leadership items but increased details to include connectivity. Include DNS/IP/Operating System Details
Engineer/Dev OPs - 10' Elevation, all of the gory details.

Then business centric

Compliance Elevation
Security Elevation
Billing Elevation

Describe the value this feature will add to AWS Perspective
Increases audience for the data.  Permits usage of the data by leadership to create new AWS business. Use for business case justification / support of AWS servers and IT services.

We've evaluated this request and added it to our backlog but it is not prioritised in the immediate roadmap for the solution.


Remove UserAccountCreator class

UserAccountCreator class is tightly coupled to UserCreation model. It probably adds an unnecessary layer and its logic might be added to UserCreation.

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Question: Advice for Application Insights reporter

I'm looking for an advice regarding implementation of a reporter to Microsoft Azure Application Insights.
Relevant Microsoft documentation

If you are implementing your own pre-aggregation logic, you can use the Track(ITelemetry metricTelemetry) method to send the resulting aggregates.

This looks to me exactly what needs to be done as App.Metrics are doing their own aggregation, so it boils down to translating *ValueSource types from MetricsContextValueSource in the reporter to MetricTelemetry instances.
Simplified Application Insights DTO for publishing metrics aggregated on client side (pseudo-code):
MetricTelemetry
{
    double Sum,
    double? Max,
    double? Min,
    int? Count,
}

original MetricTelemetry
Questions:

Is there a way how to get min, max and stdev in sources which do not seem to expose them (MeterValue, ApdexValue)?
In what situations the collections MeterValue.SetItem[] Items and CounterValue.SetItem[] Items would have something in them (so far I've seen them always empty)?

Meters and Apdex metric types in App Metrics don't calculate these values.

If I'm not mistaken the property which allows resetting a metric after reporting is only available in CounterOptions and ApdexOptions. What is the reasoning for it not being available for example on histogram? (Where it seem to me would be most useful as statistics such as min, max, stddev are really not that interesting in a cumulative scope - i.e. minimal value ever recorded.)

I already have a working implementation of the reporter. Would you be interested in PR into App.Metrics and if so, do you have any PR guidelines?
The link for contributing in README.md seems to be broken at the moment.

Cool. I'd prefer that to be a community driven repo outside of App.Metrics. Interested in having a look and happy to have it included in the documentation.

I'd be interested in your opinion on this implementation.
I have pointed out some outstanding issues in README.md which are simply a result of two metric frameworks / abstractions having different opinions here and there. Nothing major I think, so at this point it looks usable to me.

LGTM

LGTM

That's quite an interesting tool. I've had no idea something like that exists. Default setting generates quite a lot false positives for C# code, but I guess that would be easy to tune by per project lgtm.yml. Thanks for the tip.

I've just realized you've probably meant "Looks Good To Me" and I've accidentally discovered this https://lgtm.com - a code analysis tool that can be easily integrated into GitHub (or used without it).

Released RC1 (pre-release channel).
I'm closing this ticket.


Restructure webhook parsing

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@0563d7a). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2221   +/-   ##
=======================================
  Coverage        ?   40.80%
=======================================
  Files           ?      182
  Lines           ?    10897
  Branches        ?        0
=======================================
  Hits            ?     4446
  Misses          ?     6110
  Partials        ?      341

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@anbraten well yes they look obvious but you better write them down to not have them "refactored out" in the future ...
this regression happened because of a refactor and an enhancement ... witch obviously did not had this in mind

and a refactor simply has to have a look at the numbers ... well and if it's not accounted it's a pull thats wrong and will get rejected untill it's right

->  #2222