Wslregisterdistribution failed with error 0x8007273f



Ошибка WSLregisterdistribution failed with error в терминале Linux

Подсистема Linux для Windows 10 может выдавать ошибку WSLregisterdistribution failed with error 0x8007019e, 0x800706be или 0x8000000d в терминале, после нажатия любой клавиши, терминал закрывается. Ошибка обычно возникает из-за отключенной функции подсистемы Linux в Windows 10. Также, этот компонент может быть поврежденным, и переустановка может исправить данную ошибку. Разберем, как исправить ошибку WSLregisterdistribution failed with error: 0x8007019e, 0x800706be, 0x8000000d.

1. Проверка подсистемы Linux

Откройте удаление программ через панель управление и нажмите слева «Включение или отключение компонентов Windows«. Найдите компонент «Подсистема Windows для Linux» и установите галочку, чтобы установить этот компонент и перезагрузите ПК.

Если он был уже установлен, то снимите галочку, нажмите применить, и перезагрузите ПК. После загрузки, включите обратно и снова перезагрузите.

2. Перезапуск службы LxssManager

Служба диспетчера экземпляра Linux может зависнуть и не работать корректно. Перезапуск данной службы может помочь исправить ошибку WSLregisterdistribution failed with error. Нажмите Win+R и введите services.msc,чтобы открыть службы. В службах найдите LxssManager, кликните по ней правой кнопкой мыши и выберите «Перезапустить«.

3. Обновить терминал Linux при помощи CMD

Если используете старую версию дистрибутива, то обновление приложения может решить ошибку «WSLregisterdistribution failed with error 0x8007019e или 0x8000000d«. Для этого запустите командную строку от имени администратора и введите ниже команды по очереди:

  1. C:\> bash
  2. $ sudo apt-get update
  3. $ sudo apt-get dist-upgrade
  4. $
  5. C:\> exit

Если выше команды не помогли, то обновим сам WSL, введите в CMD:

  • wsl.exe —update
  • Если обновления установились, то нужно перезапустить WSL, введите ниже.
  • wsl —shutdown

4. Переустановка приложения

Перейдите в «Приложения», выберите приложения Linux, которое выдает ошибку (Ubuntu, Kali и т.п.) и сбросьте его по умолчанию. Если сброс не помог, то удалите его полностью и установите заново.

Источник

WSL not working after update from Microsoft store

Version
Microsoft Windows [Version 10.0.19044.1586]

WSL Version
WSL 2

Kernel Version
5.10.16

Distro Version
Ubuntu20.04LTS

Other Software
Docker Desktop (Windows), version 4.6.1 (76265) Docker Engine v20.10.13

Repro Steps I already had WSL installed from Microsoft Store few days and it was working fine. I got an update about the WSL from Microsoft Store and I updated it then it stopped working.

Expected Behavior bash shell. Windows Subsystem for Linux is already installed so it should operate normally.

Actual Behavior Hello I had successfully installed WSL few days ago and everything was working fine. But after the I got an update regarding WSL from Microsoft Store I updated WSL and since then it is throwing this error. I also restarted the computer and checked to make sure my Virtual Machine Platform and Windows Subsystem for Linux are ON and I found out that both of these services were already ON. still I get the same error. May I please get any guidance on this one? as I have to use WSL for my educational purpose that would be really helpful thanks

Diagnostic Logs No response

5 Answers 5

A second possible answer based on the latest information. I cannot test this personally since I am not having the issue.

Please backup (using the steps I mention in my previous answer) before trying this.

  • wsl —shutdown (from PowerShell or CMD)
  • In Windows, run the Registry Editor
  • Find \HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Lxss
  • Find the key in there that has DistributionName of Ubuntu20.04LTS . Change the Ubuntu20.04LTS to Ubuntu-20.04 .
Читайте также:  Error get value from agent failed cannot connect to

In theory, that may fix the problem by changing the distribution name back to what it should be.

Update: This answer was my first attempt at the solution (which does work), and the «safe» way of doing it. However, the «quick and easy» (but less «safe») registry edit that I posted as a second answer appears to be working for multiple users as well. This answer contains the background on the problem and why both of these techniques work for correcting it.

From reading through several Github issues (including, from the looks of it, one that you posted there), this appears to be a problem with the recent Store update of the Ubuntu app. The ubuntu.exe or ubuntu2004.exe (edit: I now believe this only happens with ubuntu2004.exe , but please let me know if you experience this on the ubuntu.exe version) is broken after update.

The ubuntu.exe command really does two things — It first checks to see if Ubuntu is installed in WSL. If not, it extracts the Ubuntu rootfs and asks you to configure a username and password. If it’s already installed, it launches WSL using that distribution.

The problem seems to have actually started in the previous version of the «Ubuntu 20.04» app in the Microsoft Store. The name of the distribution that is installed should be (historically), Ubuntu-20.04 . The previous version appears to have had a bug where this was renamed Ubuntu2004.LTS (thanks @Pat for pointing this out in the comments).

This would have caused a similar problem for all users that updated. However, it seems Canonical quickly pushed a fix for the issue.

Unfortunately, if you installed during that window where the «bad version» was in the Store, then the fix breaks things for you, because now:

  • ubuntu2004.exe is looking for a distribution named Ubuntu-20.04 .
  • It doesn’t find it (because your version is incorrectly named Ubuntu20.04LTS ), so it attempts to run the rootfs/configuration stage again. But the WSL files are already extracted and configured, leading to the error.

There are several options:

Personally, I’d just change any link to use the wsl.exe command instead of ubuntu.exe (or ubuntu2004.exe ). Assuming that Ubuntu is your default WSL distribution (found via wsl -l -v ), then will have the same effect and just launch it.Edit — It’s worthwhile to actually fix this.

From the Github reports, you can truly fix the issue by unregistering the Ubuntu distribution. Note that this is a destructive operation that will remove your existing Ubuntu distribution.

Assuming that the distribution still runs, via the wsl command, it is possible to back it up before unregistering, then restore it afterwards.

I would do this in two steps:

First, create a backup of the distribution via the wsl —export command. Exit the distribution, then go to PowerShell and:

Second, find the virtual drive for your Ubuntu WSL distribution. Start in File Explorer with:

Читайте также:  Lonic zip badcrcexception crc error terraria

Then find the CanonicalGroupLimited. Ubuntu (the name may vary.

Inside that, find ..\LocalState\ext4.vhdx . Copy that file to a safe location.

With two different backups in place, it’s time to unregister Ubuntu from WSL. Remember that this is a destructive operation:

Rerun the ubuntu2004.exe or ubuntu.exe (either from the command-line or the Start menu)

Ubuntu will again run its installation and initial configuration (and it should now work with the «bad» version unregistered). While you can enter a username and password here, we’re just going to throw this «installation» away anyway.

Exit the Ubuntu distribution

Copy the ext4.vhdx that you saved above back into %userprofile%\AppData\Local\CanonicalGroup. Ubuntu. \LocalState over the newly created one.

Источник

«An address incompatible with the requested protocol was used» error when trying to upgrade distro to WSL2 #5215

Comments

chraaroe commented May 15, 2020

Your Windows build number:
Microsoft Windows [Version 10.0.19041.264]

What you’re doing and what’s happening:
I followed the guide to upgrading to WSL2. No errors observed in following the official guide.

I now have an Ubuntu distro which I want to upgrade to WSL2. By Issuing the wsl —set-version Ubuntu 2 command I immediately receive the following error:

The distro works just fine. No issues to report on that front.

I have set the WSL default version to 2. If I then try to register a new distro, e.g. Alpine WSL from the Microsoft Store, I get the following error:

If I switch the default version back to 1 and try to register Alpine again I get the following:

Before being allowed to set up my user.

What’s wrong / what should be happening instead:
Unable to upgrade current distros to WSL2 nor install new distro with default version set to 2. Running current WSL1 distros works just fine as well as registering new distro with version 1.

For WSL launch issues, please [collect detailed logs]:
I’m unable to attach any detailed logs — all of the 3 commands to start the logging return the following error:

I’ve made sure to check it in both PowerShell and a old-school cmd prompt. I’m sure that they are both run with administrator privileges.

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

Источник

Wslregisterdistribution failed with error 0x8007273f

Microsoft Windows [Version 10.0.19043.1083]

WSL Version

Kernel Version

Distro Version

Ubuntu 20.04 LTS

Other Software

Repro Steps

  • Virtual Machine Platform active
  • Windows Subsystem for Linux active
  • Virtualization activated in BIOS

wsl —set-default-version 2

Open Windows Store, get and install Ubuntu 20.04 LTS. Start Ubuntu

Expected Behavior

The installation process as it should be.

Actual Behavior

This error occurs out of nowhere. 🙁

Diagnostic Logs

Created at 3 weeks ago

Same for me, but with Debian.

Win Version 21H1 (Build 19043.1081)

Tried removing Linux Subsystem, removing those features but no luck at all.

In my case I used the «Fix startup issues» in rescue mode due to an issue. After that, it was broken. Worked before without any issues.

Created at 1 year ago

I got same issue after update today. Trying to reinstall evrything but won’t helped.

Читайте также:  Engine error apex legends audio ship general russian patch

Created at 1 year ago

I got same issue after update today. Trying to reinstall evrything but won’t helped.

I just reinstalled Windows via Media Installer(from inside windows), while keeping all Apps and Data and it working again without doing anything further.

After a day of debugging with no findings that was the only viable solution for me (cost wise)

Created at 10 months ago

Judging by the error message, I suspect you may have some kind of AV software blocking the hvsocket address family.

Created at 1 year ago

Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it.

Created at 1 year ago

I got same issue after update today. Trying to reinstall evrything but won’t helped.

I have the same issue now (2021-07-20) after Microsoft support on twitter told me to update the windows store because i had this funny bug with the store https://twitter.com/bison_42/status/1416385301627408391 and now it doesn’t work anymore with the exact error message.

(its the same message but in german)

Created at 1 year ago

I just reinstalled Windows via Media Installer, while keeping all Apps and Data and it working again without doing anything further.

does it still work after you installed ALL new updates?

Created at 1 year ago

I just reinstalled Windows via Media Installer, while keeping all Apps and Data and it working again without doing anything further.

does it still work after you installed ALL new updates?

Yes it does work fine after installing the latest Windows Updates. Was required to due to IT security policy, so I had to find out!:)

Created at 1 year ago

Hello! Could you please provide more logs to help us better diagnose your issue? You can find instructions on how to attach logs here, please make sure to post the link to the Feedback Hub item in this chat so we can see it.

Created at 1 year ago

Sorry cant provide logs anymore, but in my case I had no anti virus installed and there wasn’t a vEthernet (WSL) adapter installed

Created at 1 year ago

I showed that a WSL 1.0 is currently installed, default installation version is WSL 2.

  • Installed Debian and started it —> error: 0x8007273f
  • Wanted to upgrade the WSL 1.0 to 2.0 —> «An address incompatible with the requested protocol was used.»

@benhillis No AV software other than the windows defender is installed.

Created at 1 year ago

I got same issue after update today. Trying to reinstall evrything but won’t helped.

I just reinstalled Windows via Media Installer, while keeping all Apps and Data and it working again without doing anything further.

can confirm now that this works without re-installing everything.
Windows re-install from a media installer (launching the setup from WITHIN windows and keeping all apps+data) is enough to make it work again (uninstalled all ubuntu versions before hand, maybe thats important?).
And BIG thanks @johnfriedrich

Источник

Оцените статью
toolgir.ru
Adblock
detector