Windows 10: "WSL2 is not supported with your current machine configuration" after enabling Hyper-V,...

Processor IntelR CoreTM i5-7500 CPU @ 3.40GHz 3.41 GHzInstalled RAM 16.0 GB 15.9 GB usableSystem type 64-bit operating system, x64-based processorPen and touch No pen or touch input is available for this displayEdition Windows 10 ProVersion 22H2Installed on ‎9/‎19/‎2022OS build 19045.2546Experience Windows Feature Experience Pack 120.2212.4190.0WSL2 is not supported with your current machine configuration. Please enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS. For information please visit https://aka.ms/enablevirtualization Err

:)

 

Constant Blue Screens after enabling WSL2/Hyper-V

Hello,

I have been trying to setup WSL2/Hyper-V on my windows 11 build 25236 for quite some time now. There is no crash with WSL1 but whenever I enable virtual machine platform I get constant Blue Screens with Stop Code: SYNTHETIC WATCHDOG TIMEOUT

Here is my minidump in BlueScreenView. Any help would be appreciated.

 

Enabling Hyper-V bricks Windows

A while ago I posted a question about WSL2 not working on Windows 11: Redirecting. It turns out, WSL2 requires Hyper-V enabled (even though it isn't stated anywhere).

So now I have discovered a new (actually very old) issue, enabling Hyper-V and SVM (in BIOS) bricks Windows. I have now reverted back to Windows 10, though the behavior is same on both versions (since Windows 11 is just Windows 10 under the hood). Here's what happens:

• Only Hyper-V Enabled = Boots fine
  
• Only SVM Enabled = Boots fine
  
• Hyper-V + SVM Enabled = Black screen or BSOD at boot
  

The BSOD, that appears sometimes (only Black screen most of the times), gives some insight, the error code is : 0xc0000098, caused by the BCD. Setting hypervisorlaunchtype to off in BCD (I can get to CMD through Safe Mode) "fixes" the booting issue, but it disables Hyper-V, so it is not a real fix for this problem.

I have found multiple forum posts discussing the same issue dating back to 2015, since the release of Windows 10, the final verdict being that this is a bug that needs to be resolved. But after 6 years and a new Windows release, the bug still exists.

Links to some forum posts, this is not an exhaustive list, just the first few I could find on a google search about this topic:

Windows does not boot after the Windows Hypervisor Platform is enabled - Microsoft Community

The computer does not boot if Hyper-V is enabled on Windows 10 pro (microsoft.com)

windows 10 - Can't boot computer after enabling Client Hyper-V - Super User

Can't boot after WSL 2 Install · Issue #4784 · microsoft/WSL · GitHub

 

Hyper-V & Win10

Hyper-V references:

Hyper-V Getting Started Guide

Install Hyper-V and Configure a Virtual Machine

Install and Configure Virtual Machines on Hyper-V

Step-By-Step: Enabling Hyper-V on Windows 8.1 - Canadian IT Professionals [TechNet Blogs]