Error code: Wsl/Service/CreateInstance/CreateVm/HCS/E_INVALIDARG

[brenol]

Windows Version

Microsoft Windows [Version 10.0.25905.1000]

WSL Version

1.3.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Got from wsl --version: 5.15.90.2-3

Distro Version

Ubuntu 18.04

Other Software

No response

Repro Steps

Starting WSL causes the error.

Expected Behavior

WSL runs normally

Actual Behavior

WSL doesn't start, and errors out when running wsl -d Ubuntu-18.04

Was on 1.25, tried updating to latest & to a old version, unfortunately didn't fix.

Diagnostic Logs

WslLogs-2023-07-13_09-37-04.zip

[mengxunlingxue]

I also met the same problem

[sirredbeard]

This is a known issue in the most recent Canary build. A fix is in progress for an upcoming build.

[tyingq]

This is a known issue in the most recent Canary build. A fix is in progress for an upcoming build.

Is there a way to revert to a working configuration?

[sirredbeard]

@tyingq If you have not cleaned up the previous build, you may be able to roll back to the previous build, in Settings->System->Recovery. I would then disable Windows Insiders updates until the next Canary build arrives.

[brenol]

Thank you @sirredbeard . Unfortunately my Windows restore point is pointing to the version updated today, which is the same canary version (10.0.25905.1000). Is there any other way (perhaps changing channels in Windows Update) to change the version?

Edit - for anyone that has the same issue with Windows restore - I still had Windows.old on my drive.
Restarted Windows while pressing Shift, (spammed F8) to be in the Recovery screen. Was clicking around and found a option to 'Uninstall new version of Windows' (or something like that).

It gives you two options - uninstall Quality or uninstall Feature update. Clicked on Uninstall Feature and it rolled back to 25393 and it's now working.

Had to do that because the Recovery option in the Settings application was crashing for me on 10.0.25905.1000.

[tyingq]

@sirredbeard Appreciate that. I can now confirm that rolling it back gets WSL working again.

[benhillis]

Thanks for posting, unfortunately the fix for this issue just missed the insider build snap. I would suggest rolling back to the previous Insider build until a new one is released.

[joeabbey]

Attempting to rollback as well.

[ChuixiongWu]

Unfortunately, my computer's backup point is also in this version (10.0.25905.1000). And in recovery mode, I also didn't find any updates that could be removed. So I had to wait for the new version.
Does anyone know when the new WSL available version will be released?

[duberlyguarnizofuentesrivera]

Same problem! Machine was asking to reboot to update... I ignored a problem was to happen, now I must write my code in my Linux laptop. Would this be a priority fix for the MS team?

[udithaMee]

Same problem, I have No Windows restore point so the workaround is impossible too. learning to live without WSL
The network name cannot be found.
Error code: Wsl/0x80070043
[process exited with code 4294967295 (0xffffffff)]

[nprasad2077]

@tyingq If you have not cleaned up the previous build, you may be able to roll back to the previous build, in Settings->System->Recovery. I would then disable Windows Insiders updates until the next Canary build arrives.

Can confirm that this solution worked for me. I did not have to change any BIOS options or windows features. I just restored the previous build of windows and WSL is working on login. 😀

[AndPuQing]

I rolling windows back gets WSL working again.

[moekhalil]

Rolling back now, sadly after a very long install...
Quite surprised that the likely very large set of users who are on AMD and use WSL2, even on Canary, can be provided with a broken WSL after install.
Especially since it's been over a month since the last Windows Update...

[moekhalil]

Sorry for the double comment. ^{(Not editing previous comment in order to ensure people watching this thread receive this message in their email.)}

I installed this update manually via the ISO after noticing a new build on Flight-Hub but not on my Windows Update. Taking a look at the blog post, I now see something that if I had seen earlier, would of stopped me from installing.

Known issues

[NEW] This build will not be offered to some ASUS devices or PCs with ASUS motherboards due to an issue causing a bugcheck when attempting to update to this build.

[NEW] Ethernet-connected devices may lose network connectivity after updating to this build. Unplugging the ethernet cable and re-plugging the cable in should resolve the issue.

I am on an Asus Motherboard, AND did have the ethernet issue.

For anyone already in this thread or that stumbles upon it after, if you have suffered this problem, can you please select the appropriate emoji options on this comment in order help inform of what could be root cause.

SELECT TWO OPTIONS (EMOJIS):

ONE FROM 👇	AND    ONE FROM 👇
😄 : Manual Install	☹️ : AMD and ASUS Motherboard
🎉: Auto Install	❤️ : AMD and Non-ASUS Motherboard
	🚀 : Non-AMD and ASUS Motherboard
	👀 : Non-AMD nor ASUS Motherboard

ASCII ART VERSION 😄 

      __________________________________________________________
     /=========================================================/\
    /                                                         //\\
   /=========================================================// \|\
  /             SELECT ONE FROM EACH COLUMN                 // /\/
 |----------------------|----------------------------------|/ /\/|
 /  Installation Method |           System Type             \/ / |
/_______________________|____________________________________\/| |
 | 😄: Manual Install  | 😄 : AMD and ASUS Motherboard     | / |//
 | 🎉: Auto Install    | 💖 : AMD and Non-ASUS Motherboard | | |/-----//
 |                     | 🚀 : Non-AMD and ASUS Motherboard | |//      /
 |                     | 👀 : Non-AMD nor ASUS Motherboard | //      //
 |_____________________|____________________________________//-------/
 /                     /                                   /
/    ONE FROM 👆      /                 ONE FROM 👆       /
\---------------------------------------------------------/

[Cr4z33]

Rolling back now, sadly after a very long install... Quite surprised that the likely very large set of users who are on AMD and use WSL2, even on Canary, can be provided with a broken WSL after install. Especially since it's been over a month since the last Windows Update...

I don't know you, but I got latest update (automatically) applied only like 2 weeks ago. 🤷🏽‍♂️

[paulomanrique]

This is a Windows issue with virtualization, not WSL. I use an Android emulator called Memu that also breaks with that Insider release.

[udithaMee]

After install
Version 23H2
Installed on ‎7/‎27/‎2023
OS build 25915.1000
Experience Windows Feature Experience Pack 1000.25915.1000.0
update today everything works and the bug fixed,Thanks Microsoft team

[GPMrks]

Thanks a bunch @udithaMee for the feedback about the build 25915. I've just updated my OS Build and I can confirm my WSL is working just fine now. It's curious that they didn't mention anything about the WSL bug fix in their windows insider log, but ok. Hahaha. Thanks Microsoft team.

[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!