WSL not working after windows update (Windows 10 Pro): WslRegisterDistribution failed with error: 0x80370102

[davidadarme]

Windows Version

Microsoft Windows [Version 10.0.19045.4780]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu 22.04.4 LTS (Jammy Jellyfish)

Other Software

• Docker Desktop (Windows)
• VirtualBox (Also doesn't working for the hypervirsor)

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.

$ wsl --version
WSL version: 2.2.4.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.19045.4780

$ Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
    Path          :
    Online        : True
    RestartNeeded : False

$ 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

Also I tried to repair the disk

$ bootrec /fixboot
$ bootrec /fixmbr
$ bootrec /rebuildbcd

$ chkdsk C: /f

$ 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...

Diagnostic Logs

Logs: WslLogs-2024-09-27_21-31-00.zip
PC specs: https://pcpartpicker.com/user/timdavidarm/saved/zs3n23

[github-actions]

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!

Open similar issues:

• "WSL2 is not supported with your current machine configuration" after enabling Hyper-V, Virtual Machine Platform, Windows Subsystem for Linux, Hypervisor Platform and virtualization in up-to-date bios. (#9652), similarity score: 0.83
• WSL not working after windows update (#10185), similarity score: 0.81
• Error code: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED (#10332), similarity score: 0.81

Closed similar issues:

• WSL2 fails to run with error 0x80370102 (#8065), similarity score: 0.82
• Error 0x8007019e and Wsl/CallMsi/0x80070424 and Wsl/REGDB_E_CLASSNOTREG (#11683), similarity score: 0.82

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Diagnostic information

Detected appx version: 2.2.4.0
No logs.etl found in archive.
Error while parsing the logs. See action page for details

[davidadarme]

logs with the logs.etl: WslLogs-2024-09-27_22-50-09.zip

[github-actions]

Diagnostic information

Detected appx version: 2.2.4.0
Detected user visible error: Wsl/InstallDistro/0x80072ee2

[OneBlue]

@davidadarme: It looks like another hypervisor might be conflicting with hyper-V here. Does uninstall VirtualBox and rebooting solve the issue ?