Vagrant: There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox

>PROBLEM

Starting vagrant:

    vagrant up

Causes the follwing issue:

There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. 
The command and stderr is shown below.

Command: ["startvm", "01748371-61a5-4c0e-a279-9077bab91aaf", "--type", "headless"]
Stderr: VBoxManage.exe: error: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

>SOLUTION

Turn off  hyper-v.
As administrator, issue the comand:

    bcdedit /set hypervisorlaunchtype off

Restart machine.

*** IMPORTANT NOTE:

Docker requires hyper-v on:

   bcdedit /set hypervisorlaunchtype auto start

So, after the environment is restarted, docker will stop working.
Docker and Vagrant/VirtualBox requires conflicting environment configuration.

>MORE
Turning hyper-v on and off
I have a 64bit host, but can't install 64bit guests

>ENV

Windows 10
Vagrant v2.2.6
VirtualBox 6.0


>SEE

Vagrant: The box you're attempting to add doesn't support the provider you requested

Docker: Hardware assisted virtualization and data execution protection must be enable in the BIOS