• Skip to main content
  • Skip to primary sidebar
  • Skip to footer
  • Home
RANTS.TECH

RANTS.TECH

My Rants and Experiences Shared

You are here: Home / Uncategorized / Fix: WslRegisterDistribution failed with error: 0x80370102 and error 0x80070002

Fix: WslRegisterDistribution failed with error: 0x80370102 and error 0x80070002

27th June 2020 by Johann 9 Comments

After struggling with this issue for days

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370102
Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.

Press any key to continue...

including a re-installation of windows 10 (twice) and trying everything on the windows forums, like :

bcdedit /set hypervisorlaunchtype autodid

Setting and re-setting Virtual machine platform, Hyper – V and Windows Subsytem for Linux

image

Rebooting after each setting, and a myriad of other things, the problem turned out to be a setting in the BIOS.

No it had nothing to do with Intel Virtualisation being disabled in the BIOS as many forums suggest, this has been enabled since day one.

The problem was that I had  Limit CPUID Max enabled in the BIOS. This NEEDS TO BE DISABLED for the WSL 2 to work correctly, apparently. I have no clue why or how but this is what solved it for me !

On the other hand if you encounter error 0x80070002, The most likely culprits are either Docker for Desktop or some vpn software messing up network settings. Uninstalling Docker solved the issue for me.

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070002
Error: 0x80070002 The system cannot find the file specified.

Press any key to continue...

Please let me know in the comments below if this solves the issue for you too

Share this:

  • Twitter
  • Facebook

Filed Under: Uncategorized, Windows 10, WSL Tagged With: Windows 10, Windows subsystem for Linux

Reader Interactions

Comments

  1. Feodor says

    1st November 2020 at 16:42

    Very big thanks, i enable virtualisation in BIOS (have no idea why Gigabyte turne it off)

    Reply
  2. Alexander Kokkinos says

    16th November 2020 at 16:32

    I changed wls version from 2 to 1, so:
    1. Type on Powershell wsl –set-default-version 1
    2. Re-open the Ubuntu app you have downloaded from the store.
    Hope it works for you as it did for me

    Reply
    • anonymous431 says

      3rd December 2020 at 06:50

      Thank you very much! I was trying to find a solution to this for a long long time and you help a crap ton!

      Reply
    • boyan says

      8th February 2021 at 19:52

      Took me a lot of time to realize that WSL needs a processor supporting SLAT. My old desktop is not supporting it so I’ll have to use WSL 1 while my laptop gets repaired.
      Unfortunately this didn’t work. I’ve enabled Virtualization and followed the instructions on MS’ page (https://docs.microsoft.com/en-us/windows/wsl/install-win10#manual-installation-steps) without the update to WSL 2. Still the good old “WslRegisterDistribution failed with error: 0x80370102
      Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.”
      Any tips?

      Reply
    • Ridma Tharaka Basnayaka says

      22nd March 2021 at 13:21

      yes, it’s work. thank you

      Reply
  3. Rahul Amarwal says

    29th November 2020 at 17:33

    thanks man your way worked for me

    Reply
  4. T4K says

    25th January 2021 at 22:19

    you ABSOLUTE [email protected]!*$ng HERO!!!

    I, like you, went through every possible permutation of unticking and ticking the windows feature and rebooting after each one and reinstalling this that and the other. A few months ago I did not have an issue with the same PC/hardware but I recently reimaged my machine and got the latest build version and this issue was doing my bloody head in. That CPUID was the issue for me, not sure why I did not see your post when I was googling about for the exact error code I was just getting git-hub crap.

    Reply
  5. Ramon Barnes says

    18th February 2021 at 07:58

    We’re is this CPUID ID I have an older laptop and my bios doesn’t show that. I’m taking it this is only on the newer model computers.
    Pentium(R) Dual-Core CPU T4300 @ 2.10GHz 2.10 GHz
    64-bit operating system, x64-based processor

    HP laptop

    Reply
  6. Marcus says

    10th May 2022 at 13:20

    For my HP Pavilion (made in 2019), I found a setting in BIOS that mentioned “Virtualization” or similar, with a note that this needs to be enabled for Virtual Machine usage. Enabling that setting has fixed my problem.

    Thanks for your write-up, that showed me quickly what kind of thing I was looking for.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Search

More to See

Ubiquiti AP Led Schedule

8th April 2021 By Johann

How to dockerise a python application (Properly)

25th February 2021 By Johann

Tags

3d printer 3d printing arduino atmega 2560 automation Conditional Forwarding development DNS docker fasttrack geeetech IPSEC k8s kubernetes L2TP linux-monitoring marlin Migration MikrotTik python security Server Migration Shared Hosting Backup Simple Digital Clock ssh tunnel touchscreen ubiquity ubuntu VPN VPS VPS Backup Web Hosting webmin Web Server Backup wifi Windows 10 Windows 2003 Windows 2008 Windows 2016 Windows subsystem for Linux zabbix Zimbra

Footer

Recent Posts

  • Ubiquiti AP Led Schedule
  • How to dockerise a python application (Properly)
  • A Zero Component, Super Simple Minimalist Arduino Digital Clock
  • Upgrading a Creality Ender 3 / Ender 5 to Marlin 2.x

Search

Social

  • LinkedIn
  • Twitter