WSL2 stopped working: VirtualMachinePlatform & WSL feature not recognized properly

[borjamunozf]

Windows Version

10.0.22631

WSL Version

2.0.9

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

One developer in my company reported to us a major issue with WSL. It stopped working all of the sudden and says:

WSL2 is not supported with your current configuration. Please enable Virtual Machine Platform optional component ande nsure virtualization is enabled in the BIOS

Expected Behavior

WSL works as before.

Actual Behavior

1. Windows features list seems strange (duplicates). He cannot uninstall or install again the features
   

2. Trying to uninstall them says that Windows cannot find the files. Error 0x80070490
   

3. Trying to uninstall with command line says that the features dont exist

dism /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /Remove
dism /online /disable-feature /featurename:VirtualMachinePlatform /Remove

All day without being able to work.

Please, need help.

Diagnostic Logs

No response

[github-actions]

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 scipt will output the path of the log file once done.

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

Diagnostic information

Found '/feature', adding tag 'feature'

[borjamunozf]

Here the logs

WslLogs-2024-04-16_06-46-02.zip

[josemtella]

If you don't activate Hyper-V nothing will work for you

[salvarez96]

I have the exact same problem, even with the duplicates in the features list. At first, I thought that one of the recent windows updates messed up with something, so I uninstalled every update from march and april, rebooted and the duplicated features were no longer there.
Nevertheless, WSL2 still doesn't work, only WSL1 but that doesn't work for me as all my data is saved with WSL2 and I don't want to cope with WSL1 issues. I tried so many things:

• Unregistering and reinstalling distros
• Activating and deactivating everything related with virtualization, including hyper-v, virtual platform and even CPU virtualization from BIOS.
• Trying to install distros with WSL1 and then trying to change their version for WSL2, unsuccessful.
• Rebooting like crazy after every change.
• Uninstalling and reinstalling WSL.

Nothing has worked for me, and I'm sure there's something with one of the most recent windows updates that messed with WSL because everything was working just fine. Lucky me I have an OS copy in another drive in the same computer where WSL still works like normal, so I deactivated windows updates in case some of that is the problem because that system has not been updated since february.

[eggheaded]

Same issue, two separate computers now, I thought it was related to a power outage on my desktop, but also just discovered my laptop (also on the latest Windows Insiders Build, also replicated the same uninstall, reinstall steps to no avail) has the same problem. Something is clearly going on and the other recent open and closed issues (the latter only leads to "solving the problem" by completely reinstalling windows) regarding this issue need to be taken seriously.