Kali 2020.2 OVA (VirtualBox) setup errors

[Chris_Redz]

The last two VirtualBox releases have been giving me hard times when it comes to update/upgrade/dist-upgrade. Many errors you don?t expect from a VM built by the kali team.
Has it happened to you to?


I have just downloaded 2020.2 VM for VirtualBox and when doing "apt update && apt -y full-upgrade" this is the outcome. Has it happened to you to? I don?t even know if this is their repositories playing up or my distro not properly configured. Any helpful advise is more than welcome thanks!


oot@kali:/home/kali# apt update && apt -y full-upgrade
Get:1 http://kali.download/kali kali-rolling InRelease [30.5 kB]
Get:2 http://kali.download/kali kali-rolling/main amd64 Packages [16.5 MB]
Get:3 http://kali.download/kali kali-rolling/non-free amd64 Packages [196 kB]
Get:4 http://kali.download/kali kali-rolling/contrib amd64 Packages [99.2 kB]
Err:2 http://kali.download/kali kali-rolling/main amd64 Packages
Hash Sum mismatch
Hashes of expected file:
- Filesize:63200642 [weak]
- SHA256:09402255492a57d33fca3838699a99480004d97ada9 365c18aa81caaf7f0a920
- SHA1:fed7573ae8881bfce3c212e5eb6848e4711fd255 [weak]
- MD5Sum:435c6f5e1458e7cc68aad40e617566fa [weak]
Hashes of received file:
- SHA256:6f66ca96bfbe85fdeee1073ecd28528a1b6a001f51a e9d7caacf290bf7810ab1
- SHA1:77413ed9e69d8af620a8c777011e368a11dacfc6 [weak]
- MD5Sum:435c6f5e1458e7cc68aad40e617566fa [weak]
- Filesize:63200642 [weak]
Last modification reported: Fri, 15 May 2020 12:04:40 +0000
Release file created at: Fri, 15 May 2020 12:05:35 +0000
Reading package lists... Done
E: Failed to fetch store:/var/lib/apt/lists/partial/http.kali.org_kali_dists_kali-rolling_main_binary-amd64_Packages.gz Hash Sum mismatch
Hashes of expected file:
- Filesize:63200642 [weak]
- SHA256:09402255492a57d33fca3838699a99480004d97ada9 365c18aa81caaf7f0a920
- SHA1:fed7573ae8881bfce3c212e5eb6848e4711fd255 [weak]
- MD5Sum:435c6f5e1458e7cc68aad40e617566fa [weak]
Hashes of received file:
- SHA256:6f66ca96bfbe85fdeee1073ecd28528a1b6a001f51a e9d7caacf290bf7810ab1
- SHA1:77413ed9e69d8af620a8c777011e368a11dacfc6 [weak]
- MD5Sum:435c6f5e1458e7cc68aad40e617566fa [weak]
- Filesize:63200642 [weak]
Last modification reported: Fri, 15 May 2020 12:04:40 +0000
Release file created at: Fri, 15 May 2020 12:05:35 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

[LRitzdorf]

I hate to be this guy, but I'm having the same issue and unfortunately can't offer any advice.

It's been happening to me for maybe three weeks (as of today, May 28, 2020), beginning with Kali 2020.1 (although not immediately -- I had successfully updated my 2020.1 install before this popped up) and persisting in 2020.2. From my online research, it would seem that the Kali source repository lists an incorrect hash for the `...Packages.gz` file, especially since the issue spans Kali release versions. I'm not certain of this, however, and have minimal experience with `apt` issues like this one.

[hellosatish]

Did anybody found any fix or workaround. I am also struggling with the same issue.
My Environment is -> AMD, Windows 10, Virtual Box, kali-linux-2020-2a-vbox-amd64-ova

[LRitzdorf]

I seem to recall seeing a possible solution that involved telling Kali to accept the "weak" MD5 or SHA1 hashes as sufficient proof of file integrity. That was a while ago, though, so I don't have a link. Also, consider the security implications of trusting a weaker hash method before actually doing that!

[hellosatish]

It worked for me with weak hash as well in another instace.
But about after 10-12 days without any changes being made on my side. It worked automatically on the VM in was struggling with. As it was suggested in many other threads, looks like there was something with the Mirror at that time.

[LRitzdorf]

It does appear to be a mirror/server issue, although it's not resolved for me. Additionally, I just made a new, clean VirtualBox install, with everything set to default, and immediately ran `sudo apt update`, only to hit exactly this same issue once again.

[leo2020]

i am on windows 10. and this works for me :
1. Shut down the Virtual Machine.
2. Press Windows logo key + X, then hit A to run Command Prompt(powershell) as administrator.
3. Typebcdedit /set hypervisorlaunchtype off
4. When you see"The operation completed succesfully", reboot your windows. After reboot, boot your VM and update/upgrade.

i got it from here : https://askubuntu.com/questions/1235...fferent-sha256

[LRitzdorf]

I can confirm that this method fixed the issue for me. I opened the "Turn Windows features on or off" item from the Start search bar and disabled the "Windows Hypervisor Platform" entry. After rebooting my actual computer twice, VirtualBox no longer showed the turtle variant of its virtual CPU icon, and `apt update` and `apt upgrade` worked as expected.

Also, this change does not seem to have affected my WSL (version 1) installation of Kali Linux, and should thus be completely safe.

[LRitzdorf]

Okay, yet another update. I just received an update to Windows 10 version 2004, which enables WSL 2. Unfortunately, WSL 2 requires that the "Virtual Machine Platform" Windows feature be enabled, which causes VirtualBox to return to its slow virtualization mode (with the turtle vCPU icon). For users who need both VirtualBox and WSL 2, I feel this issue would be best resolved with a VirtualBox setting to select the virtualization mode (if that's even possible).

[Log_lk2005]

hey i have a problem if i wana run Kali linux on virtual box this error comes : What can i do??
F?r die virtuelle Maschine Kali-Linux-2021.1-vbox-amd64 1 konnte keine neue Sitzung er?ffnet werden.
Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).i

Fehlercode:	E_FAIL (0x80004005)
Komponente:	ConsoleWrap
Interface:	IConsole {872da645-4a9b-1727-bee2-5585105b9eed}