microsoft / microsoft/WSL

WSL2 fails with `HCS_E_HYPERV_NOT_INSTALLED` on Windows 11 build 26200.7840; `HypervisorPresent=False` despite virtualization enabled

Open
#14,384 20 comments 0 reactions 1 assignee View on GitHub

@craigloewen-msft is already working on this.

Since Mar 24, 2026.

hypervisor-platform
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

Windows Version

Windows 11 25H2 (OS Build 26200.7840)

WSL Version

2.6.0.3.0

Are you using WSL 1 or WSL 2?
  • WSL 2
  • WSL 1
Kernel Version

6.6.87.2-1

Distro Version

No response

Other Software

No response

Repro Steps

After updating to Windows 11 25H2 (OS Build 26200.7840), WSL2 cannot install any distribution. wsl --install fails with:

Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED

This happens even though:

  • AMD-V/SVM is enabled in BIOS/UEFI and Windows confirms firmware virtualization is enabled.
  • Windows optional features required by WSL2 are enabled (VirtualMachinePlatform, HypervisorPlatform).
  • Boot loader is configured with hypervisorlaunchtype Auto.
  • vmcompute and hns services are present and running.
  • System health checks (DISM /RestoreHealth and sfc /scannow) report no integrity violations.

However, Windows reports no hypervisor is present at runtime:
(Get-CimInstance Win32_ComputerSystem).HypervisorPresent returns False.

Because the hypervisor never loads, WSL2 cannot create its VM and Docker Desktop (WSL2 backend) also cannot start.

  1. Boot Windows 11 25H2 (OS Build 26200.7840).
  2. Open PowerShell as Administrator.
  3. Run:
    wsl --install
    
  4. Observe distro installation fails with HCS_E_HYPERV_NOT_INSTALLED.

Optional verification (shows hypervisor never loads even though prerequisites are enabled):

(Get-CimInstance Win32_ComputerSystem).HypervisorPresent
Expected Behavior

Expected: True

Actual Behavior

Actual: False

Diagnostic Logs
Windows optional features
dism /online /get-featureinfo /featurename:VirtualMachinePlatform
dism /online /get-featureinfo /featurename:HypervisorPlatform

Both show:

State : Enabled
Services
Get-Service vmcompute,hns | Format-Table Name,Status,StartType
hns       Running    Manual
vmcompute Running    Manual

WSL service present on this build:

Get-Service WSLService | Format-Table Name,Status,StartType
WSLService Running Automatic

Note: LxssManager service is not present on this system (only WSLService exists).

System integrity checks
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Results:

  • DISM: restore operation completed successfully
  • SFC: Windows Resource Protection did not find any integrity violations
Additional info
systeminfo | findstr /i "Hyper-V"

Output:

Hyper-V Requirements: VM Monitor Mode Extensions: Yes
What I tried
  • Verified SVM/AMD-V enabled in BIOS/UEFI.
  • Confirmed required Windows features enabled: VirtualMachinePlatform + HypervisorPlatform (+ WSL).
  • Confirmed hypervisorlaunchtype Auto.
  • Ran DISM RestoreHealth + SFC (no integrity violations).
  • Multiple reboots.
  • Issue persists: hypervisor not present (HypervisorPresent=False) and WSL2 fails with HCS_E_HYPERV_NOT_INSTALLED.
Questions
  • Is this a known regression on Windows 11 25H2 build 26200.7840 where the hypervisor fails to load, causing WSL2 CreateVm/HCS to fail?
  • What logs should be attached to identify why the hypervisor is not loading (Event Viewer channels / ETW traces)?
  • Any workaround to force hypervisor load without reinstalling Windows?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.