Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu on WSL gets corrupted - WslRegisterDistribution failed with error: 0x800700b7 #3352

Closed
icex opened this issue Jul 4, 2018 · 21 comments

Comments

@icex
Copy link

icex commented Jul 4, 2018

  • Your Windows build number: Microsoft Windows [Version 10.0.17134.137]

  • What you're doing and what's happening:
    Sometimes, after a reboot, when I open Ubuntu I receive the error below and the only solution so far is to reinstall it clean or never reboot(ever). Same issue happened on 18.04 and on 16.04 and I had to reinstall, loosing all my config.

  • What's wrong / what should be happening instead:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x800700b7
The distribution installation has become corrupted.
Please select Reset from App Settings or uninstall and reinstall the app.
Error: 0x800700b7 Cannot create a file when that file already exists.

Press any key to continue...
@icex
Copy link
Author

icex commented Jul 4, 2018

PS: This happened on my PC and on my Laptop, both after a reboot.

@MVoz
Copy link

MVoz commented Jul 5, 2018

#634 (comment)

cmda.exe

sc query LxssManager
sc stop LxssManager
sc start LxssManager

and so apparently you have something with the system, check for errors

sfc /scannow
dism /Online /Cleanup-Image /RestoreHealth

@icex
Copy link
Author

icex commented Jul 5, 2018

Thanks. Restarting LxssManager solved it.

"Windows Resource Protection did not find any integrity violations."

@icex icex closed this as completed Jul 5, 2018
@nick-walt
Copy link

After running wslconfig /unregister Ubuntu-18.04 I received the error that started this thread. Restarting LxssManager service did not resolve it. However, uninstalling the instance did resolve it.

@KenLast
Copy link

KenLast commented Sep 16, 2018

Thank you. I ran into the same thing and restarting the service as you describe fixed it.

@saidfagan
Copy link

I get this error on both Ubuntu and OpenSuse. Restarting LxssManager solves it. But when I restart my Windows problem happens again. Any ideas?

@icex
Copy link
Author

icex commented Nov 3, 2018

I had a scheduled task to start some services (using a Vbs script) and I think I had checked run as administrator. I guess that was my cause for this. I could be wrong, but check that if you’re running at startup.

@NicholasIoanJones
Copy link

Restarting LxssManager solved it for me too

@caal-15
Copy link

caal-15 commented Dec 17, 2018

Restarting the Manager does resolve it, but it happens everytime I start the PC again :(

@kj-joseph
Copy link

@caal-15: I found this very helpful: #2576 (comment)

@caal-15
Copy link

caal-15 commented Jan 30, 2019

@kj-joseph Thank you!, that was actually really helpful :)

@epogrebnyak
Copy link

epogrebnyak commented May 26, 2019

For those looking how to restart LxssManager, here is an instruction.

@objt-ba
Copy link

objt-ba commented Aug 23, 2019

In my case, stopping the LxssManager takes ages, and after stopping it, it won't start again.
After a full system reboot everything works again though.

Now, what I have found, is that if an application displays an exception while being connected through an in-line command. (i.e. ubuntu1604 <command>) this can sometimes hang the system. My guess is that this command never comes to an end, and as a result there is no way to use that instance anymore. ... until a full system reboot in my case.

@jrdx0
Copy link

jrdx0 commented Sep 6, 2019

I cant restart LxssManager, it's stop and when I try to run it, console print ERROR 1058

@vseal001
Copy link

I found a better way to deal it, first delete the files, then delete reg, then reinstall.
Finaly: its work

@CiaranWelsh
Copy link

I found a better way to deal it, first delete the files, then delete reg, then reinstall.
Finaly: its work

Could you be more specific so others can try and replicate your solution?

@ThrashAbaddon
Copy link

This can happen if Kasperski is installed.

@vjkaran
Copy link

vjkaran commented Apr 12, 2020

This can happen if Kasperski is installed.

Did stopping the Kasperski solve it for you @ThrashAbaddon ?

@juanccamachob94
Copy link

I came here because of this error

error 0x8007010b al iniciar wsl.exe -d Ubuntu-18.04 (C:/mnt/c/)

It seems that they updated some features of the terminal and my home path /mnt/c/Users/Developer/Documents/ no longer works, but making the following change works, and better, because I can access subdirectories that before the home path did not allow me.
image
(this picture belongs to terminal configuration)

I leave it here in case it helps someone

@LiLejia
Copy link

LiLejia commented Nov 15, 2021

Fore those of you still in trouble.
Download rootfs and import manually could at least work.
https://gist.github.com/djfdyuruiry/61e32fb69645bd2618182ee17373d068

@Usman-Click
Copy link

Well... i'm here in 2024

in my case it got solved after i reset the distribution

these are the steps :

  • Open Settings:
    Press Windows + I to open the Settings app.
    Navigate to Apps:

  • Go to Apps > Apps & features.
    Find Your Linux Distribution:

  • Scroll through the list of installed apps and find your Linux distribution (e.g., Ubuntu, Debian).
    Reset the App:

  • Click on the distribution and then click Advanced options.
    Scroll down and click Reset.

re-open your distribution and ta-da i'll work In shaa Allah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests