Since Hyper-V was running at the time, I did this: The best way to do this was to create two Windows boot entry - one with and one without Hyper-V, based on this guide - Use Windows 10 bootmanager to enable Hyper-V and Other Virtual Devices in Same Computer. The usual warnings and disclaimers apply! Don’t trust me, but verify everything, thanks! You can’t have it both ways and have Hyper-V and VirtualBox running simultaneously. The solution is to turn off Hyper-V when not required, e.g.

If I am not mistaken, I did not enable Hyper-V (via Settings > Programs and Features > Turn Windows Features on or off).

Installed VirtualBox 6.1 and created a guest VM, with Guest Additions installed.

I ran few commands following the Windows Subsystem for Linux Installation Guide for Windows 10.

Only much later, did I discover the problem was that I had the Windows Subsystem for Linux 2 (WSL2) installed, and WSL2 requires the Windows Hypervisor Platform, which in turn does not play nice with VirtualBox. And then I thought it might be an AMD thing, so had a look at BIOS, e.g. insufficient cores or memory, the display controller (VBoxSVGA), insufficient video memory, etc. Initially I thought it was to do with VirtualBox, e.g.

I found that Oracle VM VirtualBox 6.1 was running very slowly on my brand new Windows 10 PC.

Macos virtualbox laggy