WSL: Failed to install linux distro with error 0x8007023e
Environment
Windows build number: 10.0.19041.0
Your Distribution version: NA
Whether the issue is on WSL 2 and/or WSL 1: WSL 2
Steps to reproduce
I follow the docs to activate wsl 2 , then I am trying to install Linux distro , but failed with below error
Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007023e Error: 0x8007023e {Application Error} The exception s (0x
Expected behavior
Linux distro installed successfully.
Actual behavior
Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007023e Error: 0x8007023e {Application Error} The exception s (0x
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 3
- Comments: 41 (2 by maintainers)
I got rid of 0x8007023e by following steps
Turn Windows features on or offI was investigating why this failed and messed up with my note taking as I fixed it without having to do all of this, but this does seem to work.
Try this. It’s more in-depth …
At this point everything, for me, started working.
I have noticed that on the completion of installing any of the virtualisation features, when invoking Windows Update then KB4592438 gets reapplied. If you wish, and maybe recommended, invoke Windows Update when you install a Windows Feature. That’s what I did. Installed a feature, rebooted and invoked Window Update. (I think the only one where I didn’t invoke Windows Update is when I installed the Windows Hypervisor Platform.)
I ended re-installing windows 😦 and then it worked
Unfortunately this worked. Damnit.
I have been facing this issue on Windows 11. followed all the troubleshooting steps suggested here but none of them worked. MY specs are as follows:-
After breaking my head on for hours, I tried the following solution at a hunch and it worked. I set the version of wsl to 1.
wsl --set-default-version 1After above operation completed successfully,
wsl --install -d Ubuntucommand worked like a charm.I don’t know why it worked and why other solutions didn’t. Others who stumble onto this page may also try this before you resort to more desperate measures.
Thanks,
For whom it may help, the privateinternetaccess desktop app was causing this issue for me.
YESSSS!!! Worked with one strange minor twist I did prior to doing your recipe, so, whether it affected the outcome being positive is uncertain, as its possible it could have worked without enrolling in the Insider program. I am going to de-enroll and hopefully it will stick as the preview build will probably be trashed and rolled back. FWIW after enrolling in the insider program so I could drop in a preview build, se if that would resolve it, still no dice. Applied the recipe above and voile! AWESOME work and thank you very much for your master chef recipe to our salvation and sanity! 👍🏼 Side note, installing win-kex for kali had a few little nits and easy to resolve and find plenty of solutions online all saying the same thing, stop the vncservice and kill kali first, before rebooting, then relaunch into kex (KALI UI) worked perfectly. Hope you all had a HNY and staying safe and healthy!
Hmmm. This might be the same for me. I found that I could get it to work by following @Myron-S 's instructions, except for re-enabling hypervisor platform. I’m not doing anything with Virtual Box or VMware so I didn’t need it. I will test the PIA desktop app later when I’m back on my machine.
I am also facing this issue, no workaround. Any solutions?
At the same time this issue also affected my previous docker installations, and tried both with Docker Desktop 2.3.0.4 and Docker Desktop 2.0.0.3; but both returned different errors.
Docker Desktop 2.3.0.4 error:
Docker Desktop 2.0.0.3 error:
Holy s*** it worked. I think the problem is with the virtual box. we can’t install wsl2 after virtual box but vice versa is possible.
This solution works perfectly. Thanks.
Thought I’d update here. Confirming it is the PIA desktop app. When starting WSL for the first time after restart while connected to the VPN, it throws the RPC server unavailable. After disconnecting from the VPN, WSL launches and behaves normally, even after reconnecting. My solution is that whenever I need to start WSL (or do apt-get update/upgrade) I disconnect from the VPN, let WSL do its thing, then reconnect. I’d love to add WSL to the VPN bypass rules, however I can’t find the executable that it’s using to access the internet, I’ve already added my mintty terminal to them and I see no difference (external IP in WSL is still that of the VPN).
@ Myron-S, much appreciated the detailed step by step instructuions I will go through it step by step and let you know if it worked! That would be amazing!! @ gyk6985432 , Thanks for sharing your success with the approach proposed by Myron-S. Hoping I can replicate as same.
Thank you so much, after two days this solved my problem finally
Any update on this? In my case, I was able to successfully run the wsl2 Ubuntu for 3 days and then it started failing with the error code - 0x8007023e as below. Tried all the workarounds related to this error but no luck. Cant reinstall Windows as well. Tried reinstalling WSL completly but still its same issue
Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007023e Error: 0x8007023e {Application Error} The exception s (0x Press any key to continue…
Not an option for me 😦