coucou wrote:after a windows 10 update
This is always a suspect, since Hyper-V or a service that uses it could have been enabled. See
I have a 64bit host, but can't install 64bit guests, 2nd & 3rd posts.
You have a lot of extra antivirus and nannybot software: TrendMicro, McAffee, Beyond Trust, Websense Endpoint. If these were present before the Windows 10 update, and were not updated as well, maybe they can be excluded. But they may have been updated too and any of them might also be suspects. See
Diagnosing VirtualBox Hardening Issues, which recommends as a troubleshooting step, complete uninstall of these extra software packages as a test to get Virtualbox working, then one-by-one reinstall with a host reboot and Virtualbox test in between reinstalls, to see when (if?) Virtualbox fails again. (Don't skip the reboots, sometimes things work until the next reboot.) It is possible that an un/reinstall of the AV will allow Virtualbox to work again and coexistence to reign supreme.
Look into Hyper-V first, especially the 'bcdedit' command, then go after the extra AV.
One other thing: The hardening log did not end in an exit code report, which likely means the guest's Virtualbox window, or possibly the error box(?) was still open when the log was saved out. Please be sure to close any window related to the failed guest before taking logs.