Thanks for anything, but is not about the bios... and it is already resolve... a put this same question in the microsoft technet forum and an user named Bill Grant gave me the resolve solution and explanation..
Uninstall Hyper-V. The only other way is to modify the hypervisorlaunchtype from bcdedit so that the hypervisor is not loaded.
When you install Hyper-V the hypervisorlaunchtype is set to auto and the hypervisor is loaded before Windows boots. The hypervisor has control of hardware virtualization, not the OS. If the hypervisor is not loaded, the OS has control of hardware virtualization and VirtualBox can access it (but Hyper-v vms and emulators will not run).
I am glad to hear that you were able to resolve your issue. Thank you for your feedback.