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)
@Joshua-IRT 's
or
wsl --updatemay 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
wsl --updateThis 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.
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-downloadI can confirm that installing the 4.17.1 version of Docker Desktop solved the problem for me too, after uninstalling the previous version.
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 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 bashworks but notwsl. 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.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 --updateworked for me as wellWhen I trying
wsl.exe --update, the update process shows error as well:but manually downloading and installation via this link actually fixed my problem. Thanks!