WSL icon indicating copy to clipboard operation
WSL copied to clipboard

WSL wont start after no changes

Open neramas1221 opened this issue 6 months ago • 6 comments

When running wsl in a terminal I get the error: WSL2 is not supported with your current machine configuration. Please enable the "Virtual Machine Platform" optional component and ensure virtualisation 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: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED

I have checked an my BIOS and settings havent changed one day WSL worked fine and the next I got this error for some reason I now have 2 versions of Windows Subsystem for linux, Windows Hypervisor Platform and VM Platform i have no idea where they came from

Any ideas on how to fix this?

Cheers

Image

neramas1221 avatar Jun 11 '25 20:06 neramas1221

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

github-actions[bot] avatar Jun 11 '25 20:06 github-actions[bot]

WslLogs-2025-06-11_21-40-35.zip Here is the requested log files

neramas1221 avatar Jun 11 '25 20:06 neramas1221

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
.wslconfig found
Detected appx version: 2.4.13.0
Found no WSL traces in the logs

github-actions[bot] avatar Jun 11 '25 20:06 github-actions[bot]

WslLogs-2025-06-11_21-45-31.zip

I do get this error when I run the command:

Get-WindowsOptionalFeature : Get-WindowsOptionalFeature failed. Error code = 0x800f0819
At C:\Users\conno\collect-wsl-logs.ps1:57 char:1
+ Get-WindowsOptionalFeature -Online > $folder/optional-components.txt
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-WindowsOptionalFeature], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.GetWindowsOptionalFeatureCommand

I ran the command and the tried to start wsl

neramas1221 avatar Jun 11 '25 20:06 neramas1221

Diagnostic information
.wslconfig found
Detected appx version: 2.4.13.0
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED

github-actions[bot] avatar Jun 11 '25 20:06 github-actions[bot]

Hmm based on the error code, it looks like the Windows optional features are in a bad state (names are duplicated somehow). Unfortunately this is probably what's causing the issue here. You can try running sfc /scannow to help fix it, but if that doesn't work you might need to reinstall Windows

OneBlue avatar Jun 16 '25 19:06 OneBlue

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!