WSL2 distro failing to startup with code 4294967295

[bitcrazed]

• Your Windows build number: (Type ver at a Windows Command Prompt)
  19609

• 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.)
  Was browsing my Ubuntu WSL2 instance's filesystem using the new File Explorer WSL distro integration

• What's wrong / what should be happening instead:
  Suddenly, File Explorer could no longer connect to the distro.

Then tried connecting to distro via Windows Terminal, but got:

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
[process exited with code 4294967295]

Can no longer access my Ubuntu WSL distro at all.

• For WSL launch issues, please collect detailed logs.
  Logs attached.
  wsl2-start-issue.zip

[therealkenc]

#4364 #4929

I have the same issue with the file manager, but I can still access my distro. Same build also, I did submit this to feedback hub also.

[holazt]

Solve "process exited with code 4294967295" , run netsh winsock reset as Administrator, then reboot your computer.
The result like below:

❯ netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

[kaevans]

Solve "process exited with code 4294967295" , run netsh winsock reset as Administrator, then reboot your computer.
The result like below:

❯ netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

Does not resolve the issue.

Stopping Hyper-V service from Hyper-V manager app solved this issue.

[kaevans]

I had a customer's VPN client installed on my machine (Cisco AnyConnect VPN), the customer's installation package also installed dnscrypt. Uninstalling this has resolved the issue on my machine, confirming other threads that indicate the issue is usually related to network issues... particularly port 53.

[leizhilong]

Solve "process exited with code 4294967295" , run netsh winsock reset as Administrator, then reboot your computer.
The result like below:

❯ netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

works for me, Thanks

[larson-carter]

I'm having this issue in a variety of situations.

1.) I'm just working and I close the terminal or ubuntu. Then I'm locked out of it
2.) I have my computer running for more than 36 hours then it does this? It could be coincidental however it is unlikely. Please not I'm not checking directly at 36 hours. It's just an estimate

Nothing fixes it. None of the above stuff mentioned has fixed it, neither have any other forum pages.

The only solution for me is to leave my PC running and every few hours to come back and check to see if it's fixed or still broken.

[forecho]

#4904 (comment)

[larson-carter]

@forecho That does not fix it.

[truealex81]

I just tried to open vhdx file in C:\Users\TrueAlex\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu20.04onWindows_79rhkp1fndgsc\LocalState
and my Ubuntu isn't working anymore :( even after reboot.

[KazeZlat]

WSL2 works fine on 19640, but fails with same code on 19645. I already had my WSL2 set up, but this update failed it. Checking for updates on 19645 resulted in nothing, even though release notes mentioned we should get kernel with Windows Update.

Had to roll back to 19640 for now.

[truealex81]

I'm solved this with:

DISM /online /disable-feature /featurename:VirtualMachinePlatform /norestart
DISM /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart

Reboot, and then:

DISM /online /enable-feature /featurename:VirtualMachinePlatform /norestart
DISM /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart