Wslregisterdistribution failed with error 0x80370114 windows 11

Если вы сталкиваетесь с ошибкой WslRegisterDistribution 0x80370114 в Windows 11 есть несколько решений, которые вы можете попробовать решить эту проблему. Эта ошибка обычно возникает, когда служба Hyper-V блокируется во время установки дистрибутива Linux с помощью инструмента Windows Subsystem for Linux (WSL). В этой статье мы собрали и подготовили все возможные решения этой проблемы. Используйте расширенные инструкции или автоматизированные инструменты для решения проблем в Windows 11. Вот несколько шагов, которые вы можете предпринять для решения проблемы:

Решение 1. Включите подсистему Windows для Linux (WSL)

В большинстве случаев пользователи не могут использовать WSL, потому что эта функция была автоматически отключена при обновлении до Windows 11. Решением в этом случае является повторное включение этой функции вручную. Вот шаги:

1. Тип Включение или выключение функций Windows в Start строка меню и щелкните Открытые.
2. Прокрутите вниз и найдите Подсистема Windows для Linux и поставьте галочку напротив него.
3. Нажмите OK для завершения изменений.

Решение 2. Включите платформу виртуальных машин и Hyper-V

Если первое решение не работает, вы можете попробовать включить платформу виртуальной машины и функции Hyper-V. Вот шаги:

1. Открытые Безопасность Windows.
2. Открытые Управление приложениями и браузером.
3. Нажмите Настройки защиты от эксплойтов внизу.
4. Переключитесь на вкладку Настройки программы меню.
5. Прокрутите вниз и найдите vmcompute.exe.
6. Нажмите Редактировать.
7. Прокрутите вниз до Защита потока кода (CFG).
8. Изменить Переопределить системные настройки в On.
9. Нажмите OK.
10. Включите Платформа виртуальных машин функцию, введя следующую команду в PowerShell запрос с правами администратора: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux.
11. Включите Hyper-V, функцию, введя следующую команду в PowerShell запрос с правами администратора: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All.

Решение 3. Восстановите или переустановите приложение дистрибутива Linux

Иногда ошибки Windows 11 WSL могут возникать из-за ошибки в установленном дистрибутиве Linux. Чтобы решить эту проблему, вы можете перезапустить приложение WSL и повторить попытку. Вот шаги:

1. Откройте приложение Start меню и найдите свое приложение дистрибутива Linux, например Ubuntu.

Решение 4. Удалите обновления

Если вышеуказанные решения не работают, вы можете попробовать удалить обновления. Вот шаги:

1. Открытые Настройки.
2. Нажмите Обновление и безопасность.
3. Нажмите Центр обновления Windows.
4. Нажмите Просмотр журнала обновлений.
5. Нажмите Удалить обновления.
6. Выберите обновление, которое хотите удалить, и нажмите Удалить.

Решение 5. Проверьте наличие вредоносных программ

Если вы все еще сталкиваетесь с ошибкой WslRegisterDistribution 0x80370114, вы можете проверить свой компьютер на наличие вредоносных программ. Вот шаги:

1. Открытые Безопасность Windows.
2. Нажмите Защита от вирусов и угроз.
3. Нажмите Параметры сканирования.
4. Выберите Полная проверка и нажмите Сканируй сейчас.

Вы можете использовать Защитник Windows по умолчанию или попробовать установить более продвинутый антивирус, разработанный Malwarebytes — надежной и талантливой группой экспертов, постоянно обновляющих свое программное обеспечение для борьбы как с локальными, так и с глобальными угрозами. Вы можете загрузить его сейчас, используя ссылку ниже, и получить 14-дневную пробную версию совершенно бесплатно. Он доступен для Windows 11, 10, 8.1, 8 и 7.

Главное окно Malwarebytes

Настройки Malwarebytes

Результаты сканирования Malwarebytes

Скачать Malwarebytes

Заключение

