Skip to content
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

WSL2 fails to run with error 0x80370102 #8065

Closed
1 of 2 tasks
chancsy opened this issue Feb 18, 2022 · 1 comment
Closed
1 of 2 tasks

WSL2 fails to run with error 0x80370102 #8065

chancsy opened this issue Feb 18, 2022 · 1 comment

Comments

@chancsy
Copy link

chancsy commented Feb 18, 2022

Version

Microsoft Windows [Version 10.0.22000.527]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.60.1

Distro Version

Ubuntu

Other Software

No response

Repro Steps

Don't have actual steps to reproduce it. Came from Windows 10 Home, upgrade to Windows 11 Home. WSL2 worked fine until 12th January (based on file modified date of my python virtual environment files which resides outside of wsl). Had VirtualBox 6.1+ installed, it has been uninstalled hoping to fix the issue.

List of Windows update after 12th January:
14-Jan: KB5008880 , KB5009566
24-Jan: KB5010795
5-Feb: KB5009469, KB402057, KB5008353
10-Feb: KB5011093
12-Feb: KB5010386
16-Feb: KB5010474
18-Feb: KB5010414

  • Virtual Machine Platform, Windows Hypervisor Platform, WSL turned on in Windows Features.
  • DEP checked and both tried both settings (Turn on DEP for essential Windows programs and services / for all programs)
  • Core Isolation -> Memory integrity turned on (was off due to "Xhunter1.sys" driver conflict when I check, Xhunter1.sys was installed by XIGNCODE3 anti-cheat and it is now removed.
> bcdedit /enum | findstr -i hypervisorlaunchtype
hypervisorlaunchtype    Auto
> systeminfo.exe
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

> msinfo32.exe

Item Value
Virtualization-based security Running
Virtualization-based security Required Security Properties Base Virtualization Support, Secure Boot, DMA Protection
Virtualization-based security Available Security Properties Base Virtualization Support, Secure Boot, DMA Protection, Secure Memory Overwrite, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control
Virtualization-based security Services Configured Credential Guard, Hypervisor enforced Code Integrity
Virtualization-based security Services Running Hypervisor enforced Code Integrity
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
Device Encryption Support Reasons for failed automatic device encryption: PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected
A hypervisor has been detected. Features required for Hyper-V will not be displayed.

Expected Behavior

Ubuntu in wsl2 install and run.

Actual Behavior

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370102
Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.

Press any key to continue...

Diagnostic Logs

https://aka.ms/AAfrvim

@chancsy
Copy link
Author

chancsy commented Feb 19, 2022

Reinstalled Windows 11 Home using ISO (keeping apps and files), problem gone. Now installing Windows updates and see which is able to break it.

Installed KB2267602, KB5009469, KB4023057 - OK
Installed KB5010474 - OK
Installed KB5010414 - OK

WSL2 and WSA still works. Closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant