github-actions[bot]
commented
1 week ago 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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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:
- "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.79
Closed similar issues:
- WSL2 fails to run with error 0x80370102 (#8065), similarity score: 0.77
- Cannot start even though hardware virt is enabled (#8107), similarity score: 0.77
- Cannot enable or otherwise use WSL2 (Possible BIOS and/or chipset quirk?) (#10973), similarity score: 0.76
- I can't use WSL2 (#10469), similarity score: 0.76
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
cheehong1030
cxw620
yjmthu
Windows Version
Microsoft Windows [Version 10.0.26120.2213]
WSL Version
2.3.26.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
docker
Other Software
Docker Desktop (Window)
Repro Steps
0x8007371B: "One or more required members of the transaction are not present."Expected Behavior
The Virtual Machine Platform should be enabled successfully, allowing me to use virtualization features. I should be able to run WSL.
Actual Behavior
The Virtual Machine Platform fails to enable with error code
0x8007371B. I am unable to use any virtualization features.Diagnostic Logs
Event Viewer The l1vhlwf service failed to start due to the following error: A hypervisor feature is not available to the user.
Related issue