{Application Error} The application was unable to start correctly (0x%lx). Click OK to close the application. Error code: Wsl/Service/CreateInstance/CreateVm/0x8007023f

[lanyuer]

Version

Microsoft Version [10.0.22000.856]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.15.57.1

Distro Version

Ubuntu-20.04

Other Software

No response

Repro Steps

Cannot reboot wsl2, it tells:

{Application Error} The application was unable to start correctly (0x%lx). Click OK to close the application.
Error code: Wsl/Service/CreateInstance/CreateVm/0x8007023f

Expected Behavior

Should be started successful

Actual Behavior

Diagnostic Logs

WslLogs-2022-09-07_13-53-08.zip

[lanyuer]

Processing fstab with mount -a failed.

<3>WSL (8) ERROR: CreateProcessEntryCommon:346: getpwuid(0) failed 2
<3>WSL (8) ERROR: CreateProcessEntryCommon:350: getpwuid(0) failed 2
<3>WSL (8) ERROR: CreateProcessEntryCommon:523: execvpe /bin/sh failed 2
<3>WSL (8) ERROR: CreateProcessEntryCommon:532: Create process not expected to return

[nlundquist]

I am also experiencing this bug.

[LikeGhost]

Processing fstab with mount -a failed.

<3>WSL (8) ERROR: CreateProcessEntryCommon:346: getpwuid(0) failed 2 <3>WSL (8) ERROR: CreateProcessEntryCommon:350: getpwuid(0) failed 2 <3>WSL (8) ERROR: CreateProcessEntryCommon:523: execvpe /bin/sh failed 2 <3>WSL (8) ERROR: CreateProcessEntryCommon:532: Create process not expected to return

Have you solved the problem?
Maybe you can help me .

[LikeGhost]

Processing fstab with mount -a failed.

<3>WSL (8) ERROR: CreateProcessEntryCommon:346: getpwuid(0) failed 2 <3>WSL (8) ERROR: CreateProcessEntryCommon:350: getpwuid(0) failed 2 <3>WSL (8) ERROR: CreateProcessEntryCommon:523: execvpe /bin/sh failed 2 <3>WSL (8) ERROR: CreateProcessEntryCommon:532: Create process not expected to return

Maybe you can set the default wsl to ubuntu or other system you needed by using the order wsl --set-default <Name>.
Because you may use the docker based wsl and the docker for windows has set the defalut wsl as docker-desktop-data.
You can use wsl --list to check.
I got the message from the other issue #5923.
I hope it was helpful for you!

[lanyuer]

I reinstalled the system finally...

[LikeGhost]

OK，I'm sorry I couldn't help you

[eternalphane]

As stated in #8750, this issue seems to be fixed in 22H2. However, I can't upgrade to this version since a safeguard hold is on my device. A temporary workaround would be to backup C:\Windows\System32\wsl.exe and make a cmd wrapper for C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\wsl.exe.

[caiqi]

Same problem here. wsl --set-default <Name> works.

Processing fstab with mount -a failed.
<3>WSL (8) ERROR: CreateProcessEntryCommon:346: getpwuid(0) failed 2 <3>WSL (8) ERROR: CreateProcessEntryCommon:350: getpwuid(0) failed 2 <3>WSL (8) ERROR: CreateProcessEntryCommon:523: execvpe /bin/sh failed 2 <3>WSL (8) ERROR: CreateProcessEntryCommon:532: Create process not expected to return

Maybe you can set the default wsl to ubuntu or other system you needed by using the order wsl --set-default <Name>. Because you may use the docker based wsl and the docker for windows has set the defalut wsl as docker-desktop-data. You can use wsl --list to check. I got the message from the other issue #5923. I hope it was helpful for you!

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!