The solution to this is simple: disable Hyper-V. This would come at the expense of performance and, as observed by myself and others, does not really work well. Virtualbox would fallback to Hyper-V using Microsoft provided APIs. Microsoft and Oracle both state that Virtualbox is compatible with WSL2. Having Virtualbox, or any other virtualization solution installed on the same machine as Hyper-V will result in problems. However, with the update to Windows 10 version 2004 WSL got updated to WSL2 which introduces Hyper-V as a virtualization solution for it’s kernel. Instead, it uses a compatibility layer which translates Linux calls into native Windows calls.
This setup worked perfectly well because WSL does not require any form of virtualization. Additionally, I had the above-mentioned virtual machines running in Virtualbox. My Windows 10 forensic analysis machine would crash on boot and while my Kali and Ubuntu based Linux machines seemingly ran properly, I encountered a “Hash sum mismatch” error when using apt update and git clone refused to clone with an “invalid distance too far back” error.Īs it turns out, the error was caused by Hyper-V and Virtualbox.īefore the upgrade to WindI used the Windows Subsystem for Linux (WSL) along with a Kali Linux distro.
Since upgrading my Windows 10 to version 2004, my Virtualbox hosted virtual machines acted up.
0 kommentar(er)
