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

WSL Error: WslRegisterDistribution failed with error: 0x80370102 #12379

Open
simonaberbece opened this issue Dec 14, 2024 · 9 comments
Open

WSL Error: WslRegisterDistribution failed with error: 0x80370102 #12379

simonaberbece opened this issue Dec 14, 2024 · 9 comments
Labels

Comments

@simonaberbece
Copy link

Hi, I tried installing Docker, but once I start it, the engine stops due to a WSL error. I think the problem might be related to the enabling of the virtualization. I am currently working on Windows Pro 11. I opened the windows features and made sure the following features are installed: VM-Platform, Windows Subsystem for Linux and Hyper-V. I also entered BIOS to make sure 'Intel (R) Virtualization Technology' is enabled. Moreover, when I enter Task Manager, it appears like virtualization is enabled.

However, when I try to input 'Get-WmiObject -Query "select * from Win32_Processor" | Select-Object -Property Name, VirtualizationFirmwareEnabled' in the terminal (admministrator) I get the following message:

Name VirtualizationFirmwareEnabled


13th Gen Intel(R) Core(TM) i7-1355U False

Nonetheless, when I try to install Ubuntu by using the command ' wsl.exe --install Ubuntu', I get the following error:

Ubuntu ist bereits installiert.

Ubuntu wird gestartet...

Installing, this may take a few minutes...

WslRegisterDistribution failed with error: 0x80370102

Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.

However, I tried to disable and enable again all these features and to uninstall wsl and start over, but I got the same result. Let me know how I can proceed. Thank you!

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How 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.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

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:

Closed similar issues:

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

@simonaberbece

This comment has been minimized.

Copy link

Diagnostic information
Found '/question', adding tag 'question'
Found '/feature', adding tag 'feature'
Found '/emailed-logs', adding tag 'emailed-logs'

@simonaberbece
Copy link
Author

/question

Copy link

Diagnostic information
Found '/question', adding tag 'question'

@elsaco
Copy link

elsaco commented Dec 14, 2024

@simonaberbece in an elevated pwsh session run get-windowsOptionalFeature -online -FeatureName virtualmachineplatform and check if enabled.

Sample output:

PS C:\Users\elsaco> get-windowsOptionalFeature -online -FeatureName virtualmachineplatform

FeatureName      : VirtualMachinePlatform
DisplayName      : Virtual Machine Platform
Description      : Enables platform support for virtual machines
RestartRequired  : Possible
State            : Enabled
CustomProperties :

and

PS C:\Users\elsaco> (gcim win32_processor).VirtualizationFirmwareEnabled
True

@simonaberbece
Copy link
Author

I ran get-windowsOptionalFeature -online -FeatureName virtualmachineplatform in powershell and got the output:
FeatureName : VirtualMachinePlatform
DisplayName : VM-Plattform
Description : Aktiviert die Plattformunterstützung für virtuelle Computer.
RestartRequired : Possible
State : Enabled
CustomProperties :

@zcobol
Copy link

zcobol commented Dec 16, 2024

According to Windows API documentation error 0x80370102 means The virtual machine could not be started because a required feature is not installed.

Please recheck your setup. Also check the filesystem(s) for errors.

@simonaberbece
Copy link
Author

However, I opened the windows features and made sure the following features are installed: VM-Platform, Windows Subsystem for Linux and Hyper-V. I also entered BIOS to make sure 'Intel (R) Virtualization Technology' is enabled. Moreover, when I enter Task Manager, it appears like virtualization is enabled. Did I miss something or is it any additional feature I didn't enable or method I forgot about?
Moreover, how do I check the filesystem for errors?

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

No branches or pull requests

3 participants