Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x80070142
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
### Windows Version
Microsoft Windows [Version 10.0.26100.4202]
### WSL Version
2.5.7.0
### Are you using WSL 1 or WSL 2?
- [x] WSL 2
- [ ] WSL 1
### Kernel Version
n/a
### Distro Version
n/a
### Other Software
Trying to start wsl from the command line fails with the bug title. Docker Desktop also fails to start with the following message >>
```
_deploying WSL2 distributions
provisioning docker WSL distros: ensuring main distro is deployed: checking if main distro is up to date: checking main distro bootstrap version: getting main distro bootstrap version: open \\wsl$\docker-desktop\etc\wsl_bootstrap_version: The specified network name is no longer available.
checking if isocache exists: CreateFile \\wsl$\docker-desktop-data\isocache\: The network name cannot be found._
```
### Repro Steps
Update to Win 11 Pro to version 24H2 via Windows Update!
### Expected Behavior
WSL (and by extension Docker to still work)
### Actual Behavior
Both WSL and Docker (by dependency fail to start)
```
> wsl
The target device has insufficient resources to complete the operation.
Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x80070142
```
and
```
deploying WSL2 distributions
provisioning docker WSL distros: ensuring main distro is deployed: checking if main distro is up to date: checking main distro bootstrap version: getting main distro bootstrap version: open \\wsl$\docker-desktop\etc\wsl_bootstrap_version: The specified network name is no longer available.
checking if isocache exists: CreateFile \\wsl$\docker-desktop-data\isocache\: The network name cannot be found.
```
### Diagnostic Logs
_No response_
Contributor guide
Research direction
Start by reproducing the failure with the `wsl` command after the Windows 11 24H2 update, then compare the WSL error with Docker Desktop's deployment logs. No repository file or test is identified in the issue; done would mean WSL starts successfully and Docker Desktop can deploy its WSL2 distributions without the reported network or resource errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100