-
Notifications
You must be signed in to change notification settings - Fork 812
-
Notifications
You must be signed in to change notification settings - Fork 812
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to install linux distro with error 0x8007023e #5508
Comments
Probably #4103 |
Tried the solution , It did not work. fsutil behavior set disableencryption 1 |
I have the same error too |
Please collect detailed logs given the work-around over there didn't take. |
Please check logs |
@mabusaa |
Not an option for me :( |
Any updates on this?? tried couple of workarounds mentioned (decompression and reinstalling) does not seem to work now. |
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. Installing, this may take a few minutes... |
I ended re-installing windows :( and then it worked |
I met same problem, no workaround now. |
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:
|
I got rid of 0x8007023e by following steps
|
Unfortunately this worked. Damnit. |
Thanks. I shall try this. a Windows reinstall is not an option for me. |
It didn't work. :-( |
Ok.... I have an older laptop what has Ubuntu operating under WSL2. It installed under WSL2. This is my older back-up laptop.
On my main laptop I have uninstalled all the virtual machine stuff and then reinstalled virtualisation components individually, restarting as required and running Windows Update after each restart. What could I compare between the back-up laptop and my main laptop to see where the difference/discrepancies are? |
Same issue here. I have a laptop running wsl2 but my main desktop is not taking wsl2 at all. It was previously working but one day it mysteriously wouldn't launch my WSL2 distro (Ubuntu 18.04LTS) and was throwing the "RPC server unavailable error". |
Likewise tried everything I could find online over the past 30 days, for wsl1 no issues, for wsl2, not the case, yes, d-loaded the wsl2 update also, yes, tried both manual dload of the .appx (THEN EXECUTE FROM POWERSHELL Add-AppxPackage .<distrofilename>.appx, and via msft store, both failed, yes, tried rolling back and uninstalling various updates, yes, tried going back to various other restore points, I TRIED EVERYTHING I COULD FIND ONLINE - MSFT WSL DEV TEAM PLEASE HELP THIS IS NOT GOING TO MAGICALLY FIX ITSELF - SOMETHING IS HOSED ON YOUR MSFT SIDE, IF YOU HAVE A BAND-AID UNTIL A MORE ROBUST SOLUTION, PLEASZE FEEL FREE TOENMLIGHTEN US WITH SUCH KNOWLEDGE... Installing, this may take a few minutes... I don't believe any of the fixes I have seen online actually work for whatever is happening now. @EfveZombie Damnit, it did not work for me, but E for Effort! - Tried the shut off Virt and WSL in Win Features, reboot, re-enable, reboot again - not so much. Tried enabling [and disabling] various alleged juju tricks which apparently resolved issues for others such as state changes to services and also in gpedit, again, negative results. Current sys info on my side: OS Name Microsoft Windows 10 Pro for Workstations Virtualization-based security Running MSFT's release notes version by version: https://docs.microsoft.com/en-us/windows/wsl/release-notes - in case it helps anyone else on here, it did not for me, but saw places where it has for others. Reinstallation of Windows 10 is not an option for me. Any logs I can send simply let me know the default path to such log files (e.g. C:\users\...) - happy to provide. Any assistance is appreciated...perhaps an electromagnetic deflector shield in the event cosmic rays output by the Sun are causing such to occur? /Zap |
I 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.) |
Thank you so much, after two days this solved my problem finally |
@ 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!! |
For whom it may help, the privateinternetaccess desktop app was causing this issue for me. |
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. |
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! |
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. |
This solution works perfectly. Thanks. |
This solution works for a different error. One that says the disk are sparse, If you are getting that error, uninstall the distros you have installed, copy the first command into Powershell, Enter, repeat with the second and restart your pc. Also, make sure you installed the WSL 2 kernel AND you ran wsl --set-default-version 2. To find out more help info on the WSL in general you can type Get-Help wsl into Powershell to get advanced options. GL! |
Worked. Oddly enough this is the second error I have had to fix. The first one was solved by the commands |
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. |
Linking to logs from other issue: https://github.com/microsoft/WSL/files/5965131/wsl.etl.zip |
The only recipe that worked for me, and was extremely easy to apply was in this reddit reply So basically, the root of the problem is with the DNS client service. If you have restart this service using regular tools such as services.msc, way to go. But in my case, the option was greyed out. As described in the link, I had to disable, restart, enable, restart.
One final thing to add, in case anyone finds any connection. About one or two weeks back I had opted into Windows Insider program. This problem emerged when my Windows 10 was updated about two or three days back. |
this method works, it may take a while to restart. |
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. After above operation completed successfully, 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, |
I should also add that I want to Linux GUI applications and have installed WSLg Preview version. Necesaary drivers for vGPU from Intel and Nvidia have been added as per instructions manual for WSLg. Relevant information about my system is as follows:-
Would really like a solution here. |
I can see the maintainers have not even assigned anyone to work on this issue. What is the point of lengthy submissions and issue-raising if discussions remain idle for want fo response. Really expected better. |
After following @Myron-S solution I was still getting the error then I tried @rajivranjansinghpolice suggestion and finally it worked ...so many days and hours of my life were lost on this thank you for the fix nothing else on line worked |
I had the same issue and went through all steps listed here with no changes. Right before i was going to reinstall windows i rememberd i hadn't installed Restoro on this computer yet. It works by scanning and replacing courrupted/deleted files in windows. So quick install, run and restart with Restoro and everthing is back to normal for me. Although i did use the paid version the free version should be able to do the same thing for anyone interested. I'm not affiliated with Restoro in anyway just think it could help some of the people dealing with this issue. It was 3 days of beating my head agaisnt the wall before this so i understand everyones pain! Good Luck! :) |
however, most of these methos don't work after restart PC times |
the most interseting is that: after i change wsl vertion back (version 2) it worked too!!! |
Environment
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
The text was updated successfully, but these errors were encountered: