0x8007019e ubuntu как решить

Sorry, you have been blocked

This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.

What can I do to resolve this?

You can email the site owner to let them know you were blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page.

Cloudflare Ray ID: 7a6fceb79cf122f5 • Your IP: Click to reveal 88.135.219.175 • Performance & security by Cloudflare

Исправить WslRegisterDistribution не удалось с ошибками 0x8007019e и 0x8000000d

Скачайте и установите инструмент для ремонта здесь.

WSL или Windows Подсистема для Linux для Windows 10 это отличный инструмент для разработчиков. Но иногда он запускает код ошибки 0x8007019e или 0x8000000d при запуске командной строки. Хотя ошибка, по-видимому, связана с установкой WSL, это может быть ложным срабатыванием. У некоторых пользователей был установлен WSL, но они все еще сталкиваются с проблемой. Код ошибки:

Установка, это может занять несколько минут .
Сбой WslRegisterDistribution: 0x8007019e / 0x8000000d
Ошибка: 0x8007019e / 0x8000000d Параметр неверен.
Нажмите любую клавишу для продолжения.

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

Убедитесь, что подсистема Windows для Linux (WSL) включена.

1. Откройте панель управления
2. Программы и функции

Обновление за февраль 2023 года:

Теперь вы можете предотвратить проблемы с ПК с помощью этого инструмента, например, защитить вас от потери файлов и вредоносных программ. Кроме того, это отличный способ оптимизировать ваш компьютер для достижения максимальной производительности. Программа с легкостью исправляет типичные ошибки, которые могут возникнуть в системах Windows — нет необходимости часами искать и устранять неполадки, если у вас под рукой есть идеальное решение:

• Шаг 1: Скачать PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista — Microsoft Gold Certified).
• Шаг 2: Нажмите «Начать сканирование”, Чтобы найти проблемы реестра Windows, которые могут вызывать проблемы с ПК.
• Шаг 3: Нажмите «Починить все», Чтобы исправить все проблемы.

Использование командлета PowerShell

1. Включить WindowsOptionnel -Интернет-функциональность -ФункциональностьNameMicrosoft Windows Подсистема Linux
2. Перезагрузите компьютер при появлении соответствующего запроса.

CMD обходное решение

• Перейдите в меню «Пуск» и найдите подсказку.
• Или нажмите CTRL + R и введите cmd.

Отныне вы можете (в качестве обходного решения) запускать Kali Linux из командной строки. Конечно, это нежелательно, но это может быть временным решением.

Совет экспертов: Этот инструмент восстановления сканирует репозитории и заменяет поврежденные или отсутствующие файлы, если ни один из этих методов не сработал. Это хорошо работает в большинстве случаев, когда проблема связана с повреждением системы. Этот инструмент также оптимизирует вашу систему, чтобы максимизировать производительность. Его можно скачать по Щелчок Здесь

CCNA, веб-разработчик, ПК для устранения неполадок

Я компьютерный энтузиаст и практикующий ИТ-специалист. У меня за плечами многолетний опыт работы в области компьютерного программирования, устранения неисправностей и ремонта оборудования. Я специализируюсь на веб-разработке и дизайне баз данных. У меня также есть сертификат CCNA для проектирования сетей и устранения неполадок.

Fix: WSLRegisterDistribution Failed with Error: 0x8007019e

You may encounter the WSLRegisterDistribution Failed error due to the disabled subsystem for the Linux. Moreover, a corrupt installation of the Linux distro application may also cause the error.

The affected user gets the error when he tries to launch the Linux terminal with the following message:

WslRegisterDistribution failed with error 0x8007019e

Before proceeding with the troubleshooting process, try to launch the Linux console using the Windows Search bar (located on the Taskbar of your system), not by the bash.

Solution 1: Enable/Disable Subsystem for Linux

Windows has a feature “Subsystem for Linux” which is essential for the operation of your Linux distribution. If the said option is not enabled, then you may encounter the error at hand. In this case, enabling the option of the subsystem for Linux may solve the problem.

1. On the Taskbar, click on the Windows Search bar and type Control Panel. Then in the results shown, click on Control Panel. Open Control Panel
2. Now click on Uninstall a Program. Click Uninstall a Program in Control Panel
3. Then, in the left pane of the window, click on Turn Windows Feature on or off. Turn Windows Feature on or off
4. Now, scroll down till the end and enable Windows Subsystem for Linux Option. Enable Windows Subsystem For Linux
5. Then restart your system and then check if the system is clear of the error.
6. If the option is already enabled at step 4, then disable it and restart your system.
7. Upon restart, enable the Subsystem option and then restart your system.
8. Upon restart, check if the Linux distro is working fine.

Solution 2: Restart the LxssManager Service

Linux instance life cycle service i.e. LxssManager operates in the background to keep things under control. You may encounter the error at hand if the said service is stuck in operation or is in an error state. In this scenario, restarting the service may clear the glitch and thus solve the problem.

1. Press Windows + R keys to bring out the Run command box.
2. Now type Services.msc and then click on OK. Type “services.msc” into the Run dialog and press Enter
3. Now find and restart the LxssManager service. Restart Lxss Manager Service
4. Then relaunch the terminal to check if it is clear of the error.

Solution 3: Launch the Subsystem from Microsoft Store

Linux distribution has a bug, in which, sometimes the terminal starts to show the error at hand when launched from the shortcut/command prompt. This glitch can be cleared by launching the application directly from the Microsoft Store interface.

1. On the Taskbar of your system, click on Windows Search box and type Microsoft Store. Then in the list of results shown, click on Microsoft Store. Open Microsoft Store
2. Then, in the top right corner of the window, click on the horizontal Ellipses and then click on My Library. Open My Library in Microsoft Store
3. Now in the left pane of the window, click on Installed. Open the Installed Tab in My Library
4. Then in the right pane of the window, click on your Linux distro App.
5. Now click on the Launch button and then check if the issue has resolved. Launch the Linux Console Application from the Microsoft Store

Solution 4: Update the Linux Terminal by Using Command Prompt

You may encounter the error under discussion if you are using an older version of the distribution. In this context, updating the application may solve the issue. You can use the Command Prompt to achieve the same without reinstalling the application.

1. On the Taskbar of your system, click on the Windows Search box and type Command Prompt. Then in the results shown, right-click on Command Prompt and then in the sub-menu, click on Run as Administrator. Open Command Prompt from Windows Search
2. Now type the following commands in the Command Prompt and press the enter key after each command:
3. Now, launch the terminal to check if it is clear of the error.

Solution 5: Repair the Linux Terminal App

If nothing has helped you so far, then the issue may have been caused by a corrupt installation of the Linux distribution app. To overcome such corruption, the Repair feature of Windows Settings can be used which will then solve the problem.

1. Right-click on the Windows button and click on Settings. Open Windows Settings
2. Then tap on Apps. Open Apps in Windows Settings
3. Now, find and click on your Linux Distribution Application, e.g., if you are using Ubuntu, click on Ubuntu. Then click on Advanced Options. Open Advanced Settings of the Linux Distribution Application
4. Now, scroll down till the end and click on the Repair button. Repair the Linux Distribution Application
5. After repairing the distro, check if it is clear of the error.
6. If not, open Advanced Options (step 1 to 2).
7. Then, scroll down till the end and click on the Reset button (your data/settings will be lost). Reset the Linux Distribution Application
8. Now, launch the distro to check if it is clear of the error.

Solution 6: Reinstall the Linux Console Application

If the repairing of the Linux console has not solved the issue, then the corrupt module of the application is beyond repairing and you have to manually uninstall and then reinstall the application to solve the problem.

1. Right-click on the Windows button and click on Settings.
2. Now, find and click on your Linux Distribution Application, e.g., if you are using Ubuntu, click on Ubuntu. Then click on Uninstall. Uninstall the Linux Distribution Application
3. After uninstalling, disable the Subsystem for Linux Option (as discussed in solution 1) and restart your system.
4. Upon restart, enable the Subsystem for Linux (as discussed in solution 1).
5. Now install your Linux Console Application and hopefully, your issue has been resolved.

If nothing has worked for you, then you may have to Reset your Windows PC or perform a clean installation of Windows.

Installation Failed with Error 0x8007019e #2982

I have tried Repair, Reset and reinstall these two apps, but the problem is still there. Is there anything I can do to check the detail of the problem?

The text was updated successfully, but these errors were encountered:

I have collected some yesterday (if no mistake). However, ubuntu works again today. Sorry for I cannot reproduce it now.
detail.zip

@0NG Make sure Windows Subsystem for Linux is checked.

Yes, it was checked at first, since I have used WSL for a long time. When the problem occured but I couldn’t find any solution, I tried to uncheck it, test if ubuntu work, and then checked it again, but the problem was still there. I think it may not because of this Windows feature unchecked.

Yep somehow the WSL feature was disabled, that’s what error 0x8007019e means.

In case it helps someone, I had the same error despite having WSL checked.
Unchecking it, rebooting, checking it, rebooting again, and running Ubuntu install worked for me.

@krysjez Aha! Yes, it also worked for me! Just two weeks ago, the error came up again, and I solved it by the same steps.

Same issue here. The Windows Susbsystem for Linux feature was turned off. I guess that happened during a Windows update. However, I had another error : 0x800700b7. I could fix it by reinstalling the Ubuntu app from the store.

I am not so happy with this having been closed without any changes. Can’t we add a more descriptive error message which points the user into the right direction?

I have a similar scenario to @michellaevens except instead of a second error code, I get a GSOD — depending on the exact invocation means, it’s either a SYSTEM_SERVICE_EXCEPTION in hbflt.sys or a SYSTEM_THREAD_EXCPEPTION_NOT_HANDLED in fltmgr.sys
This has been happening for the last several slow ring builds, plus the official release on Monday.
Anyone else seeing the same thing?

It appears hbflt.sys is a BitDefender file-system filter, and there have been a couple of other reports (#1750, #2323) involving BitDefender. Those were usability issues instead of crashes, but possibly all related.

@Brian-Perkins — Aha — You are correct! Uninstalling BitDefender allowed WSL to run. I’ll work on seeing if there is an updated version of it available to get pushed out to our dev machines. Had been working until roughly mid-march builds, if I recall correctly.

In case this helps anyone else, I had this problem show up today after using WSL for months with no problems. I recently changed my startup to automatically open ConEmu on system boot. All I did to rectify this was to close all open terminals. I reopened ConEmu and now it seems to be working fine. Perhaps trying to open WSL too early in the boot process can cause this error.

The happened to me today. I have been using WSL daily, suddenly it does not work. The Windows feature is checked.

to: fix: uncheck the feature, reboot, check the feature, reboot.

I get the same error, but my linux subsystem is already installed and enabled.

This comes and goes on mine.

I get a same error in Win 10 1803. I am sad.

@benhillis Maybe this issue should be reopened?

@AnthonySteele this reminds me of The IT Crowd: «Have you tried turning it off and on again?»
But I must say. It worked! ��

I have seen a similar error a few more times, usually right after the machine was started up.
In those cases, I tried again 5 minutes later and it worked then. Without a re-install.

I think I’m the first person in this thread for whom unchecking and re-checking didn’t work. I’ve tried Ubuntu 18, OpenSuse and Debian

@SalamiArmy This didn’t work for me, too.
But after a while (and many windows updates) it works now without doing anything.

@0NG Make sure Windows Subsystem for Linux is checked.

Rebooting only after enabling worked for me:

Run as administrator:

Run as administrator:

Running the second line of this as Admin on PowerShell and then rebooting right afterwards also worked for me.

@0NG Make sure Windows Subsystem for Linux is checked.

This worked like a charm for me for now.

@JuKu Did you discover what the problem was?
I currently have the same issue

@0NG Make sure Windows Subsystem for Linux is checked.

Thanks man!! It worked

I had this error after WSL had crashed/frozen.

My wsl crashed after I had opened two Ubuntu wsl terminals and moved some files to its filesystem with file explorer. Afterwards I got this error everytime I opened WSL. I had used Ubuntu WSL previously for years. I hope to find out how to properly reproduce this.

I solved this problem by disabling and enabling the feature and then rebooting.

In case it helps someone, I had the same error despite having WSL checked.
Unchecking it, rebooting, checking it, rebooting again, and running Ubuntu install worked for me.

I have an issue of automatically unchecking wsl after restart. Error when restart: we couldn’t complete the features undoing changes..

In case it helps someone, I had the same error despite having WSL checked.
Unchecking it, rebooting, checking it, rebooting again, and running Ubuntu install worked for me.

I have an issue of automatically unchecking wsl after restart. Error when restart: we couldn’t complete the features undoing changes..

I think I’m the first person in this thread for whom unchecking and re-checking didn’t work. I’ve tried Ubuntu 18, OpenSuse and Debian

I have an issue of automatically unchecking wsl after restart. Error when restart: we couldn’t complete the features undoing changes..

In case it helps someone, I had the same error despite having WSL checked.
Unchecking it, rebooting, checking it, rebooting again, and running Ubuntu install worked for me.

Thank You So Much. This fixed my error

It’s helped for Me also, just checked it and restart pc.
I used UbuntuLTD20.4
Thx

Windows Subsystem for Linux is checked if is , uncheck and check again . then need to be restart in order to have LxssManager on Services.msc, then install Ubuntu app from ms store .

@0NG Make sure Windows Subsystem for Linux is checked.