When installing a distribution the process fails with: "WslRegisterDistribution failed with error: 0x800706be. #5768

IPlayZed · 2020-08-16T11:14:47Z

Environment

Windows build number: Win32NT 10.0.20190.0 Microsoft Windows NT 10.0.20190.0
Your Distribution version: Can not be verified, as distro does not launch due to installtion error.
Whether the issue is on WSL 2 and/or WSL 1: Can not be verified, as distro does not launch due to installtion error.

Steps to reproduce

Turn on Hyper-V in feature settings -> Turn on WSL in feature settings-> Restart -> Download some distro -> Launch distro.

WSL logs: https://aka.ms/AA99uko

Expected behavior

Distro should install on system.

Actual behavior

Installation terminates with error code 0x800706be.

IPlayZed · 2020-08-16T12:21:04Z

Update
It seems like this is a bug in the preview build.
The process worked flawlessly when rolled back to a previous build.

ajpeacock0 · 2020-08-16T19:59:37Z

Hitting same issue on Windows 10 Enterprise Insider Preview 20193. Launching Ubuntu fails with:

WslRegisterDistribution failed with error: 0x800706be
Error: 0x800706be The remote procedure call failed.

I tried disabling the WSL feature from "Turn Windows features on or off", rebooting, turning it back on with no success.

zanettea · 2020-08-17T14:53:39Z

I have the same issue. Looks like the lsxxmanager is crashing when the distro tries to install:

Faulting application name: svchost.exe_LxssManager, version: 10.0.20190.1000, time stamp: 0xb3740412
Faulting module name: lxssmanager.dll, version: 10.0.20190.1000, time stamp: 0xca1f91f1
Exception code: 0xc0000005
Fault offset: 0x000000000003192d
Faulting process id: 0x46e4
Faulting application start time: 0x01d674a49588d0e4
Faulting application path: C:\WINDOWS\system32\svchost.exe
Faulting module path: c:\windows\system32\lxss\lxssmanager.dll
Report Id: 5fa5be4b-5fc7-416c-bd17-24c6bc9d8f3e
Faulting package full name:
Faulting package-relative application ID:

yurividal · 2020-08-18T13:46:42Z

Same problem on Insider 20190

Loca123 · 2020-08-18T15:33:51Z

I'm also having this issue. I've only managed to get WSL2 working correctly on 1 of 3 machines so far. All running 20190.

camille-ryan · 2020-08-18T17:37:23Z

@Loca123 any ideas on what made it work on the one successful machine?

Duayt · 2020-08-18T18:49:34Z

I was able to resolve the problem by cleaning up some system file using disk cleanup together with the solution from GeorgeApostolopoulos1 in this link

copying from his suggestion:
Basically he reset a number of related services, while clearing out your temporary folder, eliminates this error. you can do this by making the following .bat file on your desktop and running from there:

net stop wuauserv
net stop Cryptsvc
ren %windir%\SoftwareDistribution sdold.old
ren %windir%\system32\catroot2 crt2old.old
net start wuauserv
net start Cryptsvc

Need to give GeorgeApostolopoulos1 the credit for this

yurividal · 2020-08-18T21:42:04Z

I was able to resolve the problem by cleaning up some system file using disk cleanup together with the solution from GeorgeApostolopoulos1 in this link

copying from his suggestion:
Basically he reset a number of related services, while clearing out your temporary folder, eliminates this error. you can do this by making the following .bat file on your desktop and running from there:

net stop wuauserv
net stop Cryptsvc
ren %windir%\SoftwareDistribution sdold.old
ren %windir%\system32\catroot2 crt2old.old
net start wuauserv
net start Cryptsvc

Need to give GeorgeApostolopoulos1 the credit for this

Unfortunately this did not work for me. Tried running theses commands manually, tried them in a .bat file, and also used disk cleanup to clean every cleanable bit. WSL still fails to install.

Loca123 · 2020-08-18T22:54:58Z

@Loca123 any ideas on what made it work on the one successful machine?

I've just noticed that it looks like virtualization might be off in the BIOS on the machine that has this error. Unfortunately it's remote so I'm not sure when I'll be able to get that enabled and see if it fixes anything. I'll update here after I've enabled it.

I've managed to get a second machine out of the three working properly now. That was actually a different issue, it was unable to connect to the internet. Running "Network reset" and adding "nameserver 8.8.8.8" to the resolv.conf seems to have fixed that one.

camille-ryan · 2020-08-19T05:02:34Z

The solution @Duayt linked did not work for me either. Also just enabled bios virtualization, and that didn't fix things for me either. Will be interesting to see if that fixes things for @Loca123

benhillis · 2020-08-20T04:46:23Z

Thanks for reporting, I have identified the issue and a fix is incoming. Change needs to make it to the rs_prerelease branch but I'm optimistic the first Insider Fast build in September will have the fix.

dudeisbrendan03 · 2020-08-20T14:44:13Z

Anything we can do in the meantime before the fix is out?

benhillis · 2020-08-20T14:54:34Z

I would roll back to the previous insider version.

aCoder2013 · 2020-08-22T04:21:11Z

Running this command solved it for me, insider preview 2004

wsl.exe --update

ghost · 2020-08-22T05:30:48Z

Running this command solved it for me
wsl.exe --update

This really worked for me, thank you @aCoder2013 . I'm currently on 20197 version which also had the same problem but everything works perfectly rn.

machug · 2020-08-22T06:13:55Z

Running this command solved it for me
wsl.exe --update

Can confirm this worked for me too, insider build 20197.

allanheller · 2020-08-22T10:21:50Z

Can confirm wsl --update worked for me also.

Version 2004 (OS Build 20197.1000)

tigerblue77 · 2020-08-22T12:23:06Z

I'm in 20197.1000

Exactly the same problem for me with Debian distro
@IPlayZed, I can confirm this is a bug in the preview build (20190)
The solution @Duayt linked did not work for me either
"wsl.exe --update" found an update, I did it, I rebooted, reopen Debian that didn't worked, reinstalled Debian, it didn't worked either...

ghost · 2020-08-22T20:22:52Z

I'm in 20197.1000

Exactly the same problem for me with Debian distro

@IPlayZed, I can confirm this is a bug in the preview build (20190)

The solution @Duayt linked did not work for me either

"wsl.exe --update" found an update, I did it, I rebooted, reopen Debian that didn't worked, reinstalled Debian, it didn't worked either...

Strange, it worked fine for me, (although, i'm installing on another drive other than C:) but i was able to get to set up my unix username and with windows terminal, it listed debian too along with ubuntu that i installed already before. i'm in 20197 too, btw

radday5 · 2020-08-23T01:10:39Z

Version 2004
OS. Build 20197.1000
wsl.exe --update
worked for me

tpjones-coder · 2020-08-24T17:08:33Z

Running this command solved it for me
wsl.exe --update
This really worked for me, thank you @aCoder2013 . I'm currently on 20197 version which also had the same problem but everything works perfectly rn.

Also worked for me too - thankyou @aCoder2013 - I'am on version 2004 20197.

voidiak · 2020-08-24T17:25:06Z

I have encountered this error too. I tried " wsl.exe --update", it updated, but it did not resolve the error. Suddenly I realized that I did not enable virtualization in bios. After I turn on the "SVM Mode" for AMD cpu, the error is gone now.

deepan-py · 2020-08-25T06:47:32Z

I encountered the same problem. Run the following commands this helped me sure it will help you too.
Run these commands in powershell

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

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

wsl --set-default-version 2

wsl.exe --update

wsl --shutdown

wsl <distribution_name>

keremnymn · 2020-08-25T15:51:18Z

Running this command solved it for me
wsl.exe --update
Can confirm this worked for me too, insider build 20197.

Thank you!!!

radovanobal · 2020-08-26T21:00:07Z

Running this command solved it for me
wsl.exe --update
Can confirm this worked for me too, insider build 20197.
Thank you!!!

Did not work for me on 20197

tpanj · 2020-08-26T21:59:53Z

On Microsoft Windows [Version 10.0.20201.1000] this helped

wsl.exe --update

doctordns · 2020-09-07T16:27:58Z

I have the same issue as @wpzero - running 20206 insiders build, ubuntu fails with the same error.
Tried adding Hyper-V, and other fixes. Still get the error when installing:

PS C:\Ubuntu> .\ubuntu2004.exe
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x800706be
Error: 0x800706be The remote procedure call failed.

superZhouDaLu · 2020-09-08T03:20:18Z

I have the same issue - running 20206, WSL kernel version: 4.19.128.

superZhouDaLu · 2020-09-08T07:08:13Z

I fixed, reason is make sure that virtualization is enabled inside of my computer's BIOS.

doctordns · 2020-09-08T09:05:24Z

I fixed, reason is make sure that virtualization is enabled inside of my computer's BIOS.

Sadly, that fix does not seem to work here.

I suspect there IS a bug, but...
IF the WSL installer discovers virtualisation is NOT bios enabled, can't the distribution installer give a better error message - please provide actionable error messages.

bmartinson · 2020-09-08T16:47:38Z

@doctordns, what build are you currently using? I spent hours trying to resolve this issue on the latest RC and Beta channel builds without any luck. Had to switch to the dev channel and install build 20206 to resolve the issue. Definitely a bug that is sitting fixed in the dev insider channel right now.

benhillis · 2020-09-08T16:51:50Z

Fix is inbound.

benhillis · 2020-09-11T13:49:37Z

Fixed in 20211.

JTDaddy17 · 2020-09-11T18:18:32Z

Having problems with this error too, currently on Insider Release Preview Channel 20H2 19042.508

tigerblue77 · 2020-09-12T12:10:17Z

Fixed in 20211.

Nope, I reinstalled everything (WSL + Debian distro) and same error

toddmc · 2020-09-13T23:32:07Z

Fixed in 20211.

I recently installed 20211. Even with 20211, I initially had issues with running ubuntu. After trying some series of steps here, I was able to get ubuntu 20.04 to run briefly. Unfortunately, I am now getting the following message when starting it:

WSL 2 requires an update to its kernel component. For information please visit https://aka.ms/wsl2kernel
Press any key to continue...

And the 3 ways that I know to update the kernel are failing for me:

Windows Update
There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070643)
Download from https://aka.ms/wsl2kernel
When running wsl_update_x64 I get a prompt to insert a 'Windows Subsystem for Linux Update' disk. It fails when I do not.
wsl --update
Same as above