Если ни одно из вышеперечисленных решений не работает, вы можете проверить наличие дополнительных решений на форуме сообщества Microsoft или других онлайн-ресурсах. Некоторые пользователи сообщают об успешном отключении Control Flow Guard или восстановлении функции Virtual Machine Platform. В заключение, ошибка WslRegisterDistribution 0x80370114 в Windows 11 может быть неприятной, но есть несколько решений, которые вы можете попробовать решить эту проблему. Выполнив шаги, описанные выше, вы сможете решить проблему и использовать WSL должным образом.

It’s normal to encounter error messages on your device; they usually signal that something needs fixing. They may point towards blocked processes or hardware issues.

This article delves into the Windows Subsystem for Linux (WSL) tool and a frequent error it presents, particularly on Windows 10/11 – “WslRegisterDistribution Failed with Error: 0x80370114.”

Let’s explore this error message and understand its potential solutions.

What Is the Windows Subsystem for Linux?

To understand this error, let’s first familiarize ourselves with the Windows Subsystem for Linux, also known as WSL.

The Windows Subsystem for Linux is a tool that allows developers to run a Linux platform on a Windows device. With the WSL, developers can select their favorite Linux distributions from the official Microsoft Store. They can also execute some command-line commands and tools, including sed, awk, and grep.

In addition, the WSL tool lets developers run Linux applications on Windows and run Bash shell scripts in command-line programs.

To install the WSL tool on Windows, you must do the following:

Step 1: Enable the WSL Tool

First, you have to enable the Windows Subsystem for the Linux feature for the tool to run on Windows. To do this, launch the PowerShell with administrator privileges. And then, execute this command: dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart. Once done, restart your computer.

Step 2: Install Your Choice of Linux Distribution

First, open Microsoft Store and choose a Linux distribution. Options include:

• Ubuntu
• openSUSE Leap 42
• SUSE Linux Enterprise Server 42
• Kali Linux
• Debian GNU/Linux

After picking, click it and you’ll be directed to its page. Click the ‘Get’ button to start installation. A console window pops up during the first installation, asking you to wait for file decompression. Future installations should be quicker.

Make sure the Hyper-V Host Compute service is running to avoid the ‘WslRegisterDistribution failed with error: 0x80370114’ error.

What Is the WslRegisterDistribution Failed Error in Windows 10/11?

The error ‘WslRegisterDistribution failed with error: 0x80370114’ typically occurs when the Hyper-V service is blocked during a Linux distribution installation using the WSL tool. It usually comes with the complete error message, “Error: 0x80370114 The operation could not be started because a required feature is not installed.”

When you see the error, you are likely not able to access the WSL command-line tool.

What Triggers the ‘WslRegisterDistribution Failed’ Error in Windows 10/11?

As mentioned, this error appears if the Hyper-V service is blocked during the installation of a Linux distro using the WSL tool. However, there are instances when it shows because of the absence of an essential supporting Windows 10/11 feature.

Basic Fixes for the ‘WslRegisterDistribution Failed’ Error in Windows 10/11

The following fixes may take a bit of time to implement. But before you try them, reboot your computer first. There are times when all your computer needs is a quick reboot. You might be surprised to find that the error disappears after a reboot. This is especially true if you haven’t shut down your computer for a while.

Now, if you think you are suffering from a more complicated error that you cannot reboot normally, consider other advanced reboot options. After you reboot and you see the problem persists, troubleshoot!

To troubleshoot the problem, you will need to enable the Windows Subsystem for the Linux feature first. And to do so, there are two methods.

Method #1: Enable the Windows Subsystem for Linux Feature via the Turn Windows Features On or Off Option

To enable the Windows Subsystem for Linux feature via the Turn Windows Features On or Off option, search for the option using the search field. From the list of results, tick the option next to Windows Subsystem for Linux. Hit OK to proceed.

At this point, your system will find and install all the required system files. Once it is done, it will ask you to restart your computer. After your computer has restarted, there should be no more problems.

Method #2: Use the Windows PowerShell

Another way to troubleshoot the problem is by using Windows PowerShell. For this method to work, you need to open the Windows PowerShell with administrator privileges. And then, input the following command to enable the WSL feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux.

After entering the command, your system will then begin searching and installing all the required system files. When asked, input Y to restart your computer.

How to Fix the WslRegisterDistribution Failed Error in Windows 10/11

Now, if the above troubleshooting methods don’t work, then proceed with the fixes we have listed below.

Fix #1: Unblock the Hyper-V Host Compute Service

To unblock the service, you have to check first if you are using an antivirus solution. If you are using Windows Defender, proceed by doing these steps:

1. Into the search field, input windows security. Hit Enter to launch the Windows Security window.
2. Go to the App and Browser Control section.
3. Click Exploit Protection Settings.
4. Navigate to the Program Settings tab.
5. Find the Hyper-V Host Compute service by going to this path: C:\WINDOWS\System32\vmcompute.exe.
6. Select the service and click on the Edit button.
7. Find the Code Flow Guard (CFG) section and untick the Override System Settings option.
8. Next, open Windows PowerShell with administrator privilege.
9. Execute this command: net start vcompute.

It is worth noting that the App and Browser control under Windows Security plays a vital role in your PC. It protects your device from threats and potentially dangerous, files, downloads, apps, and websites. So, be sure that it is not disabled. If needed, you can just add an exception so other programs that depend on it can run as expected.

Fix #2: Restart the Lxss Manager Service

Another service that is associated with the WSL is the Linux Instance Life Cycle service. It runs in the background to somehow keep things in control. But if this service is blocked or is experiencing problems, then you can encounter the error. In this case, restarting the service can resolve the glitch.

To restart the service, here’s what you should do:

1. Press the Windows + R keys to launch the Run dialog box.
2. Input services.msc into the text field and hit OK.
3. From the list of services, find the LxssManager service and restart it.
4. Once done, relaunch the WSL tool and check if the error message is gone.

Fix #3: Launch the WSL tool from Microsoft Store

There are cases when the Linux distribution you installed has a bug, resulting in an error upon launch of the WSL tool. The good thing is that it can be easily cleared by relaunching the WSL app directly from the Microsoft Store’s interface.

For a detailed guide on what to do, follow these steps:

1. Go to the Taskbar and click the Windows Search field.
2. Here, type Microsoft Store and hit Enter.
3. A list of results will be displayed on your screen. Click on the most relevant result.
4. In the upper-right corner of the window, click the three-dotted menu.
5. Select My Library.
6. Navigate to the left pane of the window and click Installed.
7. Next, go back to the right pane and choose your Linux Distribution app.
8. Click the Launch button and see if the problem is resolved.

Fix #4: Update the Linux Terminal via Command Prompt

If you are running an older version of the distribution, then you may likely encounter the error. But again, this can be fixed. Updating the app will do the trick.

To update your Linux distribution, use the Command Prompt. This way, you don’t need to reinstall the application. Here’s a guide on what to do:

1. Go to the Taskbar and click the Windows Search field.
2. Input Command Prompt and hit Enter.
3. In the list of results, right-click on Command Prompt.
4. Select Run as Administrator.
5. Next, input the following commands into the command line. Make sure to hit Enter after each command:
   • C:\> bash
   • $ sudo apt-get update
   • $ sudo apt-get dist-upgrade
   • $ <CTRL-D>
   • C:\> exit
6. Now, launch the WSL tool to see if the error has been cleared.

Fix #5: Repair the WSL App

If nothing has worked so far, then it is possible that the error is caused by a corrupt installation of the WSL app. To repair this, use the Repair feature of Windows.

Here’s how:

1. Right-click on the Windows button and select Settings.
2. Go to Apps.
3. Find and click on the WSL application.
4. Select Advanced Options.
5. Scroll down and find the Repair button.
6. Once the app is repaired, check if the error is fixed. Otherwise, go back to the Advanced Options section.
7. And then, click the Reset button. Take note that this action will cause you to lose your data and other settings.
8. Relaunch the app and see if the error is cleared.

Fix #6: Reinstall the WSL Application

If repairing the app has not fixed the problem, then the damaged module of the app must have incurred so much damage that the repair process can no longer fix it. For this, you need to manually uninstall the app and reinstall it again.

Follow these steps:

1. Right-click on the Windows button and select Settings.
2. Find the WSL application and choose Uninstall.
3. Once it is uninstalled, disable the Subsystem for Linux option and restart your device.
4. Upon restart, try to enable the Subsystem for Linux option once again.
5. And then, reinstall the WSL app. Hopefully, this will fix the problem.

Fix #7: Reset Your Windows PC

Microsoft provides a reset feature for Windows 10 and Windows 11 users. Doing this will return your operating system to the way it was when it was accessed the first time, meaning any third-party applications are no longer present.

Performing a Windows 10/11 reset gives your computer a fresh start. This is a handy solution if you’re facing a software-related issue that you can’t seem to resolve.

There are two ways to reset Windows 10/11. Refer to the sections below.

Method #1: Reset Windows from Within

If you can successfully log in to Windows, then resetting it would be a straightforward process. Just follow these steps:

1. Go to the Start menu.
2. Select Settings.
3. Navigate to Update and Security and select Recovery.
4. In the right pane, go to Reset This PC and click Get Started.
5. You have two options at this point: Keep My Files and Remove Everything. If you plan to choose the second option, be sure that you have already created a backup of your important data as they will be lost in the succeeding steps.
6. If a warning appears, just click Next.
7. In the window that appears, review the particulars of the action you will be doing. If you are happy with them, click the Reset button. This will initiate the reset process.
8. The process will take a few minutes to complete. Also, your computer will restart several times along the way. The moment you see a screen that gives you three options, select one and hit Continue.

Method #2: Reset Windows 10 or Windows 11 without Logging In

If you are unable to log in to your Windows 10/11 account, you still have another way to reset your device: Use the Boot Options menu. This menu will appear automatically if your device fails to boot properly two to three times consecutively. But if it doesn’t, you can call it up by pressing the Shift and Power button. And then, click Restart. Once your device reboots, you will see the Boot Options menu. From here, you can proceed with performing a Windows 10/11 reset.

Here’s how to proceed:

1. Click the Troubleshoot
2. Select Reset This PC.
3. Follow steps 6 to 8 from the previous method, then wait for your device to restart and complete the reset.
4. When asked to select one of three options after your device has been reset, select Continue.

Fix #8: Perform a Clean Install of Windows

Before you can proceed with performing a clean install of Windows 10/11, make sure that you meet the following requirements first:

• 1 GB RAM for 32-bit and 2 GB for 64-bit
• 1 GHz processor or faster
• 20 GB free hard drive space
• 800 x 600 display
• DirectX 9 Graphics Processor
• Stable Internet Access
• A valid Microsoft account

To perform a clean install, you have to consider a few things first. If you have downloaded the Windows 10/11 ISO file, but plan to install it on another computer, you can do so by using a DVD or a USB. To start, you should have a flash drive that has at least 4 GB of free space. If you are planning to use a DVD, make sure that the computer where you will be installing the OS has an optical drive.

Once you have all these requirements, you can proceed with creating a bootable drive. Insert the USB into your computer and load the burner software program of your choice. Follow the on-screen instructions to create the bootable disk. And then, choose a drive and find the ISO file you have downloaded. The process will then start and it should take around 10 to 15 minutes to complete.

After creating a bootable media device, install it on the computer. Insert the DVD or USB and switch off the computer. Next, switch it back on and hit the F2 or F12 button to access the BIOS boot menu. Here, select where your PC will boot from. Select your bootable drive. Follow the instructions from here.

Fix #9: Conduct a Malware Scan

