WSL2 Stopped Working? Fixing HCS_E_HYPERV_NOT_INSTALLED with Root-Cause Diagnostics
This error indicates a host virtualization issue, not a Linux distro issue.
Error context
Wsl/Service/CreateInstance/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
HCS cannot provision the WSL2 VM because Hyper-V is not active at kernel boot.
Root-cause chain
- BIOS/UEFI virtualization enabled
hypervisorlaunchtype=AutoVirtualMachinePlatform+WSLfeatures enabled- Virtualization services healthy
Structured fix
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
bcdedit /set hypervisorlaunchtype auto
Reboot and validate:
wsl --status
wsl -l -v
Advanced cases
- corporate hardening/GPO may disable required virtualization paths
- nested virtualization is mandatory when Windows itself runs as VM
Fallback
wsl --set-version <DistroName> 1
Use WSL1 only as contingency when Hyper-V cannot be enabled.
Conclusion
Treat this as a host orchestration incident. Fixing BIOS + BCD + features + services restores WSL2 reliably and avoids repetitive reinstallation noise.
This post is licensed under CC BY-NC.
Comments
Join the discussion below.
Comments are not configured yet. Add Cusdis settings in /assets/json/config/blog-comments-config.json.