Besides turning on virtualization features of the processor and turning off Hyper-V, here's another thing, related to Windows' Virtualization-Based Security features:
https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-vbs
VBS (and the associated security features) must be disabled to avoid conflicting hypervisors. Here is a solution from VMware, which also seems valid for the VirtualBox issue":
https://kb.vmware.com/s/article/2146361