WSL 2Troubleshooting guide
WSL 2 error 0x80370102 prevents a distribution from starting
WSL 2 error 0x80370102 prevents a distribution from starting.
Checked 2026.09.05Read guide ↗
SYMPTOM GUIDE
WSL, Hyper-V and virtualization will not start
Find WSL installation, Hyper-V and Windows Sandbox guides. Check the Windows edition, virtualization requirements and exact error before changing a Linux installation.
Choose the right starting point
- Use winver to record the Windows version and build.
- Check virtualization status in Task Manager under CPU.
- Back up the Linux environment before operations that remove it.
Guides for this symptom 7
General troubleshooting guides are distinct from reports of a known issue affecting a specific version. Check the conditions in each article.
Windows Subsystem for LinuxTroubleshooting guide
Restore the WSL optional component when error 0x8007019e appears
Restore the WSL optional component when error 0x8007019e appears.
Checked 2026.09.05Read guide ↗
WSL 2Troubleshooting guide
WSL alone cannot resolve names while a VPN is connected
WSL alone cannot resolve names while a VPN is connected.
Checked 2026.09.05Read guide ↗
Hyper-VTroubleshooting guide
Hyper-V is missing from Windows Features or cannot be enabled
Hyper-V is missing from Windows Features or cannot be enabled.
Checked 2026.09.05Read guide ↗
Hyper-V nested virtualizationTroubleshooting guide
WSL 2 or Hyper-V cannot run inside a Hyper-V virtual machine
WSL 2 or Hyper-V cannot run inside a Hyper-V virtual machine.
Checked 2026.09.05Read guide ↗
Windows SandboxTroubleshooting guide
Windows Sandbox is missing or cannot start
Windows Sandbox is missing or cannot start.
Checked 2026.09.05Read guide ↗
Windows SandboxTroubleshooting guide
Disable networking and clipboard sharing in Windows Sandbox
Disable networking and clipboard sharing in Windows Sandbox.
Checked 2026.09.05Read guide ↗