You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ systeminfo
...
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
$ DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Image Version: 10.0.19045.4780
[===========================84.9%================= ]
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
I tried resolver with the windows steps for "Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.": https://aka.ms/enablevirtualization
$ bcdedit /set hypervisorlaunchtype Auto
The boot configuration data store could not be opened.
The requested system device cannot be found.
bcdedit /enum | findstr -i hypervisorlaunchtype
Other details:
It doesnt' let me access the BIOS (UEFI) with F12, F11, F10, F9, F8, ESC, etc to access the CLI and run becedit/bootrec. It only continues with the normal boot (Fast mode).
Windows has been receiving updates and some install fine and others don't install and send error of uninstalling updates.
I went to the bios/uefi and enabled the Intel VT-D and Intel Virtualization Tech for MSI Intel
I undo Old Windows Updates (
Expected Behavior
Working WSL distros, VMware, VirtualBox and Docker
Actual Behavior
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: WslRegisterDistribution failed with error: 0x80370102
Press any key to continue...
No logs.etl found in the archive. Make sure that you ran collect-wsl-logs.ps1 as administrator and that the logs.etl file is in the archive.
View similar issues
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!
Windows Version
Microsoft Windows [Version 10.0.19045.4780]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 22.04.4 LTS (Jammy Jellyfish)
Other Software
Repro Steps
Open Ubuntu or do anything wsl related to open a distro like
wsl --install Ubuntu
.I was using WSL with Ubuntu normally and after receiving a Windows update it updated a driver (I think) and after that, it stops working.
$ systeminfo ... Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
I tried resolver with the windows steps for "Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.": https://aka.ms/enablevirtualization
Also I tried to repair the disk
Other details:
becedit/bootrec
. It only continues with the normal boot (Fast mode).Intel VT-D
andIntel Virtualization Tech
for MSI IntelExpected Behavior
Working WSL distros, VMware, VirtualBox and Docker
Actual Behavior
Diagnostic Logs
Logs: WslLogs-2024-09-27_21-31-00.zip
PC specs: https://pcpartpicker.com/user/timdavidarm/saved/zs3n23
The text was updated successfully, but these errors were encountered: