-
Notifications
You must be signed in to change notification settings - Fork 798
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
Kali Linux release 2/22/2018 through Store, WslRegisterDistribution fails with error 0x80070057 #3054
Comments
I think you'll need to address this with the Kali Linux team as they are responsible for the appx. Probably an update in response to the update to the launcher that is now open-source. FWIW, I had no issues with the update but I don't have a clean image either. |
hi I am having the same issue. anyone has any idea on how to fix this? thanks so much |
Whn I extract the kali.exe and install.tar.gz from Appx package, Kali installs rootfs successfully. |
Hi @Biswa96, where can you get the Appx package which contains kali.exe and install.tar.gz? Thanks |
What do you do with these files after extracting? |
Would it be possible to collect logs while attempting the install? https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs |
Same issue |
Has anyone tried to uninstall the Kali Linux package fully from Windows Store and reinstall? |
Running kali.exe fixed it for me. |
Running kali.exe actually brought the errormessage from the above screenshots. |
If somebody that is hitting the issue could collect logs it would be helpful in getting this fixed. https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs |
I just started getting the problem today. I'm scared to uninstall since I have some private keys on the instance for an ssh server that doesn't have username login. I did notice when I run the wsl.exe, kali will run since it's the only distro on the system. Edit: WSL is just an alias for bash.exe like @godmodenewbie showed Here are some logs: |
Thanks, I have identified the issue and will work with Kali to get this fixed. |
So the bare image for WSL stems from the link I had referenced above but it appears the official page is https://github.com/offensive-security/Kali-WSL-chroot where it shows in the main page:
So we should probably file Kali issues there instead. I edited my post above to remove the link. |
same problem after the update |
Any update on this? I have installed metasploit, and would like to preserve my config without re-installing... any advice welcome. |
Same issue for me. |
Unfortunately the updates version of the kali app uses a different distribution identifier than the previous version. This is causing WSL to think that the app is not installed, and when the install is attempted it fails because the root file system already exists. The easiest way to rectify this issue will be to select Reset from Kali App Settings or uninstall and reinstall the app. If you'd like to back up any information from your previous install you can use wslconfig.exe and wsl.exe:
|
wslconfig.exe /setdefault kali-rolling DONE, Everything is where you left it. |
benhillis, why back it up? Just set the default to kali and type bash... |
Because Kali.exe won't work until you reinstall it reset. |
Also, I realize there is an issue with using proxy/vpn in the WSL that I believe you commented on before. |
I did what @Izumiko mentioned
with @bityob info to move the rootfs from and Kali works again with installed packages still intact |
IMPORTANT: You must move the rootfs folder out of the C:\Users<username>\AppData\Local\Packages\KaliLinux\LocalState folder for safe keeping because everything in the LocalState folder will be deleted when you reset Kali in the Windows Store. If you simply rename the rootfs folder (e.g., rootfs.sav) in place it will be deleted by the reset and you will loose your packages and content. |
mark it!!! Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x800703fa
Error: 0x800703fa ???????????????????????
Press any key to continue... |
revisiting this issue after months with a whole new problem
|
Installing, this may take a few minutes... Press any key to continue... Tried all the suggested remedies and none of them have worked, anyone else getting this error? |
@SquatchRage a reboot fixed it for me |
My bad, I'll remove that comment to avoid confusing people. |
BAD ENGLISH
|
In my case the LxssManager service was set to manual and needed to be started up after every reboot. The startup type could not be set in services.msc (even as admin). I had to manually set the the registry key here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LxssManager Start = 2 |
Closing out since issue is resolved. |
Happened again today with the update to 1.1.4. Same error as in the initial comment. All other WSL distributions still work and it is still shown as registered and can still access it by changing the default and using wsl.exe. |
Looks like the distribution name got changed again. I'll follow up with the Kali dev that owns the package. |
I tried to start Kali Linux on my Windows PC and here is the problem: Installation, it may take a few minutes ... Another solution to overcome this problem that worked on my pc: 1- Go to C:\Program Files\WindowsApps\KaliLinux_1.1.4.0_x64 __ * The problem is now solved See You |
@31i73-73aM I have no idea how that can even work as the error occurs when you try to run kali.exe @benhillis There was a 1.1.5 update today which probably fixed the problem but broke it again for me. As none of the suggested workaround worked for me it took me hours to get this working again and probably will again now. There really need to be some proper safe guards for this... |
need WSL on in windows and all work. |
tu problema es no haber iniciado powershell como administrador con esto solucionas el problema you problem not is start to terminal of powershell as administrator for install |
just use this command to set your WSL version to 1 |
OMG 😲, thanks for this. After so many restarts, preparing and resetting linuxs apps installed by Microsoft Store, and several dism and wsl install commands you find one useful to make kali and ubuntu Linux run under Linux subsystem. This should be in some official documentation. I previously edited LxssManager key in registry to enable it. |
You can backup your wsl distro using the below command from Powershell wsl --export kali-rolling kali-rolling.tar.gz |
@aditya-digitalai set the following registry key value to 1: OR deletE the file %USERPROFILE%.wslconfig, restart wsl and retry the distro install. It is worth to check for this before doing any in-place upgrade... Ref: #6363 |
Tried setting the value in registry |
This will install kali with WSL 1. The |
Windows 10.0.16299.334 Pro x64 en-us (current public release build with current cumulative update KB4089848 at time of issue).
Kali Linux installed through the Store on original release date, no problem observed (but not used much).
Other distributions (Ubuntu and Debian) working fine.
Today Kali Linux got updated through the Store, to version 1.1.2.0 released on 2/22/2018.
After update, launching the Kali Linux instance shows the following:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070057
Error: 0x80070057 The parameter is incorrect.
Uninstalling and reinstalling Kali Linux package works.
The text was updated successfully, but these errors were encountered: