-
Notifications
You must be signed in to change notification settings - Fork 856
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
Error reinstalling bash - Error 0x80070005 #473
Comments
Try lxrun /uninstall /full /y and try installing via bash.exe? |
Hi @fpqc, tried it already! No joy :( |
#410 (comment) maybe! |
@davidedimauro88 - Which Windows build are you on? Can you try this with Windows build 14352? |
@sunilmut - I'm on the 14352 already! |
@davidedimauro88 - Sorry to hear that it is still not working for you. Can you try these steps and see if that helps?
|
Hi @sunilmut - it worked!!! |
C:\Users\pstejska\AppData\Local\lxss\home\pstejska\android>rmdir /s /q . This seems to be why. The %appdata%\home\username\android\external has this problem. |
@davidedimauro88 - Good to know that your issue is resolved. We had a bug in WSL that was leaking handles to directory. During bash instance start, we would try to delete these directories and that would fail (because of leaked handles) and cause the instance to not start. This has been fixed in our dev branch and should hit the release branch soon. |
Reopening this until the fix hits the insider builds. |
@sunilmut thanks for the update and the help! will be waiting for the new build then. |
This should be fixed in Build 14371 and probably even earlier than that. If possible @davidedimauro88 could you let us know if this is resolved for you? |
Hey @benhillis, I just tried to replicate the issue again and it seems to be fixed now. Thanks a lot! |
@davidedimauro88 Thank you very much for confirming! |
This error happened to me after the latest update on the release branch OS Build 14393.693 The instructions provided by @sunilmut fixed it, but requires losing all of the data which is not acceptable solution for most people: |
@NoFlames - You should also just be able to remove %localappdata%\lxss\temp |
I am reopening this issue. Before using the workaround, please collect traces as we would like to get to the bottom of this issue. Agreed with @NoFlames that lostig user data is not an acceptable solution. |
@sunilmut - If it helps, this started happening to me after I modified the file permissions so I could see hidden files. After I reverted that change, the issue no longer existed - so it may be an issue with windows modifying file attributes in a way that the bash shell doesn't like. |
@sunilmut unfortunately this procedure doesn't work on my system, still getting error 0x80070005 It worked well until yesterday, I don't know what has changed... My build is 15063.540 (Windows 10 1703) |
@lornova Had the same problem after I made the mistake of trying to access WSL files from Windows-Explorer. There were a bunch of stubborn temporary files under %appdata%\lxss\temp; often several sundirectories deep. After manually deleting these from an elevated-CMD window, I was able to completely delete %appdata%\lxss. After that, running Bash.exe worked fine. |
@lornova had the same issue after updating and rebooting Windows (I don't think updating had anything to do with it). After doing @sunilmut procedure (which was very hard due to a lot of files having excessive path names) and extra cleaning |
Closing this issue as it is stale. If you come across this again we will re-open and repro. |
Hi guys,
I've been trying bash for a couple of weeks and I literally 'Messed around' with it to test my full Linux stack and whether it could work with my workflow or not.
I've got to the point, though, when I broke too many things therefore I decided to reinstall it from scratch.
lxrun /uninstall
worked as expected but when I now runlxrun /install
, this is the output I getAlso tried to do the same thing opening bash directly but when I type
y
the bash window disappear!Thanks in advance and congrats for the amazing job you're doing!
The text was updated successfully, but these errors were encountered: