[Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update

Discussions related to using VirtualBox on Windows hosts.

[Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update

Postby davide.cossano » 14. Sep 2017, 15:52

Hello,
i use VirtualBox from a lot of year.
Tomorrow windows 10 get the last update (Version 10.0.15063) and after it mi windows Xp Vm doesn't start any more

When Virtual box give VERR_VMX_NO_VMX error tipically the virtual-t in bios isn't active.
In may case nothing is changed, only windows make an update.

I already try to unistall and install Virtual Box, but nothing chage.
I already try to stop all services where hyper-v is named.

I finish the idea. I already search this error on the comunity, but i have not find a right solution for my problem.

Sameone has already fixed my problem?
Thanks you for support.
Best regards
Davide Cossano.
davide.cossano
 
Posts: 2
Joined: 14. Sep 2017, 15:44

Re: VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update

Postby mpack » 14. Sep 2017, 16:35

Disable Hyper-v, per all the previous discussions of this problem.
mpack
Site Moderator
 
Posts: 25508
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update

Postby davide.cossano » 14. Sep 2017, 17:16

I had already stopped all services about hyper-v
i tryed to unistall hyper-v from windows component
but wasn't enought...

I solved using this command from console:

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

Thanks you for you support.
Regards
Davide.
davide.cossano
 
Posts: 2
Joined: 14. Sep 2017, 15:44

Re: VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update

Postby mpack » 14. Sep 2017, 17:39

Thanks for reporting back.
mpack
Site Moderator
 
Posts: 25508
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: [Solved] VT-x is not available (VERR_VMX_NO_VMX) After Windows 10 Update

Postby RBStorms » 1. Dec 2017, 23:57

This appears to be happening again due to Microsoft issuing an update on the normal Windows 10 release track. They are enabling Hyper-v to one of their security issues.

Just thought I'd mention this, since mpack gets tired of regurgitating the same thing, over and over. :)

I KNOW I turned OFF Hyper-v when installing VirtualBox. It WAS working fine, and then MS Updates happened. Suddenly Hyper-v was back on, and VBox failed to open my XP VM.

Lesson learned: Check that Hyper-v is not enabled, even if you know you have previously disabled it. M$ is turning it back on for you.

Thank You for your support!
RBStorms
 
Posts: 1
Joined: 1. Dec 2017, 23:36


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: Bing [Bot], davidhay and 30 guests