-
Notifications
You must be signed in to change notification settings - Fork 105
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
Cant upgrade to WSL2 "bsdtar: Write error" #504
Comments
I have seen this too. I found that resetting back to factory Pengwin, reducing the size of the installed application helps. I wonder if this is a bug in the conversion process that affects installs over a certain size. More investigation is needed and possible upstream bug report. |
But resting back to factory Pengwin, will remove all installed apps, right? If so, I don't think this is an easy step for me now :) !
How can I get you my installation size? |
Some questions:
|
Hi @Biswa96 What do you think? I just manually install Ubuntu 18.04 Windows Build10.Pro N |
Ok, now it's works like a Charm!!! It's a messy procedure an d i donk know, but some tips from this post did the magic.
Now, anyone can explain what is the charm? |
The fact we can reproduce this issue across multiple distros leads me to think it is an upstream issue. Has anyone reported this upstream or something similar? |
@sirredbeard any idea where can we "report this upstream"? |
I have submitted the issue upstream to the WSL team here microsoft/WSL#4394. Lets try to land a hand there tracking this down as it affects all distros. |
Has anyone got |
@Biswa96 I was actually working on that last night for this issue and got distracted. Trying to make it consistently fail. Stand by. |
I have just disabled Windows Security, re-tried and the command completed successfully this time but neither bash.exe nor Pengwin app work :( |
Are you running on a build 18945 or higher? #497 |
I'm running 18963, and it is working now (with some weird lagging) after I edited |
@HoshiYamazaki Please subscribe to microsoft/WSL#4394 for more details on this. |
I had the same error, too. Since the error was related to 'bsdtar', my intuition was to do the following
Currently, I'm running wsl2 without a problem (for now) |
@KaraxThePhaseSmith That's interesting. I don't think it's calling bsdtar in the distro, I think it's calling a bsdtar binary in the WSL layer. It might have worked then because this bug is sporadic at times. But I will pass it along. |
For those who is interested, disabling real-time protection of Windows Defender did the thing for me. Disgusting! |
It worked for me. In Windows:
open linux distro (Ubuntu)
In Windows (didn't even close Powershell in between):
|
Hi the only fix that worked for me was to limit the ram usage etc...
sirredbeard was maybe in the right when he said it could be "random" bugs, (I tried every tips on this page and my wsl install is fresh) edit : |
I had a brokenpipe error when crackmapexec was being installed |
Hello, I don't thing this is the same error. Could you elaborate more what you did and the result? Regards |
Yes yes ... It's not an error when trying to upgrade to wsl-2 |
The most probable issue is due to a problem in internet connection. I tried now to install this package and it installed without problems. Try to issue an apt update and try again. |
I ran into quite a few issues when converting from WSL 1 to WSL 2 that relates to this ticket. I detailed my environment and the journey I took to work around them in the following comment. |
@CompSciMaj13 Thanks for sharing |
Describe the bug
Basic Troubleshooting Checklist
[ ] I have reset Pengwin: Settings->Apps->Apps & features->Pengwin->Advanced Options->Reset.
[ ] I have disabled and re-enabled WSL in Windows Features.
[x] I have run Windows 10 updates and restarted.
*What other troubleshooting have you attempted?
Made sure that WSL is not running, restarted multiple times and kept re-trying but failed.
Pengwin Version
1.2.7.0
Windows Build
10.0.18947 N/A Build 18947
The text was updated successfully, but these errors were encountered: