11-10-2019 04:32 AM
I contact you after (at least) 2 days of tries-and-errors experience ... I saw a lot of proposed solutions but none are working in my case.
I receive a new T590 (excellent PC) but I cannot start existing VM or create new with Oracle VirtualBox.
This VM is runnig on other PC's with same version of VirtualBox, but other model of Lenovo (fe P70)
The Bios is (in my point of view) well configured in order to allow Virtualization feature (Secutity > Virtualization > (as far I remember) DMA enable, Virtualization enable, vt-d enable, biometric enable)
I updated the Bios of this host (N2IET77W 1.55)
Check Windows 10 properties comparing colleague's PC where all is OK
Check Windows features found on internet solutions
Check the ability of processor to run Vitual machins
Compare Bios setup with running machins
Compare Widows setup with running machins
Search and search on google solutions
Who can help me or give me a tip ?
Don't hesitate if additional info is needed.
Thanks for your reading and future help
T590 (I7 - 16Go Ram - 256Go SSD)
Win 10 1903 Enterprise (10.0.18362 Build 18362
VirtualBox Error message
Failed to open a session for the virtual machine xxxx.
Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).
|Result Code:||E_FAIL (0x80004005)|
Solved! Go to Solution.
11-11-2019 02:48 AM
Thanks for your answer.
Where is this feature ? Bios or Windows ?
Do you have a check list to enable virtualization on T590 ? I did it in 2 steps on other laptops (several manfacturers on several windows versions) : enable Virtualization in Bios and run Oracle Virtual box on Windows without any modification in windows configuration.
Thansk for your advices.
11-13-2019 02:29 AM
After tests, retries, erros ... It seems that Intel processor included in this Laptop is the guilty part of the problem.
The intel documentation says that this processor can support virtualization while the Intel tool says No.
Bios is well configured and Hyper-V is disabled in Windows BUT systeminfo statement says that Hyper-V is running.
Is it the reason of the bad diagnose of Intel tool ?
How to be sure that Hyper-V is not running at all on Windows 10 ? How to avoid its execution ? A lot of solutions exists on Internet but none (of these I found) are working ...
Who solve this blocking issue ?
Thanks for your reading and future help ;-)