There are times when malware entities or viruses successfully infiltrate your system and affect important system processes or disable vital services. If that happens, you may encounter error messages like ‘WslRegisterDistribution Failed with Error 0x80370114’.

So, make it a habit to perform regular malware scans to protect your device against threats. Luckily, you don’t have to stress yourself out looking for the perfect malware scanner out there. You can use Windows 10/11’s in-built malware scanner: Windows Defender.

Here’s how to use it.

1. Launch the Windows Security settings.
2. Choose Virus and Threat Protection.
3. Select Scan Options.
4. From here, click Windows Defender Offline Scan.
5. Hit the Scan Now button.
6. The scan will take about 15 minutes to complete. After that, your device will restart.
7. Once the scan is done, view the results by opening Windows Security Settings. Select Virus and Threat Protection, and then click Protection History.
8. Follow the recommended actions.

If you feel that the initial scan was not sufficient, you can conduct an additional scan using a reputable third-party antivirus program.

Simply download an antivirus program of your choice and launch it. Again, perform a scan and remove the malware to keep your device protected against threats.

Fix #10: Use the System File Checker

The System File Checker is a tool that allows Windows users to scan and restore damaged corrupted system files that trigger errors on the Windows 10/11 platform. To use it, do the following:

1. Press the Windows + X keys to launch the main menu.
2. Select Command Prompt (Admin) to launch Command Prompt with administrator rights.
3. In the command line, enter the sfc /scannow command and hit Enter.
4. The repair process should now start. Make sure you don’t close the window or interrupt the process.
5. Once the scan is complete, restart your computer.

Fix #11: Free Up System Space

In some cases, the error message appears because there is no enough space on your drive, so the system cannot complete the process. One way to deal with this problem is to free up space on your drive.

For this, you can use the Disk Cleanup tool which is built-in on most Windows 10/11 devices. To use it, follow these steps:

1. Click the Start menu.
2. Go to All Programs.
3. Select Accessories and click System Tools.
4. Choose Disk Cleanup.
5. Under the Files to Delete section, select all file types that you want to remove.
6. Once you have made a choice, hit OK.

You could also manually free up system space by examining your folders one by one, though this could be time-consuming. We suggest that you use the Disk Cleanup tool or a third-party PC repair tool.

Fix #12: Ask for Professional Help

If you have done everything but nothing seems to work, then do not be afraid to ask for help. Experts will always be willing to lend you a helping hand.

You can reach out to the support team of Microsoft through their website and inquire about a solution tailored to your needs. If you require an urgent fix, consider seeking help from professionals in your area. They can handle the error on your behalf, saving you time and effort.

Wrapping Up

Understanding the Windows Subsystem for Linux tool can be beneficial, even if it’s mainly used by developers. Being aware of its common errors, such as WslRegisterDistribution Failed with Error: 0x80370114, and their solutions is crucial.

In case you encounter this issue, try basic troubleshooting: activate the Windows Subsystem for Linux via PowerShell or Windows Features. If unsuccessful, other fixes include unblocking the Hyper-V Host Compute Service, restarting the Lxss Manager, launching WSL from Microsoft Store, updating the tool via Command Prompt, reinstalling WSL, or resetting Windows.

Should these attempts fail, don’t hesitate to contact Microsoft’s support team or visit a certified service center. We’d love to hear your thoughts or any other solutions for the WslRegisterDistribution error in the comments below!

I am facing almost exactly the same issue.

Microsoft Windows 11 [Version 10.0.22000.675]
wsl --status
Default Version: 2
WSL version: 0.58.3.0
Kernel version: 5.10.102.1
WSLg version: 1.0.33
MSRDC version: 1.2.2924
Direct3D version: 1.601.0

I have been running Debian and Ubuntu in WSL normally for several months.
Both working just fine for a long time.
But since a few days ago, I could not start any distro.

So I checked all services and event logs and I think I have narrowed it down to:

The service vmcompute can not be started.

