WSL: Error: 0x80040326 when opening WSL

Windows Version

Win 11 22621.1413

WSL Version

1.1.3.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.90.1

Distro Version

22.04

Other Software

No response

Repro Steps

Repro steps:

  • Start window
  • Wait few minutes
  • Try to access wsl

I received an “Error: 0x80040326” when attempting to open WSL on Windows 11. This error appears after I have opened several WSL tabs and have been working with them for a while. When I try to open a new tab, the error appears in the Command Prompt or PowerShell, while the old WSL tabs still work normally.

However, when I open a new terminal tab in VSCode, everything works normally. This issue only occurs with WSL tabs opened in the Command Prompt or PowerShell.

Therefore, I am seeking the support of experts to identify the cause of this issue and provide a solution. My Windows 11 version is up-to-date, and I am using WSL2.

Expected Behavior

Can open wsl without error

Actual Behavior

It throw error

Error: 0x80040326
Error code: Wsl/Service/0x80040326
Press any key to continue...

Diagnostic Logs

No response

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 8
  • Comments: 40 (4 by maintainers)

Most upvoted comments

@Joshua-IRT 's

Forced an update check in the Microsoft Store and an update for WSL appeared.

or

wsl --update

may resolve this issue.

Forced an update check in the Microsoft Store and an update for WSL appeared.

Problem is resolved with this version:

WSL version: 1.1.6.0 Kernel version: 5.15.90.1 WSLg version: 1.0.50 MSRDC version: 1.2.3770 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2728

  • Open the Windows PowerShell
  • wsl --update

This solves my issue. The same thread here: https://github.com/microsoft/WSL/issues/9867

Restart the computer and immediately execute “wsl–update” on powershell. After that, my problem was solved

wsl --update

Can confirm wsl --update has fixed this issue atm.

try downloading from this https://github.com/microsoft/WSL/releases/download/1.1.6/Microsoft.WSL_1.1.6.0_x64_ARM64.msixbundle and update

When I trying wsl.exe --update, the update process shows error as well:

Error: 0x80d03805
Error code: Wsl/UpdatePackage/0x80d03805

but manually downloading and installation via this link actually fixed my problem. Thanks!

This error could happen when your sysadmin blocks windows store. To avoid a manual download, you can use the web-download option: wsl --update --web-download

I can confirm that installing the 4.17.1 version of Docker Desktop solved the problem for me too, after uninstalling the previous version.

Super curious as to what caused this (and how many developer hours were lost today 😄)

Too many to count I’m afraid 😭

@SogoKato I also installed the latest Docker Version (4.17.1), I had to manually kill the docker service process beforehand though to make it work. It now seems to work again 🚀

Super curious as to what caused this (and how many developer hours were lost today 😄)

I’m having the same exact problem, no matter what I do (purge data, factory reset, manually delete docker related folder), Docker Desktop is stuck showing the “Docker Desktop starting…” message until it crashes. Has anyone found the cause of this?

I also had this issue. Re-install docker desktop using the latest installer (4.17.1) worked for me. Before re-installing, I was using a little old version (4.6). No uninstallation was needed.

I had this same issue after downgrading from 1.1.6 to 1.1.5. The command wsl bash works but not wsl. Didn’t have any issues with docker but version 1.1.6 has issues where it cannot bind to ports as described in issue #9763.

Did wsl --update, this fixed WSL for me but completely broke Docker for Desktop on Windows? How is this even possible?

Docker is unable to start now due to a

Docker.Engines.WSL2.WSL2ErrorFoundInLogsException:
Error found in logs indicating startup will most likely fail: Error creating 000-metadata: exit status 1

This error also persists when disabling the WSL2 integration in Docker, and I can’t start Docker for Desktop on Windows anymore. WSL2 now works fine, but no docker.

It’s quite curious, everything was working fine yesterday, shutting off the computer, turning it back on ~8 hours later and WSL was broken, without any update from my side.

I’m having the same exact problem, no matter what I do (purge data, factory reset, manually delete docker related folder), Docker Desktop is stuck showing the “Docker Desktop starting…” message until it crashes. Has anyone found the cause of this?

wsl --update worked for me as well

try downloading from this https://github.com/microsoft/WSL/releases/download/1.1.6/Microsoft.WSL_1.1.6.0_x64_ARM64.msixbundle and update

When I trying wsl.exe --update, the update process shows error as well:

Error: 0x80d03805
Error code: Wsl/UpdatePackage/0x80d03805

but manually downloading and installation via this link actually fixed my problem. Thanks!