Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureGpu/HCS/0x80041001

[Niviral]

Windows Version

Microsoft Windows [Version 10.0.22635.2776]

WSL Version

2.0.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

I have turned Hyper-v features off as I found out that it is not required in WIN11
Error Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureGpu/HCS/0x80041001 started to occur
turnedt Hyper-v features on, error still exist

Expected Behavior

Wsl starting correctly

Actual Behavior

Error: 0x80041001
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureGpu/HCS/0x80041001
Press any key to continue...

[process exited with code 4294967295 (0xffffffff)]

Diagnostic Logs

WslLogs-2023-12-13_19-11-38.zip

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002 (#9016), similarity score: 0.93
• Error code: Wsl/Service/CreateInstance/CreateVm/HCS/E_INVALIDARG (#10285), similarity score: 0.93
• Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424 (#10778), similarity score: 0.93

Closed similar issues:

• Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x80070032 (#10809), similarity score: 0.97
• Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002 (#9845), similarity score: 0.93

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[OneBlue]

Thank you @Niviral. Looking at the logs, it looks like the VM triple faulted:

317	True	Microsoft.Windows.HyperV.Worker	VmTripleFault	0	12-13-2023 10:11:50.872	"	"	"Cr3: 	0x3DDC000
Cr4: 	0x20
Cr8: 	0x0
Cs: 	0x0
Ds: 	0x0
Es: 	0x0
Fs: 	0x0
Gdtr: 	0x0
Gs: 	0x0
HvMessageType: 	0xFFFFFFFF80000021
Idtr: 	0xFFFF000000000000
Ldtr: 	0x0
Rip: 	0x100026D
Ss: 	0x0
Tr: 	0x0
VmId: 	{b34cd835-8550-41c8-8a73-29c6b3d6d5bb}"				19344	30072	2		00000000-0000-0000-0000-000000000000		

Let me see if I can find a way to gather more information on the crash.

[glichten]

Hey @OneBlue I'm running into the same issue, but never saw a follow up comment from above. Any chance you can take a look at my log dump and extract any info as how to proceed? I'd prefer not to have to re-install, but that seems like the only choice I've got at this point, as I've tried all combinations of disabling wsl/virtualization features, rebooting, & re-enabling.
WslLogs-2024-06-25_17-05-50.zip

[glichten]

As a follow on, I updated the .wslconfig file with the below block, and now I instead receive the error Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x80041001 so it appears that the issue exists regardless of the gpu being used or not. If you could point me to what I should be looking at within the logs, I'd be happy to dig through and see if I can find anything further.

gpuSupport=false

[glichten]

As a follow on, I updated the .wslconfig file with the below block, and now I instead receive the error Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x80041001 so it appears that the issue exists regardless of the gpu being used or not. Attached are the latest set of logs.

[wsl2]
gpuSupport=false

Digging through them, I still see the following error which really doesn't provide me with much additional data. 'Virtual Machine' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID 3147E7F6-70BF-477E-95FE-ECCD9739518B)
I also attempted an inplace re-install with the current build of windows I have, and still no luck. So any help you could provide @OneBlue would be extremely helpful.

WslLogs-2024-06-26_16-46-40.zip

[glichten]

Closing the loop here for anyone else that might be unlucky enough to run into this scenario, and this might help. Turn out all I had to do was run a wsl --uninstall and then run wsl and it cleaned up/fixed whatever was going on.