Error Wsl/Service/CreateInstance/0xd000020c with code 4294967295 (0xffffffff) #11255
Comments
|
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
|
|
I had already seen some of the links proposed by the bot, but abyways none of them is helpful for me. |
|
I've been using WSL Ubuntu successfully for years, but as of this morning it fails with the above error. "wsl.exe --status" reports no problem. |
|
I have not used WSL in a month on this machine, but if was working fine last time I checked. This is what I get: |
|
Following. I have the same exact issue. I use WSL (ubuntu) periodically, at least once a week if no more. It used to work without any issues, but since today I'm also getting the "Wsl/Service/CreateInstance/0xd000020c" error. |
|
Thanks for your patience, everybody. We've been unable to reproduce this locally, but I have some additional steps that will help us debug this. Could you please set the below reg key, then re-run log collection? This will put the lxcore driver into verbose logging mode which should help identify why init is falling over.
|
|
rollback to lower version or try the command: |
|
I faced this yesterday, I have no clue what is going on here, It was working fine until yesterday. I'm just a "advanced user" I did fully reset WSL, DISM, SFC. System restore didn't help either but it seems to have crashed yesterday with some windows updates... KB5034848 The weird thing is that Docker seems to be working normally by the way |
|
also had the same, docker was not working till I switched docker to use wsl2 for me the problem started yesterday, but my update history says my last update was installed on 15/02, the only update I had yesterday were some windows defender rules |
|
Same issue here since today with WSL 2.1.4.0 on Win10 22H2 (10.0.19045.4046), last MS updates were installed on Feb 28th. Edit: on my machine only Ubuntu-18.04 on WSL1 made troubles - after migrating the distribution to WSL2 (via |
|
Ok, I gave up. I ended up disabling WSL 1 (ubuntu 18) and installing WSL 2 Ubuntu 22.04. |
|
Did a "wsl --update", tried to start "wsl"; the error in question came up: "Error code: Wsl/Service/CreateInstance/0xd000020c" |
same here. No way to use WSL1 anymore |
|
Same here. I was in an active WSL1 session that suddenly died. I go have a look in the Store app -- Windows Subsystem for Linux showing "Modified minutes ago" Rude! |
Can you share the link with us? By the way, did anyone try wsl --install --enable-wsl1 ? |
|
I'm still looking for an updated trace with these instructions, could one of you please share with me? |
|
@DesktopECHO - thank you, to confirm you set the below reg key prior to starting the trace? I'm not seeing any more traces. You may actually need to restart after setting that key. Could you try that? |
|
I set the registry key, but I did not restart. Not near this box right now, will have to pick this back up later today. |
|
@benhillis I followed your instructions and produced the attached logs. Hope they help! |
|
Happens with WSL1 Kali Linux but not with WSL1 Ubuntu 20.04. |
@benhillis Here are the results of the log script with the reg key set: Some important (and puzzling) things to mention:
According to several users, the bug appeared close to yesterday, and may be due to a recent update of WSL. I hope this can be quickly fixed.
This is what I get with the command you suggested: |
|
@dashqua - thanks! It looks like you have two different distros, a WSL1 and a WSL2. The WSL2 is working and the WSL1 is not. Unfortunately the reg key is not causing any more logging to show up for WSL1, so I suspect the init user mode process is just crashing very early. I have a theory about what might be happening, but I would need somebody with a repro to try out a private version of the WSL msi to test. Let me know if anybody is open to that and I can coordinate with you. Thanks for the help! Once we sort out what's wrong we'll get this added to our test matrix so this doesn't happen again... |
|
@benhillis Happy to see that you take the problem seriously. I have to admit I did not understand all the jargon you employed, but I understand you need a volunteer to experiment something before coming back to me. I just want to make sure the issue is solved and my data is intact. |
|
So this one worked for me after unregistering every wsl1 distro You may try it with a registered distro wsl --install --enable-wsl1 |
|
I've been using WSL for years without ever running into anything like this, but I ran into this same problem this morning. I eventually worked around it by essentially uninstalling and re-installing. I was already on WSL2, and I'm still on it after the workaround. Not sure if there is anything new here that I have, in that it seems most of the frustration in the comments above are people who were using WSL1 and are now being forced to move to WSL2. That said, if anyone else was frustrated by this in the wsl2 world, here is what I did: followed by: |
|
@wjristow - we're working on resolving this ASAP, sorry for the frustration. I want to advise people to avoid doing what you suggest though since it will result in data loss. We hope to have this resolved here shortly. |
|
Ahhh, thanks for the update and warning @benhillis ! I did lose some environment/setup things using the approach I described, and I wish that hadn't happened. I hope I haven't lost anything more. |
|
I just experienced this issue as well. I was using my WSL2 Ubuntu this morning, but when I came back after lunch it won't start. |
@benhillis Do you still someone to test this? I would be open to do so. |
|
@firewave - if you're down to try a few private MSI's shoot me an email, it would really help! My address is . |
|
To everybody joining the thread: please provide as much info as you can. You can get the powershell log script above, and I also encourage you to attach screenshots to second your post. Hopefully, with a growing number of users reporting problems, a fix may appear soon! |
|
I have the same error on Ubuntu 20.04 + WSL 1. Ubuntu 22.04 + WSL 1 is working.
Happy to run diagnostics if that will help resolve the problem. Here is some information: On my primary machine (fips enabled) where 20.04, wsl-1 is failing: WSL version: 2.1.4.0 On a second machine (not fips) where 20.04, wsl-1 works: WSL version: 2.0.9.0 |
|
I had the same problem with a Debian distro that uses WSL1. Installing 2.0.15 fixed it. I also tried 2.1.0, 2.1.1, and 2.1.3 but they all failed the same as 2.1.4 I can try to get some logs if you don't already have enough of them to inspect. |
|
I too needed to downgrade to the last stable release msi on this GitHub project (2.0.14) from 2.1.4 installed by the Microsoft Store automatically (Windows 10 Pro 22H2) to get my Debian distro on WSL1 working again. Seems like 2.1.x introduced a regression. |
Can you give us the commands you used? Also, did you witness any data loss? |
|
FWIW, the procedure I used to downgrade/test various versions was
2.0.15 worked; others in the 2.1 series immediately failed with 0xd000020c. There was no data loss as far as I can tell. Debian has been behaving the same as before since the downgrade. |
@MitchBradley Thanks for your detailed answer. I have followed EXACTLY what you suggested (took the 2.0.15 release) and I am happy to tell you that I recovered my WSL session. My problem seems resolved. I let this thred open in case the developpers want to say something. Also, people are welcome to give explanation about what's happening with WSL. Cheers |
Just wanted to say, I was having the same problem and this fixed it for me. Thanks a bunch! |
Lifesaver! This fixed it for me at the moment |
|
I have a working theory but I would need somebody who's able to repro this to try a private version of WSL. Is anybody able to assist? |
|
If you can give me an msi or some such I will test it, especially if you give me good instructions for what you want me to do. I am a software developer so I won't need much handholding, but mostly I do embedded stuff so I don't live and breathe Windows arcana. |
|
@MitchBradley - awesome, that would be greatly appreciated. If you could shoot me an email I'll send you the binary. |
|
Email sent |
|
I'll also happily test tomorrow when I'm working from the home office
(where I run WSL). I'll send you an email as well!
I may have really messed my machine up though, as I aborted unregistering
my Ubuntu instance halfway through when I panicked about potentially losing
data.
Den mån 11 mars 2024 18:16Ben Hillis ***@***.***> skrev:
… @MitchBradley <https:/MitchBradley> - awesome, that would be
greatly appreciated. If you could shoot me an email I'll send you the
binary.
benhill (at) microsoft (dot) com
—
Reply to this email directly, view it on GitHub
<#11255 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/ABFRA2VFUKEBLHPMWUCSOGTYXXYGJAVCNFSM6AAAAABEJT4T52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBZGAYDAOJXHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Thanks for your patience everyone, this was a tricky one but @OneBlue and I were finally able to get a repro locally. I have a fix for this and will roll out an updated WSL package ASAP. Sorry for the disruption this caused. |
|
Tricky ones are fun after the fact. Good job. |
|
Fixed with https:/microsoft/WSL/releases/tag/2.1.5. Sorry again for the pain here - I will introduce a test to make sure something like this can't happen again. |
|
Fix confirmed. Thanks. |
How could this be fixed when the latest commit on any branch happened 5 days ago? |
|
@electrofloat the code is not in this repo. WSL is not open source |
|
Ahh... microsoft... What was I thinking... |
|
2.1.5 fixed both my machines, thanks for the quick turnaround! |
|
Glad this helped a lot of users... Though this version broke my WSL when I had no issues it seems...
|
|
I have started getting this same error on 2.2.4.0 of WSL 1 Downgrading to 2.1.5.0 or 2.0.15.0 didn't help |
and others
Windows Version
Microsoft Windows [Version 10.0.22631.3235]
WSL Version
2.1.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
CYGWIN_NT-10.0-22631 version 3.4.5-1.x86_64 (runneradmin@fv-az420-156) (gcc version 11.3.0 (GCC) ) 2023-01-19 19:09 UTC
Distro Version
Ubuntu-22.04
Other Software
No response
Repro Steps
I believe the command of the shortcut is C:\WINDOWS\system32\wsl.exe -d Ubuntu
Expected Behavior
I was expecting to be connected to my Ubuntu setup; I attach here an example of what it looked like
The user is 'thomas', my user's home directory contains a tree of directories and files. As you can see, .bashrc and my PS1 were also altered. I cannot recall the WSL version I was using before this issue, as I tried to install the version 2 at some point but I am not sure I succedded at the time.
Actual Behavior
When I replicate the aboe steps, instead of seeing my WSL setup, I get the following error
Diagnostic Logs
WslLogs-2024-03-06_20-03-40.zip
The text was updated successfully, but these errors were encountered: