WSL2 is failing to attach the wsl virtual disk and giving error code 4294967295

[yunusparvezkhan]

Windows Version

Windows 11 Evaluation Copy

WSL Version

1.3.15

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.90.4-1

Distro Version

Ubuntu

Other Software

No response

Repro Steps

1. Launch Computer
2. Start WSL2 in terminal
3. Error pops up

Expected Behavior

The terminal usually boots up within 10 seconds.

Actual Behavior

Instead the linux did not boot up at all and thrown an error, as follows,

Failed to attach disk 'C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_1.3.15.0_x64__8wekyb3d8bbwe\system.vhd' to WSL2: The request is not supported.
Error code: Wsl/Service/CreateInstance/CreateVm/MountVhd/HCS/0x80070032

[process exited with code 4294967295 (0xffffffff)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

Diagnostic Logs

No response

[yunusparvezkhan]

Now after running

netsh winsock reset

from administrator powershell, as suggested by some folks in #5092
and restarting the computer, wsl2 gives a new error message with the same error code on bootup.

The error looks like,

Element not found.
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureGpu/HCS/ERROR_NOT_FOUND

[process exited with code 4294967295 (0xffffffff)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

[yunusparvezkhan]

After running

netsh winsock reset

from administrator PowerShell and restarting the computer multiple times, the problem got solved and wsl2 successfully booted it. My issue is resolved, but still looking forward to an explanation of what caused the issue.

[raiyan22]

After running

netsh winsock reset

from administrator PowerShell and restarting the computer multiple times, the problem got solved and wsl2 successfully booted it. My issue is resolved, but still looking forward to an explanation of what caused the issue.

this helped me start the wsl.

[adelenelai]

can confirm the above solved same problem for me.

On Windows,
Run Terminal as Admin
run netsh winsock reset
Reboot

[j-a-y-s-o-n]

Had the same problem.

Just restarted wsl from task manager and re-access again on terminal solved the issue for me.

[fharper]

None of the previous solution worked for me, but uninstalling WSL + WSL updates and reinstalling did it for me.

[cyy280113999]

After running

netsh winsock reset

from administrator PowerShell and restarting the computer multiple times, the problem got solved and wsl2 successfully booted it. My issue is resolved, but still looking forward to an explanation of what caused the issue.

works

[pluma]

Thanks for this. I got nervous after getting this error after a Windows crash fearing the file got corrupted but after running this in an admin terminal and rebooting everything works properly again.