Error : Wsl/Service/CreateInstance/CreateVm/HCS/0x80070142 after upgrading to Win11 24H2

[pquiring]

Windows Version

Microsoft Windows [Version 10.0.26100.1742]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

All

Other Software

none

Repro Steps

wsl

Expected Behavior

Get bash prompt.

Actual Behavior

The target device has insufficient resources to complete the operation.
Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x80070142

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Open similar issues:

• Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureGpu/HCS/0x80041001 (#10917), similarity score: 0.80
• Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x8007000d (#12042), similarity score: 0.79

Closed similar issues:

• Since update to windows 24H2 Error code: Wsl/Service/CreateInstance/0xd0000022 (#11630), similarity score: 0.81
• Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x80070032 (#10809), similarity score: 0.78
• WSL2 is failing to attach the wsl virtual disk and giving error code 4294967295 (#10390), similarity score: 0.78

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

[pquiring]

Uploading WslLogs-2024-10-02_10-12-41.zip…

[pquiring]

Tried to uninstall and reinstall - no change. (took an unusual long time to do that).

[pquiring]

Unable to start a VM in Hyper-V : same error code.

[pquiring]

Just for comparison, VirtualBox is working fine. So not a hardware issue.

[OneBlue]

@pquiring: The above link doesn't actually point to logs.

/logs

[pquiring]

WslLogs-2024-10-02_10-12-41.zip

[github-actions]

Diagnostic information

Appx package is not installed
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/HCS/0x80070142

[OneBlue]

Thank you @pquiring. I wonder if the limitation is coming from CPU cores.

Can you try writing:

[wsl2]
processors=1
memory=1GB
nestedVirtualization=false

To %USERPROFILE%/.wslconfig and collect /logs if that fails again ?

[pquiring]

WslLogs-2024-10-02_20-04-16.zip

.wslconfig had no effect.

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.3.24.0

[pquiring]

Found this in event log:
Virtual machine '' cannot be started on this server. The virtual machine NUMA topology requirements cannot be satisfied by the server NUMA topology. Try to use the server NUMA topology, or enable NUMA spanning. (Virtual machine ID A879800A-4440-4534-BBBD-6BE6A106AAE6).

[pquiring]

Fixed it!
Enabled NUMA spanning in HyperV management and then restarted all HyperV services.

[Nate-Mina]

Fixed it! Enabled NUMA spanning in HyperV management and then restarted all HyperV services.

thanks i had same issue this was the only help