WSL start-up attempts fail (time-out / -1 / exited 4294967295 / 0x80370109)

[maxboone]

Windows Build Number

Microsoft Windows [Version 10.0.22458.1000]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.10.43

Distro Version

Debian 10, Ubuntu 20.04 LTS, Fedora, any

Other Software

No response

Repro Steps

• Start system
• Open Linux-session (either through Windows Terminal, WSL -d distro -e /bin/sh, or anything else)
• See it time-out

Expected Behavior

Open a shell

Actual Behavior

The operation timed out because a response was not received from the virtual machine or container.
[process exited with code 4294967295]

Trying to add a new OS to see if it's an fs-related problem:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370109
Error: 0x80370109 The operation timed out because a response was not received from the virtual machine or container.

Press any key to continue...

Diagnostic Logs

Uploaded to Feedback Hub => https://aka.ms/AAdtxrl

[maxboone]

Steps that didn't help:

• Disabling & re-enabling the features
• Uninstalling both wslg & kernel updates from software center and installing them using wsl --update
• Running netcfg -d
• Installing & registering a new distro (same error occurs)
• Invoking WSL with the -e flag to specify it to start /bin/sh
• Don't have anything running on port 53
• Restarting several services, LxssManager, vmcompute, SharedAccess
• Repairing system image with sfc /scannow and dism /Online /Cleanup-Image /RestoreHealth
• Setting a $WINDOWS_HOME/.wslconfig

I don't have the vmsmp service (even after above steps) which I saw in another issue - could that be related - as I don't have vEthernet switches either in my Device Manager (hidden devices & set devmgr_show_nonpresent_devices=1 turned on)

As this kinda feels like a networking issue I thought this to be relevant possibly.

[maxboone]

Running the debug console doesn't help either, it just shows the following on failure:

WSL has terminated, press any key to continue...

[maxboone]

VmSwitch-Logging.zip

Event Logs don't show anything interesting either, on the VmSwitch, I guess it never makes it to that stage :(

[benhillis]

/dupe #5194

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!