Only wanted to install Kali on wsl with kex. You guys can’t even be real. Do you do this to everyone who has installed this? This is unbelievable. IDP.Generic? not even 1 minuto into shell? Unreal.
Did you follow the steps here BEFORE installing kali in WSL or did you just download kali from microsoft without downloding the kernel etc;
I just used the installation method recommended by windows on-shell, via wsl install and just adding kali linux. When I got into the system (dev@user) y started following the win kex commands, but after one or two Avast woke up. I searched a bit because that Generic could be a false positive, but unfortunately there was nothing on the avast chest, although I told it to.
I’m aware that things usually require a little bit of attention, but since I started using kali, on virtual machines, it has always being a little bit pain you know where, and that’s why I was a bit concerned. Avast was always waking up any time I made upgrades, I expended hours and hours trying to solve initramfs whenever I run it on VirtualBox, only “solution” being using fsck and reboot -f every time I started it, and even Avast crash when trying to analyze all my files, mysteriously always on kali linux installer.
Man I know Kali is for “experts”, I’m studying a Master on Cybersecurity, myself (not that I studied computer science, tho), but man they could do it a little bit easier for everyone, like you sent me to some webpage just for something that should be done via wsl install and done. Sjsldjslskslsj.
Antivirus warnings are expected due to the nature of Kali’s tools.
If you are using Kali on windows and it flags something, chances are it quarantines a file which breaks something. Just set the exclusion up and you shouldn’t have problems. Not much we can do on our side for this outside of having the documentation that we have currently.
Actually if you want to use Kali for cybersecurity then WSL is not a good choice, Windows restricts Kali too much, if you want to use Kali from within Windows, use Virtual Box or VM Ware Workstation and install Kali as a guest OS from an ISO file, otherwise most of the tutorials etc you try and follow will fail in a WSL environment.
Thank you both of you, really, :). I’m aware of using some vms for a better and more secure experience with Kali, I just wanted to have a ressemblance on a comfortable and full hardware equipped option. Now you actually reminded me that I shouldn’t do the risckiest jobs there, so I’ll still give another try to vbox kali, since ware gave me more or less the same issues and im more of a box guy :). ty so much for your consideration, and for not bringing the fire onto me for my critics or lack of xp. Bless you guys
I disagree with this. Pentester for many years, and pretty much all of the offsec certs. I use kali in WSL pretty much exclusively.
fair enough, last time I tried Kali in WSL it was very restricted in function, I’m sure lots has changed.
I had to Disable my Windows Virus Protection to download Kali ISO.
Windows does not like Kali it is much less sever on other versions of Linux.
I was using Avast in Windows, it would not let me download Kali ISO, so I disabled it.
I saw your screen Capture, it is Obviously a Message from Avast Anti Virus.
Disable Avast, and you can Download Kali ISO.
My security protocols and apps running under Windows has often quarantined critical files necessary for a piece of software to operate properly. Its only after pulling hair and much nail biting, cursing and the like do I find out a Restore button solves my problem.