Cannot enable or otherwise use WSL2 (Possible BIOS and/or chipset quirk?)

[TheSystemGuy1337]

Windows Version

Microsoft Windows [Version 10.0.22631.2861]

WSL Version

Not applicable

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Not applicable

Distro Version

Not applicable

Other Software

Not applicable

Repro Steps

Attempt to enable WSL2 on a Beelink SER5.

Expected Behavior

WSL2 enables, and works as intended. No fatal errors or 0x codes being tossed.

Actual Behavior

WSL complains, stating "Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.", even if both are enabled. Doing a clean install results in WSL tossing 0x80370102. Other people seem to have the exact same issue as me, but those issues appear to be dead.

Diagnostic Logs

WSL doesn't init, so logs may be useless here. But they have been added anyway.
WslLogs-2024-01-02_12-46-52.zip

P.S. Trying to enable WSL2 will also break Virtualbox and VMware, with VMware complaining saying "VMware Player and Device/Credential Guard are not compatible. VMware Player can be run after disabling Device/Credential Guard. Visit http://www.vmware.com/go/turnoff_CG_DG for more details."

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

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.80
• After enabling WSL2 - Your PC ran into problem (#5770), similarity score: 0.80

Closed similar issues:

• Unable to enable WSL2 (#5282), similarity score: 0.82
• Can't enable WSL2 (#4817), similarity score: 0.82
• WSL2 fails to run any distros with error 0x80370102 (#7068), similarity score: 0.80

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

[OneBlue]

@TheSystemGuy1337: I'm not seeing any WSL logs in the trace you shared. Can you share /logs of a repro of the error you're seeing ?

[TheSystemGuy1337]

This issue is dead. I have moved on to better solutions like VMware and Oracle VM VirtualBox. Other people have the same issue as me; so it's clearly obvious that WSL was rushed right out the door. Also, how am I supposed to send logs when WSL WON'T INITALIZE TO BEGIN WITH?