-
Notifications
You must be signed in to change notification settings - Fork 806
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
wsl --import Unspecified Error / The specified network name is no longer available. #4835
Comments
Update: When deleting I'm suspecting either conflicts with the |
Same for me. Unspecified Error each time I try the wsl --import command on a previously exported (in.tar) image |
Same for me. |
What worked for me was importing the WSL 2 distribution as WSL 1 using |
But obviously this is a temporary workaround. In my case, the import would cause the RAM utilization to go to about 95%, and then I would see the aforementioned error. It seems like there is something wrong with importing large image sizes (mine was about 18GB). |
Same here. @nimamahmoudi's method works but now running "wsl -d MyImportedDistrib" give me a root prompt instead of the correct user... ^^' (the import process can be speedup by excluding the install directory in defender...) |
Ran into the same issue, which appears to be related to RAM. I'm on 8GB trying to import an image that is also about 8GB. I was able to get around this issue by temporarily increasing the virtual RAM to 16GB. |
I was getting this error on my WSL2 image which was 45GB. I ended up installing a new Ubuntu WSL2 instance then just copying over my vhdx file. Just had to setup my user again as it was logging in with |
The import fails for me with the Unspecified error regardless of whether I try version 1 or version 2. I have 16G of memory, the image size is about 2G. Is there any way to diagnose further? |
I got same sutiation, after that I set "swap=120GB" in .wslconfig file, it worked! @kristof-mattei this may be memory lack caused |
@nimamahmoudi solution of importing as v1 then converting was the only one that worked for me. |
Only thing that worked for me was importing as v1 and turning it into v2. |
@stormysky Where is the .wslconfig file stored for WSL2? Or if it's not existing you need to create it by your own? For me importing as V1 and converting then has worked out, but I've been able to login as root by default after re-import (not sure if it's connected to converting). So had to patch the register to fix it to my primary OS user. |
@adolgoff .wslconfig need to created by own strored at current user path (c:\users\xxxx, xxx is current user), here is my configuration |
None of these work for me, I've tried importing as |
I solved this problem after compact my wsl vdisk: |
Maybe a duplicate of issue #4735. |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Your Windows build number: Microsoft Windows [Version 10.0.19041.21]
What you're doing and what's happening:
Exported Ubuntu from C Drive due to size issues. I now have a .tar sitting on
D:\Ubuntu.tar
Trying to import the file yields
Unspecified Error
orThe specified network name is no longer available.
Command executed:
wsl --import Ubuntu-18.04 d:\WSL\Ubuntu-18.04\ d:\Ubuntu.tar
What's wrong / what should be happening instead:
This shouldn't happen, the Distro should import.
For WSL launch issues, please [collect detailed logs] logs.zip
Logs attached!
The text was updated successfully, but these errors were encountered: