Fix HCS E SERVICE NOT AVAILABLE WSL Error on Windows 10 & 11 (7 Proven Fixes)

When you try to install or launch a Linux distribution in Windows Subsystem for Linux (WSL), you may see this error:

error wsl/installdistro/service/registerdistro/createvm/hcs/hcs_e_service_not_available

This error means Windows cannot start the Hyper-V Compute Service (HCS) that WSL2 uses to create its virtual machine. When virtualization services, Windows features, or system drivers fail to initialize correctly, WSL cannot start its backend VM and throws this error.

You’ll commonly encounter this problem after Windows updates, BIOS resets, virtualization conflicts, or corrupted WSL components.

What Causes HCS_E_SERVICE_NOT_AVAILABLE in WSL?

This error typically appears when one or more of the following conditions exist:

• The LxssManager service is stopped or stuck.
• Windows Subsystem for Linux or Virtual Machine Platform features are disabled.
• Hardware virtualization is disabled in BIOS or UEFI.
• Hyper-V requirements are not satisfied on the system.
• WSL kernel or tools are outdated or corrupted.
• Linux distribution registration fails due to broken configuration.
• The Windows hypervisor fails to launch during boot.
• Conflicts exist with virtualization software such as VirtualBox or VMware.

This error often appears alongside messages like CreateVM failed, WSL2 cannot start virtual machine, or Hyper-V Compute Service error.

How to Fix HCS_E_SERVICE_NOT_AVAILABLE WSL Error

Apply these fixes one by one. After each fix, restart your system and test WSL again.

1. Restart the WSL Services

A stalled background service can block WSL from initializing.

Steps:

1. Open Command Prompt as Administrator.
2. Run:

net stop LxssManager
net start LxssManager

3. Launch your Linux distro again.

If the service fails to start, continue to the next fix.

2. Enable WSL and Virtual Machine Platform Features

WSL cannot run if required Windows features are disabled.

PowerShell Method:

Open PowerShell as Administrator and run:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux -NoRestart
Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform -NoRestart

Restart your PC afterward.

GUI Method:

1. Press Win + R, type optionalfeatures, press Enter.
2. Enable:
   • Windows Subsystem for Linux
   • Virtual Machine Platform
3. Click OK and restart.

3. Verify and Enable Hardware Virtualization in BIOS

WSL2 requires CPU virtualization support.

Check status:

1. Open Task Manager → Performance → CPU.
2. Look for Virtualization: Enabled.

If disabled:

• Restart your PC and enter BIOS/UEFI.
• Enable one of the following depending on your CPU:
  • Intel VT-x / VT-d
  • AMD-V / SVM Mode
• Save changes and reboot.

4. Check and Enable Hyper-V Requirements

Even on Windows Home editions, WSL2 depends on Hyper-V virtualization components.

Steps:

1. Open Command Prompt.
2. Run:

systeminfo

3. Scroll to the bottom and verify:
   • Virtualization Enabled in Firmware: Yes
   • Hyper-V Requirements: All Yes

If any requirement shows No, BIOS virtualization or Windows features may still be misconfigured.

5. Update the WSL Kernel and Tools

Outdated WSL components frequently cause compatibility issues after Windows updates.

Steps:

Open PowerShell as Administrator and run:

wsl --update
wsl --shutdown

Reopen WSL and test again.

6. Re-register or Reinstall the Linux Distribution

A corrupted Linux distro can prevent WSL from registering correctly.

Steps:

1. List installed distros:

wsl --list --verbose

2. Unregister the broken distro:

wsl --unregister <DistroName>

3. Reinstall it:

wsl --install -d <DistroName>

Replace <DistroName> with your actual distro name (Ubuntu, Debian, etc.).

7. Install All Windows Updates

Microsoft often fixes virtualization and WSL bugs through cumulative updates.

Steps:

1. Open Settings → Windows Update.
2. Click Check for updates.
3. Install all pending updates.
4. Restart the system.

8. Verify Hypervisor Launch Type (Advanced)

Sometimes Hyper-V is installed correctly but fails to launch during boot.

Steps:

1. Open Command Prompt as Administrator.
2. Run:

bcdedit /enum | findstr hypervisorlaunchtype

If it shows OFF, enable it:

bcdedit /set hypervisorlaunchtype auto

Restart your computer afterward.

This fix resolves many cases where WSL2 cannot create the virtual machine even though features appear enabled.

Advanced Troubleshooting Options

If the issue persists, try these deeper checks:

Check WSL Status

wsl --status

This shows default version, kernel status, and configuration.

Resolve Virtualization Software Conflicts

Older versions of VirtualBox and VMware may conflict with Hyper-V.

• Update virtualization software to the latest version.
• Temporarily disable unused hypervisors for testing.

Nested Virtualization (VM Users)

If running Windows inside another VM (Azure, VMware, VirtualBox), enable nested virtualization in the host environment.

Repair Corrupted System Files

Open Command Prompt (Admin) and run:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Restart after completion.

FAQs

Does WSL require Hyper-V?

WSL2 requires Hyper-V virtualization to run its virtual machine, while WSL1 runs without Hyper-V but has limited performance and features.

How do I check if virtualization is enabled on my PC?

Open Task Manager → Performance → CPU and check whether Virtualization shows Enabled; if it shows Disabled, enable Intel VT-x or AMD-V in BIOS.

Can VirtualBox and WSL run together on the same system?

Newer VirtualBox versions support Hyper-V, but conflicts and performance issues may still occur, so updating or temporarily disabling one platform can help.

Does Windows Home edition support WSL2?

Yes, Windows 10 (2004+) and Windows 11 Home support WSL2 when virtualization and required Windows features are enabled.

How do I switch between WSL1 and WSL2?

Run wsl --set-version <DistroName> 1 to switch to WSL1 or wsl --set-version <DistroName> 2 to switch back to WSL2 in PowerShell.

Can Windows Core Isolation block WSL virtualization?

Yes, Memory Integrity under Core Isolation can block virtualization drivers and prevent WSL2 from starting correctly.

Can antivirus software block the HCS service?

Yes, some antivirus or endpoint security tools can restrict virtualization services and prevent the HCS service from starting.

The HCS_E_SERVICE_NOT_AVAILABLE WSL error usually occurs when virtualization services, hypervisor launch settings, or WSL components fail to initialize correctly. By enabling required features, updating WSL, verifying BIOS virtualization, and validating hypervisor launch settings, most systems recover without requiring a full Windows reinstall.

This guide has been updated for the latest Windows 11 cumulative updates and WSL improvements.

If the error continues, check Microsoft’s WSL GitHub issues or leave a comment below for further troubleshooting.