Error: 0x800703e3 when launching WSL [Insider, Build 17655, 17661 & 17666] #3134
Comments
|
I am encountering the same issue. Can anyone more familiar with the WSL internals give more information on further steps or determining steps to reproduce? |
|
Additional information that may be useful: I'm seeing two init processes. One of them is using the entirety of a CPU core, the other of which is sitting idle. Killing the second one results in another printing of Oddly enough, killing the init that's using the entire core will result in the idle one waking up, and taking up an entire core, and spawning it's own idle daemon. Killing the active one reverses it again and prints Hopefully this is helpful |
|
I also tried it with https://github.com/yuk7/ArchWSL, to the same result, but I'm not familiar enough with lower-level WSL to know if that's what you mean. With the behaviours of init, and the admittedly little that I know about WSL from Black Hat talks and blog posts, I'd guess the issue is with the re-implementation of init. |
|
@Brian-Perkins Unfortunately I can't remember. It was either 17643 or 17650, either way it was from one Skip Ahead to another. I've been busy lately so I can't remember whether I skipped 17650 or not. |
|
Could somebody experiencing these issues please collect and share logs so I can see what's going on? https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs |
|
@Seriell I am sure there is an official way, but a good enough way is to find a "Build: " string in c:\windows.old\windows\logs\cbs\cbs.log (note the .old part of the path) |
|
@Brian-Perkins Unfortunately I was low on disk space earlier today and I let it delete Windows.old, sorry! @benhillis Will do that now, hold up. |
|
@benhillis Here are the logs for the All I did was run |
|
I had originally installed the latest non-insider build, and then upgraded to this build |
|
@Seriell - Thanks for sharing the logs. Unfortunately nothing in there that would indicate what is spinning. Could you see if running bash.exe has the same behavior? |
|
bash.exe does the same thing, as does other distro exes. (I even tried as Admin but no dice) As noted by @0xADD1E it's probably some low level problem with the Init process. |
|
I tried to install a distro in fresh VM of Win build 17655. There is no problem with Wsl* functions (as was in 17650). Though I didn't try with Store app. |
|
Yes I did install Ubuntu in a previous build (More specifically, 17643) from the Store app. |
|
@Seriell - Thanks. Unfortunately I think the next step would be to look at a full memory dump. There are instructions for collecing one here: #2859 (comment) |
|
@Biswa96 That service wasn't running when I first looked (Set to manual), I started it and nothing changed. @benhillis I'll do that when I have time (Maybe later today, probably end up being tomorrow). |
|
@Seriell - Thank you very much, yes please reference this issue and my Microsoft alias: benhill |
|
i have same problem too. How to fix it? |
|
I just reverted to 17650 and paused the insider updates. |
|
i have same problem too. |
|
I couldn't manage to do the memory dump because I've been too caught up in other stuff, but a new build was released today, I'll try that build as soon as I can, and I suggest other with the same problem try updating too. |
|
I have tried the new build of Windows 17661, this problem still exists. |
|
This error paralyzed my work. How do I recover from it? |
|
I discovered I was updated to 17661 when I logged in this morning. Getting this same error with either legacy or ubuntu. Anyone know if reverting to the previous build lets this work again? Oh, and lxrun.exe doesn't seem to be installed any more, or at least not in System32 or anywhere else on the path. |
|
We still do not have enough information to fix this issue. The most useful thing somebody that is experiencing this issue can do would be to take a kernel dump and share it with me via secure@microsoft.com. |
|
@benhills, can you please provide a link to instructions? PS I'm available on Gitter for realtime chat. |
|
@lolmaus - Instructions here #3134 (comment). |
|
Will any memory dump do, or just before/during/after trying to start wsl.exe, or after the error message shows up? |
|
@rodrymbo - It will have to be while the CPU is spinning trying to launch. |
|
@Moises Cardona is this in WSL?
|
|
Yes @DaJakerBoss |
|
@moisesmcardona - That is the same error. In the most recent Insider build, wsl.exe and bash.exe will print error strings instead of hex error values whenever possible. |
|
@ben Hillis will the bug fix for WSL also fix some of the other
memory-related issues? 17666 is still having the same application errors as
before (though I'm not surprised since there was no fix for WSL in 666
either).
Speaking of, why isn't this issue listed in the Insider Blog?
…On Thu, May 10, 2018 at 4:05 PM, Ben Hillis ***@***.***> wrote:
@moisesmcardona <https://github.com/moisesmcardona> - That is the same
error. In the most recent Insider build, wsl.exe and bash.exe will print
error strings instead of hex error values whenever possible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3134 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Afs4z7K3GcFaSTQTVbGZ5Rq4Wl5QOriAks5txKuugaJpZM4Tr1HX>
.
|
|
Yes it should. I'm not sure, I'll sync up with the people who write those release notes tomorrow and see about adding something. |
|
thank you so much!
…On Thu, May 10, 2018 at 8:37 PM, Ben Hillis ***@***.***> wrote:
Yes it should. I'm not sure, I'll sync up with the people who write those
release notes tomorrow and see about adding something.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3134 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Afs4z5ZJ2WLnhTenYq4Hd7hUq0NR_-2sks5txOtbgaJpZM4Tr1HX>
.
|
|
Is it fixed in 17672.1000 perhaps? |
|
@ioweb-gr - Yep! This is fixed in 17672. |
|
That's great to hear :) |
|
Just tried it and it works! Thank you |
|
Thank you so much! I can get back to work now!
…On Wed, May 16, 2018 at 1:52 PM, SemperFu ***@***.***> wrote:
Just tried it and it works!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3134 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Afs4zyijgChRghNy9X4iOR2FsA0QuIu5ks5tzHVfgaJpZM4Tr1HX>
.
|
|
I just updated and it works fine for me too. Thank you very much |
|
17672 Fixed. Thanks! |
|
Updated and can confirm it works here too. |
|
Thanks. |
|
Thanks for confirming the issue is resolved. |
|
The error started poping up again in April 2020 update |
I don't have this issue on build 19041.207 with Ryzen 7 2700X, it may be something else causing it. Might also help to know what your CPU is since the original isssue only affected AMD CPUs. |
|
@arcsoftech Same for me. It happens during startup, before anything else is displayed. And I am on an Intel CPU. |
|
@Erisa Perhaps re-open the issue or should we make a new? |
If it's affecting Intel CPUs then it's probably not related to this problem and you should probably open a new issue. |
|
I got this issue as well. I found that the most stable way to launch WSL Bash is to wait until after these two conditions are met:
Once those two conditions are met, I open my PowerShell 7 and type My Winver: |
and others
On the latest Skip Ahead Insider build (1803 / 10.0.17655.1000), WSL refuses to launch (On any distro), instead hanging (With Init using ~25% cpu at all times) before giving
Error: 0x800703e3and sometimes0x80070040.I've tried running
cleanand even installing a different distro (Can reproduce on Ubuntu and openSUSE) to no avail.I only noticed this happening directly after updating to 17655, and searching online for this error code only comes up with #1661, which doesn't appear to be related(?)
Full show of everything going on:
The text was updated successfully, but these errors were encountered: