ghost
commented
1 year ago /logs would be appreciated
Open bebablub opened 1 year ago
ghost
commented
1 year ago /logs would be appreciated
microsoft-github-policy-service[bot]
commented
1 year ago 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:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1The 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!
bebablub
commented
1 year ago Hello,
thank you for reply. I have executed the script as administrator in a powershell and tried to start wsl within my terminal. Logs are attached
WslLogs-2023-07-26_03-10-04.zip
thx!
bebablub
commented
1 year ago Does anyone have an idea?.... :/ Otherwise will do a clean Windows install....
NeonWizard
commented
1 year ago Same issue here. Not able to find any solutions online. Just randomly started happening, I haven't changed anything.
AskAlice
commented
1 year ago Same issue here. Not able to find any solutions online. Just randomly started happening, I haven't changed anything.
check msconfig and ensure you are in normal startup mode, and your boot services aren't cherry-picked
NeonWizard
commented
1 year ago Same issue here. Not able to find any solutions online. Just randomly started happening, I haven't changed anything.
check msconfig and ensure you are in normal startup mode, and your boot service aren't cherry-picked
You are literally a godsend. I was in selective startup for some reason, switching to normal startup fixed it.
snhok
commented
1 year ago For me, I had recently updated my bios and the Intel Virtualization Technology became disabled. After I reenabled it, WSL2 was working again.
AskAlice
commented
1 year ago Same issue here. Not able to find any solutions online. Just randomly started happening, I haven't changed anything.
check msconfig and ensure you are in normal startup mode, and your boot service aren't cherry-picked
You are literally a godsend. I was in selective startup for some reason, switching to normal startup fixed it.
lol I would say the same to you. When you mentioned you weren't able to find any solutions having tried the ones above, I thought about what i changed when i migrated my windows install to a VM with gpu passthrouh on linux, and realized I disabled the hypervisor in startup settings. I thought it was weird that the windows bootloader UI looked like windows 7 and there was no automatic timer and I had to press enter every time I wanted to boot into a different bcdedit entry...
jafber
commented
1 year ago Had the same problem, could not start Docker Desktop (and curiously also not install WSL 2). Turning the Hyper-V Windows feature off and on again solved it for me. So:
Control Panel > Programs > Turn Windows features on or off > Untick Hyper-V > Ok > Restart
Control Panel > Programs > Turn Windows features on or off > Tick Hyper-V > Ok > Restart
prokopis3
commented
12 months ago WslLogs-2023-07-26_03-10-04.zip same problem here i just upload the logs file of our system any thoughts
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:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1The 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!
sergiopvilar
commented
11 months ago Same issue here. I have everything enabled on the windows and on my BIOS as well. Not sure why I'm getting this since I had WSL 2 running a while ago on the same machine.
NeonWizard
commented
11 months ago Same issue here. I have everything enabled on the windows and on my BIOS as well. Not sure why I'm getting this since I had WSL 2 running a while ago on the same machine.
Did you give AskAlice's solution a try? If WSL gets in a bad state Windows apparently can automatically disable its bootup processes in msconfig. I think this happened to me when Docker Desktop had a really bad memory leak inside WSL2
yeremi01
commented
11 months ago aqui esta mi solucion https://www.youtube.com/watch?v=QW2DgEzb3Vc
xiurenfuwo
commented
10 months ago check msconfig and ensure you are in normal startup mode, and your boot services aren't cherry-picked
Thanks, it effects.
prokopis3
commented
10 months ago The wrong drivers were installed in the motherboard. My problem fixed
misft55
commented
10 months ago Hello, I don't know if your wsl --install issue was resolved, I will put this out there JIC. My issue was resolved differently than prokopis3. I was working on MacOS/VirtualBox Win 11install and in a "how to" related to Win11Vming in Windows Security I changed two Core Isolation options to off.
I turned them back on, restarted and Ubuntu fired right up.
goodpersons
commented
8 months ago bcdedit /set hypervisorlaunchtype auto
之前使用模拟器 提示让我禁用 Hyper-V ， 之后我进行了 Hyper-V 的重启 试过上面的所以的方法都没有效果，在最后
执行了 如上指令 在重启电脑 得到了解决 希望可以帮助到你
CalvinXu17
commented
4 months ago
bcdedit /set hypervisorlaunchtype auto之前使用模拟器 提示让我禁用 Hyper-V ， 之后我进行了 Hyper-V 的重启 试过上面的所以的方法都没有效果，在最后 执行了 如上指令 在重启电脑 得到了解决 希望可以帮助到你
This is useful!! Thanks bro.
Windows Version
Microsoft Windows [Version 10.0.22631.2050]
WSL Version
WSL version: 1.3.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
Kernel version: 5.15.90.3-1
Distro Version
Ubuntu-20.04
Other Software
No response
Repro Steps
It worked a few weeks ago so I installed Ubuntu 20.04 distro. But now i am getting `WSL2 is not supported with your current machine configuration. Please enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS. Enable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution For information please visit https://aka.ms/enablevirtualization Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED Press any key to continue...
[process exited with code 4294967295 (0xffffffff)] You can now close this terminal with Ctrl+D, or press Enter to restart.`
After trying to start the distro within Windows Terminal 1.17.11461.0
Expected Behavior
Ubuntu WSL starts
Actual Behavior
`WSL2 is not supported with your current machine configuration. Please enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS. Enable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution For information please visit https://aka.ms/enablevirtualization Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED Press any key to continue...
[process exited with code 4294967295 (0xffffffff)] You can now close this terminal with Ctrl+D, or press Enter to restart.`
Diagnostic Logs
I am running on a a pretty new AMD Ryzen 9 7940HS based ASUS ROG Zephyrus G14 (GA402XZ-NC021W).
SMT is enabled at BIOS, enable or disable Secure Boot does not seem to have any effect
I tried with no effect:
Enabled core isolation (memory integrity & Kernel mode enforced hardware stack)
Checked that file system is uncompressed
Reinstalling hyper visor plattform and virtual machine plattform through software control panel
Manually starting the LXSSMANAGER and validating that HV Host Service is running
Validated service logs (which were clean)
Created a new user at system... which ended up in same problems
Does anyone has an idea? Thank you!