What have you tried: reinstallation following aborted install
What is the error: install fails when reaching installing software packages
What device is this on: Dell precision 3680 tower
Hi all, I have an issue installing Kali in virtual box. I had previously tried to install Kali following a tutorial that was wrong. This led my antivirus to quarantine a huge amount of files. The installation was aborted and the ISO deleted. I now have the correct process to install Kali Linux in virtual box however when the install gets to installing the software it gets so far and fails. It looks like there are old files left over from the previous installation that I need to get rid of before I can install it properly however I have no idea where to find these files so I can remove them. As you can probably tell I am new to cybersecurity so any help on this would be greatly appreciated. I can’t be the first person to of had this issue? Thanks in advance!
Is your Dell precision using Windows and are you trying to install Kali Linux from the same storage device as your OS or from a USB device? Is it your intention to install Kali so you can have a dual boot device?
Why do you believe old installed files are the problem?
What specific error(s) are being generated?
Lastly, if Windows is your primary OS, have you considered WSL?
With the virtual machine ‘switched off’ check in virtual box settings for it that the vm has at the least a dual core processor with 4 GB RAM allocated to it, and a 20 GB disk drive for the installation, if there is either not enough RAM memory to hold downloaded applications in, or not enough storage to write them too, then this part of the install will fail.
It is for the best to follow the official documentation always. You can also try the prebuilt image for vbox since you can just download it and run it without going through the mess of installation.
Thanks for taking the time to respond to this. I had another look at it with a fresh head this evening and found id made the simplest of mistakes. i had not named the machine properly in virtualbox, which then wouldnt allow me to create a new virtual disc and finish the process of adding the VM to virtualbox (although it looked like it was added and was in the list)
@Niccea the reason i thought there may be old files is because it was telling me there may be, but it looks like that was because it was trying to install onto the same virtual disc as an existing linux ubuntu VM, because i hadnt been able to specify the creration of a new virtual disc for the install. (i think)
Thanks again for all your responses, problem is now solved. Lesson learned!