doctordns · 2020-09-14T09:18:47Z

Fixed in 20211.

No. It's not. At least not here...

First time I try to install ubuntu:

Then I try again and show the Winver

hylowaker · 2020-09-15T01:41:00Z

Upgrading from 20206 to 20211 caused the error.

When I rollbacked to 20206, the error is gone.

tommy-hansen · 2020-09-21T21:50:03Z

Got the same error when trying to run in VMWare Fusion, the solution was a hypervisor CPU setting as described in the answer to this question.

All good.

Paranoid-Dev · 2020-09-25T07:07:11Z

I'm on 2004 OS build 20201.1000.

wsl.exe --update didn't work for me. Only works if I use wsl 1.

I'm on 20201 now, and the wsl.exe update worked!
Maybe it's fixed now for 20201 at least?

zhaolei-momo · 2020-09-25T09:24:32Z

Now I can only update from 2004 to 20150,
I donot know how can I update to 20201.

tigerblue77 · 2020-09-25T10:22:48Z

Hello,

So I installed build 20221 (should have fixed this problem accordingly to Windows insiders's blog) but it was not working. Here is what I did :

Uninstalled my distro (debian)
Uninstalled WSL functionnality
Restarted my PC
Reinstalled WSL
Reinstalled Debian (didn't worked) so I followed this : https://docs.microsoft.com/en-us/windows/wsl/install-win10
After step 4 my problem seems fixed because debian asked me an username for the new user to create
But when I enter an username : "Remote procedure call failure" (translated error message)

Paranoid-Dev · 2020-09-25T11:22:48Z

Now I can only update from 2004 to 20150,
I donot know how can I update to 20201.

https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced

Here, the ISO is build 20201 last time I checked (if you upgrade by the update center, you can get newer releases)
If you upgrade by ISO, instead of the usual method of using the update center, you can install without giving Windows (and MS) your MS account, so less telemetry this way

tigerblue77 · 2020-10-03T15:00:53Z

Build 20226.1000 : I can confirm that this problem has been fixed now ! It works perfectly again 👍

MKhoshnevis · 2020-12-11T20:51:45Z

I had the same issue with wsl , tring to install opensuse to install netdata on windows machine .
to resolve ,
1 -remove the WSl and Virtual machine platform options form windows apps and feature
2- reboot machine
3- go regedit > HKEY_LOCAL_MACHINE/SYSTEM/CURRENT CONTROL SET/SERVICES
here you may see multiple LSXXMANAGER service listed
4 - REMOVE LSXXMANAGER , starting from the last on elisted ( if you can't remove some, just change the Start key tp 1 , and start LSXXMANAGER from the Services.msc )
5 - reboot
6 - Install back WSL and Virtual Machine Platform options in Apps and Features
7 - get opensuse 15.1 from microsoft store .

this worked for me .

hekailiang · 2021-01-14T15:25:34Z

Running this command solved it for me, insider preview 2004
wsl.exe --update

worked for me, but need to run PowerShell as administrator first

benhillis added bug fixinbound labels Aug 20, 2020

benhillis self-assigned this Aug 20, 2020

radovanobal mentioned this issue Aug 27, 2020

Unable to start wsl, only cursor #5807

Closed

microsoft locked and limited conversation to collaborators Sep 8, 2020

screamingworld mentioned this issue Sep 9, 2020

Convert WSL Instance to version 2 failed with "The remote procedure call failed" #5263

Closed

francescarpi mentioned this issue Sep 9, 2020

"Element not found" after install KB4571756 #5880

Closed

benhillis closed this as completed Sep 11, 2020

microsoft unlocked this conversation Sep 11, 2020

benhillis added fixedininsiderbuilds and removed fixinbound labels Sep 11, 2020

Brian-Perkins mentioned this issue Sep 11, 2020

WSL 2 will not start after installing KB4571756 #5890

Closed

shawnz mentioned this issue Apr 1, 2021

Can't install WSL1 with hardware virtualization disabled on Insider builds #6741

Closed

TBBle mentioned this issue May 30, 2022

WSL 2 broken on Windows Server Preview (since change to fe_release branch) #6301

Closed

When installing a distribution the process fails with: "WslRegisterDistribution failed with error: 0x800706be. #5768

When installing a distribution the process fails with: "WslRegisterDistribution failed with error: 0x800706be. #5768

Comments

IPlayZed commented Aug 16, 2020 • edited Loading

Environment

Steps to reproduce

Expected behavior

Actual behavior

IPlayZed commented Aug 16, 2020

ajpeacock0 commented Aug 16, 2020

zanettea commented Aug 17, 2020

yurividal commented Aug 18, 2020

Loca123 commented Aug 18, 2020 • edited Loading

camille-ryan commented Aug 18, 2020

Duayt commented Aug 18, 2020

yurividal commented Aug 18, 2020

Loca123 commented Aug 18, 2020

camille-ryan commented Aug 19, 2020 • edited Loading

benhillis commented Aug 20, 2020 • edited Loading

dudeisbrendan03 commented Aug 20, 2020

benhillis commented Aug 20, 2020

aCoder2013 commented Aug 22, 2020 • edited Loading

ghost commented Aug 22, 2020 • edited by ghost Loading

machug commented Aug 22, 2020

allanheller commented Aug 22, 2020

tigerblue77 commented Aug 22, 2020 • edited Loading

ghost commented Aug 22, 2020

radday5 commented Aug 23, 2020

tpjones-coder commented Aug 24, 2020

voidiak commented Aug 24, 2020

deepan-py commented Aug 25, 2020 • edited Loading

keremnymn commented Aug 25, 2020

radovanobal commented Aug 26, 2020

tpanj commented Aug 26, 2020

doctordns commented Sep 7, 2020

superZhouDaLu commented Sep 8, 2020 • edited Loading

superZhouDaLu commented Sep 8, 2020 • edited Loading

doctordns commented Sep 8, 2020

bmartinson commented Sep 8, 2020

benhillis commented Sep 8, 2020 • edited Loading

benhillis commented Sep 11, 2020

JTDaddy17 commented Sep 11, 2020

tigerblue77 commented Sep 12, 2020

toddmc commented Sep 13, 2020 • edited Loading

doctordns commented Sep 14, 2020

hylowaker commented Sep 15, 2020

tommy-hansen commented Sep 21, 2020 • edited Loading

Paranoid-Dev commented Sep 25, 2020 • edited Loading

zhaolei-momo commented Sep 25, 2020

tigerblue77 commented Sep 25, 2020 • edited Loading

Paranoid-Dev commented Sep 25, 2020 • edited Loading

tigerblue77 commented Oct 3, 2020

MKhoshnevis commented Dec 11, 2020

hekailiang commented Jan 14, 2021

IPlayZed commented Aug 16, 2020 •

edited

Loading

Loca123 commented Aug 18, 2020 •

edited

Loading

camille-ryan commented Aug 19, 2020 •

edited

Loading

benhillis commented Aug 20, 2020 •

edited

Loading

aCoder2013 commented Aug 22, 2020 •

edited

Loading

ghost commented Aug 22, 2020 •

edited by ghost

Loading

tigerblue77 commented Aug 22, 2020 •

edited

Loading

deepan-py commented Aug 25, 2020 •

edited

Loading

superZhouDaLu commented Sep 8, 2020 •

edited

Loading

superZhouDaLu commented Sep 8, 2020 •

edited

Loading

benhillis commented Sep 8, 2020 •

edited

Loading

toddmc commented Sep 13, 2020 •

edited

Loading

tommy-hansen commented Sep 21, 2020 •

edited

Loading

Paranoid-Dev commented Sep 25, 2020 •

edited

Loading

tigerblue77 commented Sep 25, 2020 •

edited

Loading

Paranoid-Dev commented Sep 25, 2020 •

edited

Loading