-
Notifications
You must be signed in to change notification settings - Fork 823
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
WslRegisterDistribution failed with error: 0x8007023e #10507
Comments
I don't see anything in the traces. Did you let the log collection run while launching wsl? |
what more do you need? |
@pszlaga, what I need is for the log collection program to run while you run commands on/inside wsl. If you immediately exit the log collection, I don't get to see anything. |
/logs |
Hello! Could you please provide more logs to help us better diagnose your issue? To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging Thank you! |
Oh, i'm sorry, my bad. Now you have new logs in attachment |
@keith-horton, can you triage or delegate triage? This is pre mirrored and shows errors on |
It's failing to create the switch (network). @pszlaga , can you collect a trace using this WPR script https://github.com/microsoft/WSL/blob/master/diagnostics/wsl_networking.wprp? We need some network-specific traces: wpr -start wsl_networking.wprp -filemode |
Hello, do you have any solutions? |
Sorry - I reviewed the traces and opened an issue with the Hyper-V VSwitch team. Their traces don't show the source of the error - only that it's failing trying to create that NAT network. Given this I'm trying to find a way to unblock you. This continue to repro after a reboot? WSL requires Virtual Machine Platform - though you can have others installed as well. If it doesn't risk you losing data, and just a reboot won't fix this, I would remove the features above, reboot, then add what you need back. I'm sorry I don't have a better work-around available. |
I have everything disabled except:
I uninstalled the above and reinstalled it. I also removed WSL and reinstalled it via PowerShell. I used the commands: netcfg -d Unfortunately, nothing helps. Additionally, I removed the network card drivers and installed them again, but this did not solve the problem. I uninstalled VPN, VirtualBox, same problem. Tell me, am I able to recover files from a vhdx disk when the system was Ubuntu 20.04? wsl export also returns the same error as when I want to start the machine. |
Wow. sorry it's been so painful. The traces suggest something may be crashing. could you follow this to see if there's something crashing - and collect the dmp? https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#11-reporting-a-wsl-process-crash |
I followed point number 11 step by step, but my crashes folder is empty? |
I'm facing the same issue after updating Windows 11 to KB5030310 (OS Build 22621.2361) Preview. None of the virtualization apps are working including WSL2, Windows Sandbox, VMware. |
Sorry, I don't know what is causing vswitch to immediately fail to create a switch. All I can recommend at this point is to call to Windows OS support :( |
Go to WSL settings app. Go to optional settings and enable safe mode. |
Download the wsl from github. |
Windows Version
Microsoft Windows [Version 10.0.19045.3324]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
wsl -d Ubuntu-20.04
Expected Behavior
It will launch Ubuntu 20.04.
Actual Behavior
{Błąd aplikacji} W aplikacji wystąpił wyjątek %s (0x
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x8007023e
Diagnostic Logs
WslLogs-2023-09-20_00-02-31.zip
The text was updated successfully, but these errors were encountered: