Software⏱️ 3 min read📅 2026-06-11

How to Fix 0x80370102 Error – WSL2 error 0x80370102 when trying to install ubuntu

WSL2 error 0x80370102 troubleshooting guide.

Quick Answer: Enable Hyper-V, SVM, and Virtualization Platform in Windows Features.

WSL2 error 0x80370102 is a frustrating issue that affects users trying to install Ubuntu on Windows 10. This error typically occurs when Hyper-V, a virtualization platform required for WSL2, is not properly configured or enabled.

Enabling and configuring Hyper-V can be complex, especially for beginners. In this guide, we will walk you through the steps to troubleshoot and resolve this issue.

⚠️ Common Causes

  • The primary cause of WSL2 error 0x80370102 is related to Hyper-V configuration. Specifically, if Hyper-V is not enabled or configured correctly, it can prevent WSL2 from functioning properly.
  • Another potential cause could be the presence of a conflicting virtualization platform, such as VirtualBox or VMware, which may interfere with Hyper-V's operation.

🚀 How to Resolve This Issue

Enabling and Configuring Hyper-V

  1. Step 1: Step 1: Open the Start menu and type 'Turn Windows features on or off' in the search bar. This will open the Windows Features window.
  2. Step 2: Step 2: In the Windows Features window, scroll down to the 'Virtualization Platform' section and check the box next to 'Hyper-V'. Click 'OK' to save changes.
  3. Step 3: Step 3: Restart your computer to ensure Hyper-V is properly loaded and configured.

Checking BIOS Settings

  1. Step 1: Step 1: Enter your computer's BIOS settings by pressing the key indicated in your motherboard manual (usually F2, F12, or Del).
  2. Step 2: Step 2: In the BIOS settings, navigate to the 'Advanced' or 'Virtualization' tab. Ensure that SVM (System Virtualization) is enabled.
  3. Step 3: Step 3: Save changes and exit the BIOS settings.

✨ Wrapping Up

By following these steps, you should be able to troubleshoot and resolve WSL2 error 0x80370102. Remember to restart your computer after making changes to Hyper-V settings or BIOS configuration. If the issue persists, consider seeking further assistance from Microsoft support or online forums.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions