Error code: Wsl/Service/CreateInstance/0x80040326 when starting WSL Distro (again)

[fr3nch13]

Windows Version

Microsoft Windows [Version 10.0.19045.2965]

WSL Version

1.2.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.90.1

Distro Version

Ubuntu 22.04

Other Software

VS Code with WSL extension (though this happens without even using VS Code)

Repro Steps

Any of these

> ubuntu
> wsl

Expected Behavior

Launch ubuntu

Actual Behavior

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

Relates to Error code: Wsl/Service/CreateInstance/0x80040326 when starting WSL Distro #9867

Only the wsl --update doesn't seem to fix my issue.

Diagnostic Logs

Submitting through Feedback Hub.

[fr3nch13]

Version info:

>wsl -v
WSL version: 1.2.5.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
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.2965

[chrstn14]

same problem came here over night as well. Using WSL1.

>wsl -v
WSL-Version: 1.2.5.0
Kernelversion: 5.15.90.1
WSLg-Version: 1.0.51
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.3086

[Rom1deTroyes]

I believe I'm in the same situation :

Error: 0x80040326
Error code: Wsl/Service/0x80040326

[processus terminé avec le code 4294967295 (0xffffffff)]

From Powershell (admin)

PS C:\Users\romain> wsl -v
Version WSL : 1.1.3.0
Version du noyau : 5.15.90.1
Version WSLg : 1.0.49
Version MSRDC : 1.2.3770
Version direct3D : 1.608.2-61064218
Version de DXCore : 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
version Windows : 10.0.19045.2965

PS C:\Users\romain> wsl --shutdown
PS C:\Users\romain> wsl --update
Recherche des mises à jour.
Error: 0x8024500c
Error code: Wsl/UpdatePackage/0x8024500c

WSL is a nightmare to deal with.

[fr3nch13]

I had to completely uninstall wsl, disable the Linux features and reboot, before starting from scratch in order to get it working again.

[DMDTT]

Uninstalling WSL, Reboot, Installing, Reboot didn't fix the issue for me :-/

WSL-Version: 1.2.5.0
Kernelversion: 5.15.90.1
WSLg-Version: 1.0.51
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.3086

[fr3nch13]

There seems to be something tied to whether the windows store is allowed or not. -------------On Jun 25, 2023, at 9:57 PM, DMDTT ***@***.***> wrote: Uninstalling WSL, Reboot, Installing, Reboot didn't fix the issue for me :-/ —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[DMDTT]

Indeed! Our company blocked the store!

[fr3nch13]

Also check to see if windows updates are either blocked or the option is turned off and managed by your company. It also seems to have something to do with it. On Jun 26, 2023, at 9:22 AM, DMDTT ***@***.***> wrote: Indeed! Our company blocked the store! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[DMDTT]

I'll check! Thx!

[OneBlue]

Thanks for reporting this @fr3nch13. Can you share either the zip file with the logs or the Feedback Hub link so we can have a look ?

/logs

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

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 scipt will output the path of the log file once done.

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

Click here for more info on logging

Thank you!

[fr3nch13]

I wish I could. It’s a work laptop, so the Feedback hub is disabled, and I’m pretty sure it’s against policy to share logs, even to MS without going through some channel. Suffice it to say that I know that when corporate pushed changes that require a reboot, it breaks almost every time, and they have no idea why. On Jun 27, 2023, at 2:56 PM, microsoft-github-policy-service[bot] ***@***.***> wrote: Hello! Could you please provide more logs to help us better diagnose your issue? 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 scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging Thank you! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[OneBlue]

Unfortunately we'll need logs to diagnose the issue. If you can't share them, maybe someone else on this issue could ?

[chrstn14]

Unfortunately we'll need logs to diagnose the issue. If you can't share them, maybe someone else on this issue could ?

@OneBlue I had the same issue and collected the logs as described. Hope you can find the error. Thanks in advance.
WslLogs-2023-06-28_08-43-19.zip

[DMDTT]

Unfortunately I cannot provide any logs, cause the powershell restrictions by my company won't let me execute

Set-ExecutionPolicy Bypass -Scope Process -Force

so, all my hopes are with you and with the logs of @chrstn14

[OneBlue]

@OneBlue I had the same issue and collected the logs as described. Hope you can find the error. Thanks in advance.

Thank you @chrstn14. Looking at the logs, it looks like a WSL1 distribution is failing to start, but I don't see any distribution installed. Are you trying to install a distro ?

Just to validate, does this reproduce with all distros ? Does let's say wsl --install -d debian work ?

[chrstn14]

Thanks for your response, @OneBlue

Currently there are three installed distributions. The error occurs starting any of them.

wsl --list -v
  NAME            STATE           VERSION
* Ubuntu-20.04    Stopped         1
  Arch            Stopped         2
  Debian          Stopped         2

I just ran wsl --install -d debian to reinstall it:

wsl --install -d debian
Debian GNU/Linux ist bereits installiert.
Debian GNU/Linux wird gestartet...
Error: 0x80040326
Error code: Wsl/Service/CreateInstance/0x80040326
Press any key to continue...

Hope this answers your question.

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!

[chrstn14]

This problem still exists. The issue has been automatically closed. @fr3nch13 , are you - as the author - able to reopen this issue? I am not able to. :-(

@OneBlue Can I provide additional information for you for debugging purposes? Thanks a lot.

[fr3nch13]

@chrstn14 sure, I’ll see if I can.

Update: um not seeing the option to reopen via the web and app for the phone. I’ll try the desktop web when I can. @OneBlue can you reopen it?

[Bulmenisaurus]

Hitting keys at random on my keyboard led me to type wsl --update --web-download into powershell which seemed to resolve this issue for me.

[chrstn14]

Hitting keys at random on my keyboard led me to type wsl --update --web-download into powershell which seemed to resolve this issue for me.

I already tried that, thanks. Unfortunately that didn't fix it.