Open hisriram96 opened 12 months ago
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
I have tried disabling and reenabling Virtual Machine Platform and WSL features.
ism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
I have tried removing WSL completely and reinstalling again.
I have tried uninstalling and reinstalling Docker Desktop. Docker Desktop installation fails as WSL could not be started.
I also tried the steps mentioned here - https://github.com/microsoft/WSL/issues/10764#issuecomment-1815485695, but issue still persists with same error.
wsl -install
.Thank you @hisriram96. We received the logs you sent by email but I'm not seeing any logs from WSL in there.
Can you try to run the log collection while you reproduce the issue ?
/logs
Having the same problem
I have already sent logs to InsiderSupport@microsoft.com with:
Uploading them here as well. WslLogs-2023-12-01_07-24-47.zip
Hello @OneBlue, apologies, missed your comment. I have uploaded the logs in the above comment.
I observed that there was a ghost directory Linux in my File Explorer. So, I followed the steps in this article https://www.thewindowsclub.com/how-to-add-or-remove-linux-from-file-explorer-navigation-pane-in-windows-11-10 to remove that ghost Linux folder this article. I uninstalled the WSL, disabled WSL, Virtual Machine Platform, and Windows Hypervisor Platform and restarted my computer and then installed WSL, reenabled WSL, Virtual Machine Platform, and Windows Hypervisor Platform features and restarted my computer but observed same issue.
Thank you @hisriram96. Looking at logs it's unclear where exactly the issue comes from.
Are you running on an ARM64 device ?
No, it is x64-based processor.
Interesting. I wonder if this might be related to the distribution. Can you try running:
wsl --install -d debian
And see if debian can install ?
It is not related to distribution as installation of any other distribution also fails.
Thank you @hisriram96. This is interesting. Let's try to capture a TDD trace.
Can you please follow 12) Collect wslservice time travel debugging traces for let's say debian.exe and share them here ?
Hello @OneBlue, I tried collecting TDD trace for wslservice.exe
service but I observed error below.
I have shared the files generated when collecting the trace.
I observed the same error for debian.exe
process.
Please find the files generated when collecting the trace.
Ah too bad, time travel debugging might not be an option here.
Let's try something else. What's the output of wsl.exe -l -v
and wsl.exe --version
?
Ok interesting. So this works at least.
Do you have any installed software that could conflcit with WSL ? Antivirus, proxy, anti-cheat or something similar ?
Also are there any crashes when you get this error ? You can follow 11) Reporting a WSL process crash to collect them
I have sent the WSL process crash dump has been shared via email to insidersupport@microsoft.com. The C:\crashes was empty.
I have sent the WSL process crash dump has been shared via email to insidersupport@microsoft.com. The C:\crashes was empty.
We haven't received yet. Can you tried to send it to: secure@microsoft.com and say that it's for the WSL team ?
@OneBlue It seems I cannot send the file via email because it is of 36 MB even after compression. Is there any other way I could send?
@OneBlue It seems I cannot send the file via email because it is of 36 MB even after compression. Is there any other way I could send?
You can use OneDrive / Gdrive or equivalent
@OneBlue I have shared the OneDrive link to secure@microsoft.com and insidersupport@microsoft.com. You culd request for access.
Thank you @hisriram96. I confirmed that we received the dump. Unfortunately there was nothing abnormal with it so this doesn't help.
I wonder if the WSL optional component got enabled correctly. Can you share the content of the following registry keys:
HKEY_CLASSES_ROOT\CLSID\{a9b7a1b9-0671-405c-95f1-e0612cb4ce7e}
HKEY_CLASSES_ROOT\Interface\{46f3c96d-ffa3-42f0-b052-52f5e7ecbb08}
HKEY_CLASSES_ROOT\CLSID\{e66b0f30-e7b4-4f8c-acfd-d100c46c6278}
Hello @OneBlue please find the content of the requested registry keys.
Please find the registry keys below.
Thank you @hisriram96. Everything here looks normal so that's not the issue.
I've added a new log provider to our logging script which should help understand this.
Can you try to collect /logs again while you reproduce this error again ? Sorry for the back and forth.
Hello @OneBlue, no worries. Please find the logs below.
WslLogs-2023-12-16_20-41-32.zip
I ran commands wsl --install
, wsl --install -d Debian
, and wsl --install -d kali-linux
for reproducing the issue.
Hello @OneBlue, wishing you a very happy new year. Please let me know if there is anu update on the logs shared? Thank you.
Thank you @hisriram96. Unfortunately the new logs don't have the details I was hoping for. Let's try something else.
Can you share the output of (powershell):
$debian=(Get-AppxPackage TheDebianProject.DebianGNULinux).InstallLocation
wsl.exe --import test-distro . $debian/install.tar.gz
(Assuming that the debian application is installed)
It did not return any error.
Interesting. Does WSL start correctly after the distribution is installed ?
It does.
Ok. And what if you start let's say debian.exe now ?
I am observing same error when running debian.exe.
Hello @OneBlue, running debian.exe returns same error so does wsl --install
command.
Hello @OneBlue, please let me know in you had any findings.
Any fix?
Windows Version
Microsoft Windows [Version 10.0.22621.2715]
WSL Version
2.0.12.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
No response
Other Software
Docker Desktop
Repro Steps
wsl --install
Expected Behavior
wsl --install should install default distro as Ubuntu, and Docker Desktop should be able to create docket-desktop-data and docker-desktop.
Actual Behavior
Executing
wsl --install
command returns an error "0x8007019e The Windows Subsystem for Linux has not been enabled.".wsl --install Ubuntu is already installed. Launching Ubuntu... Error: 0x8007019e The Windows Subsystem for Linux has not been enabled.
Press any key to continue... The operation completed successfully.
Diagnostic Logs
No response