Blue

@YousefTurky: It's looking like the Hyper-V socket provider isn't available on your machine. I can see it being referenced under `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Catalog_Before_Reset\Catalog_Entries\00000000000` (which looks like a registry backup), but it's not...

The easiest way would be to restore the content of `Protocol_Catalog_Before_Reset`, but I don't know who / what create that key in the first place, that would be for you...

Unfortunately the error message most likely indicates that the hvsocket protocol provider is incorrectly configured. WinSock working with TCP/IP is unrelated to hvsockets so that doesn't say much. One thing...

Unfortunately I don't have deep knowledge of that registry key either. I think your best bet would be to look at the registry on a working machine or VM, and...

If going through the registry isn't an option, then the OS reset is probably your best bet. To answer your question, if a user or a program specifically modifies the...

Could you share /logs of this ?

Thank you @YousefTurky. Looking through the logs, it's looking like there's an old MSIX registration that's causing some issues. What do you get if you run `get-appxpackage -AllUsers | Where-Object...

Hmm, so it's looking like the MSIX installation is completely failing to install the WSLInstallerService. let's try something else. Does manually installing [the latest MSI release](https://github.com/microsoft/WSL/releases/download/2.6.1/wsl.2.6.1.0.x64.msi) solve the issue ?

Weird. Was the MSI package installation successful ?

Ok interesting. Could you share the content of `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WSLService` in regedit ?