WSL: Error: 0x800703e3 when launching WSL [Insider, Build 17655, 17661 & 17666]

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: 0x800703e3 and sometimes 0x80070040. I’ve tried running clean and 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 https://github.com/Microsoft/WSL/issues/1661, which doesn’t appear to be related(?)

Full show of everything going on: image

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Reactions: 2
  • Comments: 94 (20 by maintainers)

Most upvoted comments

We have identified a memory manager issue specific to AMD processors and will work to get this to the flighting branch ASAP. In the meantime I’d suggest people using AMD CPUs to roll back to a previous build if possible.

On 17666, I get The I/O operation has been aborted because of either a thread exit or an application request.. Using AMD Ryzen 2700X

@ioweb-gr - Yep! This is fixed in 17672.

Issue is still being debugged, when I have more info I will share.

We have a local repro, thanks to everybody who has sent us dumps. We are working on getting a fix out ASAP.

Just tried it and it works! Thank you

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.

Yes, the issue is in the Windows memory manager and could cause issues outside of WSL.

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 Error: 0x80070490 whereas letting it time out results in the Error: 0x800703e3. In either case, a new idle init daemon is spawned.

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 Error: 0x80070040

Hopefully this is helpful