I have tried everything I could come came across as a solution, but I could not figure out the problem.
The WSL and distros that used to work a few days ago would not start, the only service that would not start was vmcompute, and I tried every troubleshooting advice to start the service, but I could not find a solution.

So I have uninstalled everything WSL related, deleted all the distros, disabled Hyper-V, Virtual Machine Platform, Windows Subsystem for Linux from Windows Features, and reenabled them, uninstalled and reinstalled WSL, rebooted several times and tried to reinstall WSL and Debian.

And, just in case, have run:

Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase
Dism.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow
chkdsk /scan

Also, configured CFG for vmcompute in Exploit Protection.
And done everything I had done the last time to install WSL and Debian (or any distro whatsoever).

Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

All the associated services are set to auto start:
LxssManager, HvHost, AppVClient, WslService, vmcompute.

And all of the above are starting and behaving normally, except vmcompute.
vmcompute does not start, with the following errors in console:

The Hyper-V Host Compute Service service could not be started.
A system error has occurred.
System error 50 has occurred.
The request is not supported.

And the following 2 errors in the event viewer log:

The Host Compute Service failed to start:  The request is not supported.  (0x80070032)
The Hyper-V Host Compute Service service terminated with the following error:  The request is not supported.  

And any distro installation fails with 0x80370114.

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

Any ideas?
Thanks in advance

Screenshots:

In this article, we will see how to solve WslRegisterDistribution failed with error: 0x80370114 if you are also getting this error in your System. Sometimes when you are trying to install Linux on WSL then you might have observed this WslRegisterDistribution failed with error: 0x80370114. This error usually occurs when Hyper-V service is blocked during the linux installation. Without Hyper-V service up and running, linux installation won’t start. There could be few reasons for Hyper-V service not running in your System. We will see all those reasons along with the steps to solve the error.

Also Read: Solved: ‘VBoxManage’ is not recognized as an internal or external command

So in my case when I tried installing Ubuntu 20.04.5 LTS, I ended up in having WslRegisterDistribution failed with error: 0x80370114 as you can see below.

Above error could occur due to multiple reasons, one of the most frequent reason is that Hyper-V is currently not enabled in your System. This means Hyper-V Host Compute Service, aka vmcompute.exe which is responsible for making Hyper-V service up and running is currently not enabled. Along with this, Virtual Machine Worker Process, aka vmwp.exe which is responsible for running the instances in Hyper-V hosts is also not enabled. So here we are going to enable both the features using CLI mode and then we will verify the enabled feature in Program settings.

Step 1: Enable Feature

In the first step, you need to enable Microsoft Windows Subsystem feature. To enable this feature, open CLI terminal in administrator mode and run dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart command as shown below.

C:\>dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19044.2486

Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.

Next, you need to enable another feature called VirtualMachinePlatform using dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart command as shown below.

C:\>dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19044.2486

Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.

After that restart your system once. Once restarted, go to Step 2 to verify the enabled feature.

Step 2: Verify Exploit Protection Settings

You need to first search Windows Security in the search bar as shown below. Once it shows up, tap on it to open.

Next, you need to go to App & browser control as highlighted below. Please do not click on Turn on if you don’t want to turn it on. You just need to click on below highlighted area to go inside the settings.

Next you need to click on Exploit protection settings under Exploit protection as highlighted below.

Under System settings Control Flow Guard (CFG) should be «On» by default and under Program settings, you need to make sure both vmcompute.exe and vmwp.exe are available with Control Flow Guard set to below.

• Override System Settings
• On
• Use Strict CFG

After validating the programs under system settings and program settings, if you now try to start Ubuntu 20.04.5 LTS again, you will notice that it will start successfully as shown below.

If after following above steps, you are still getting the same error then you need to check your default WSL version. You need to set your default WSL version to 2 and then restart the system one more time to see if it now fixed the issue.

C:\>wsl --set-default-version 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The operation completed successfully.

Hope above given solution should be enough to fixed your error. Please let me know your feedback in the comment box !!